Twitter/X

Maintains ~2–6 concurrent Amp threads, typically with one large orchestrating…

2026-08-07 · 13:24 UTC ·@rockorager ·1 min read

Brief

rockorager describes an Amp-first workflow: they run ~2–6 concurrent threads with a central orchestrator that creates communicating orbs; webhooks spawn per-repo orbs to auto-review PRs and investigate issues; they use the PWA on Linux and iOS while running amp --no-tui as a systemd service, tag teammates in multiplayer threads, and have Amp track CI/deploy for 75% of main pushes.

Why it matters

Maintains ~2–6 concurrent Amp threads, typically with one large orchestrating thread that spawns orbs which communicate with each other to coordinate larger changes.

Key details

  • Has webhooks so every OSS project spawns a new orb for PRs; PRs are automatically reviewed and appear in the sidebar when review finishes, and issues are automatically investigated.
  • Uses the Amp PWA on Linux and iOS and no longer uses the TUI; runs amp --no-tui as a systemd service to spawn local threads from the PWA, tags Amp team members to make threads multiplayer, and asks Amp to track CI/deployment for 75% of pushes to main to report rollout issues.
Source evidence

Here's how I'm using Amp these days:

  • I have ~2-6 threads going at any given time. Often I will have one large-ish orchestrating thread that spawns new orbs to do larger changes. These orbs often communicate with each other

  • I have webhooks set up so every OSS project of mine spawns a new orb for PRs. These are automatically reviewed and ready for me in my sidebar when the review is done. Issues are automatically investigated

  • I use the PWA on Linux and the PWA on iOS. I shut my laptop regularly without a thought anymore. I don't use the TUI anymore

  • I run an amp --no-tui on my laptop as a systemd service so that I can spawn local threads from the PWA

  • I tag other amp team members in a thread, this makes the thread multiplayer. We collaborate in the Amp thread (instead of eg Slack)

  • 75% of my pushes to main I ask amp to track CI and deployment and let me know if there are any rollout issues. This is mostly so that I know when I can use the feature/fix I just pushed