Amp Launches Orbs for Unsupervised Cloud AI Agent Execution
Amp has introduced Orbs, dedicated remote cloud environments designed to run AI coding agents asynchronously without eating local machine resources. Developers can launch multiple parallel agent threads via CLI flags and pull modified files back to local checkouts.
Impact: High
Why it matters
You can now delegate long-running tasks like multi-bug investigations or test suite runs to cloud agents without blocking your local IDE.
TL;DR
- 01Launch remote agents directly from the Amp TUI using the amp -ox CLI flag.
- 02Isolate long-running tasks like performance profiling and multi-bug investigations from host hardware.
- 03Sync completed remote changes back to local worktrees without manual file transfers.
Key facts
- Execution Model
- Isolated remote cloud container (Orb)
- Billing Structure
- Billed by the minute
- CLI Launch Flag
- -ox
Isolated Cloud Execution for AI Agents
Amp Orbs transition AI coding workflows from local background processes into isolated remote sandboxes. When spawning a thread using amp -ox, the platform provisions a container equipped with repository code, toolchains, and project plugins. This architecture allows developers to convert routine bug reports or failing CI runs directly into standalone agent investigations.
Remote Inspection and Local Synchronization
Developers interact with Orb-hosted agents using the standard Amp TUI interface. The workspace allows live file browsing and execution inspection without host machine performance degradation. Once an agent completes an edit or diagnostic task, engineers sync changes directly to their local checkout.
Consumption-Based Resource Management
Orbs scale compute dynamically based on task duration. Instances spin up on demand and go to sleep upon task completion. Per-minute billing ensures cost efficiency during prolonged optimization runs or background test execution.
Try it in 2 minutes
amp -ox "Investigate why the latest CI run on 'main' failed"bash
✓ When to use
- Running long background processes such as complex refactoring or benchmark suites.
- Investigating multiple unrelated bugs in parallel without local git tree conflicts.
- Working on low-powered hardware where local agent inference and testing exhaust system memory.
What to do today
- Install or update the Amp CLI tool to access remote orb features.
- Run amp -ox with a diagnostic prompt to test background execution on a failing CI pipeline.
Sources