Skip to content
pier pier

Caveats

  • The SSM fallback tunnel is about 1 MB/s. Repos that can’t come from GitHub push their history through it (a 300 MB history takes about 5 minutes, once per create). The create output says which transfer mode you got and why.
  • Parking loses processes. Files, git state, and installed tools survive. The tmux server and an in-flight agent run don’t. Hibernate (park with RAM) is on the roadmap.
  • OAuth MCPs need a browser approval per session. Keychain-held tokens can’t be copied safely. This floor is real.
  • ssh-key-only GitHub auth pushes while attached. The forwarded agent disconnects with you. Any token lifts this.
  • pier proxy is macOS-only for now. pier port works everywhere.
  • Bake hooks live only in baked images. A repo with a .pier-bake.sh that was never baked runs stock. Setup then fails loudly, not silently.
  • Resize stays within the CPU arch (t4g to t4g). Providers only allow type changes on stopped instances.

Roadmap

Section titled “Roadmap”
  • GCP driver. Designed (IAP tunnel, labels, TERMINATED-with-disks as parked), parked until the AWS driver is fully hardened.
  • Hibernate/suspend parking. Keep RAM, resume mid-agent-run.
  • Linux pier proxy.
  • Custom base AMIs. Bring your own golden image under pier’s harness layer.