Key Takeaways
- Running coding agents directly on local developer laptops caps execution at the limits of battery life, network drops, and CPU thermal throttling.
- Amp built Orbs to run developer agents in isolated cloud environments, allowing tasks to continue uninterrupted after closing a laptop.
- Quinn Slack chose the name Orbs deliberately to avoid the negative baggage left behind by broken, early cloud agent implementations.
- Developers build custom orchestrators like Amprunner around the headless command-line mode in Amp to trigger parallel background runs.
The Laptop Fan Is Your Execution Limit
Running coding agents locally creates constant friction. When an agent runs inside a developer's local IDE or terminal, every hardware limitation becomes a work stoppage. A dropped Wi-Fi signal aborts the session. A warm room spins up the computer fan and throttles CPU compute. The engineer stays pinned to their desk because closing the machine immediately kills the process.
The Changelog hosts highlighted how local agents disrupt daily habits: “Because building with agents on your local machine is anxiety-inducing. You know, I just that world is not a world I want to live in. I want to live in a world where my agents have a home, right?” (play from 1:16:24) Moving execution out of the local environment changes developer behavior. As the hosts explained: “I've become spoiled to agents not running on the machine I'm actually on. It's liberating, you know, to be able to close the lid to your laptop or to not be anxious if you've got to transition from one work space to another, like physically.” (play from 9:02)
Why Amp Abandoned the Cloud Agent Label
Running agents remotely solves the machine bottleneck, but developer perception was broken by earlier attempts in the market. Slack pointed out that developers were burned by previous hosted solutions: “Yeah, we call them orbs because a lot of people tried cloud agents in the past or other people's cloud agents, and they just didn't work as well, and they got turned off from it.” (play from 19:17)
Instead of asking developers to babysit unstable shell sessions, Amp designed Orbs to handle autonomous, persistent execution in the cloud. As Slack described: “But now, with Orbs, and other people call them cloud agents, the ability to run agents on machines where you don't need to supervise them, and where the parallelism is not limited by how good your computer's fan is, that totally changes how you work.” (play from 8:38)
Headless CLI Lets You Scale Beyond One Machine
Cloud execution changes the developer's role from babysitter to reviewer. When an agent runs inside an isolated Orb, the engineer stops watching code generate character by character. Oversight moves to reviewing the completed output once the run finishes.
Offloading execution to cloud environments also unlocks orchestration. Teams are building custom orchestrators like Amprunner, which interfaces directly with the headless CLI mode in Amp. Because the agents run remotely, an orchestrator can dispatch five or ten tasks simultaneously across separate Orbs. The local laptop functions strictly as an interface to dispatch work and verify finished artifacts, rather than the machine grinding through the compute.
What to Do With This
Pick the most tedious multi-file task on your sprint board, such as updating API client models or cleaning up deprecation notices. Run the agent using a remote headless session instead of your local terminal, close your laptop, and walk away. Return when the cloud run finishes to inspect only the final git diff.