Amp Amp Code Orbs

One prompt. One orb. Agents that keep going.

Give every agent its own orb

Orbs are remote machines where Amp's coding agents work without supervision. Close your laptop. The work keeps going. Play the simulation to feel the difference between one blocked machine and a fleet of remote agents.

Enter Fleet Command Read the explainer

What is an orb?

A fresh remote machine for every thread

Not on your laptop

When you create a new Amp thread, you get a fresh orb. It contains your code, your plugins, and the tools the agent needs. The agent runs on the orb, not your machine, but you control it as if it were local.

Built for the heavy work

Long builds, large test suites, repository migrations, and anything you do not want eating your local machine. Agents keep working when you are not sitting at your computer.

Wake, pause, resume

Orbs auto-pause after five minutes of inactivity and pause when a thread is archived. Paused orbs cost nothing and resume the moment they are accessed. After first setup, the sandbox is snapshotted and reused for up to 24 hours, so new orbs start fast.

Parallel, unsupervised, shared

Spawn as many as you need. Agents can spawn other agents across orbs, local machines, and remote machines, sharing messages and files to parallelize work. You can invite teammates into the same orb for multiplayer control.

Simulation

Fleet Command

Use W A S D or arrow keys to move your orb. Fly to a slot and press Space to spawn an agent. Pick a size first.

Orb size
Agent mode
Scenario
$0.0000burned
0/0done
0:00fleet time

Laptop race

Laptop not started

    Inside the orb

    What lives inside a fresh orb

    Every orb runs Debian 12 and ships with the tools an agent usually needs, plus authenticated gh and amp.

    GitSSHtmuxffmpegImageMagickvimjqfzfripgrepPostgreSQLRedisBunNode.jsnpmpnpmYarnPythonpipagent-browser

    Anything else installs with apt. Repository lifecycle scripts live in .agents/:

    .agents/setup

    Runs once while the orb is being prepared. Install dependencies, generate files, seed databases, verify tools. Logs to /home/user/.cache/amp/logs/setup.log.

    .agents/resume

    Runs every time an existing orb wakes. It must be fast and idempotent, with a 10-second timeout. Logs to /home/user/.cache/amp/logs/resume.log.

    AGENTS.md

    Carries repository guidance for the agent: conventions, commands, tests, and how the codebase is organized.

    Launch an orb

    Four ways to start one

    Web

    Click Create New Thread at ampcode.com, pick a project, enter a prompt.

    CLI

    amp -ox "your prompt"

    Add --orb-size a1.small to set the size.

    TUI

    thread: new in orb

    From the command palette inside the Amp terminal interface.

    Plugin

    agent.createThread({ executor: 'orb' })

    Spawn a thread from a plugin or automation.

    Hands on

    You control every orb from anywhere

    Browse and review

    Browse files on the orb, review and approve changes straight from the thread, and mirror the orb to your laptop with amp sync <thread-id> while the work continues remotely.

    Open a terminal

    Open a shell inside the orb in a tmux session shared with the agent. Inspect files, run tests, debug in the same environment the agent uses.

    Portals

    Expose web servers inside an orb as authenticated URLs. Declare services in .amp/services.yaml, start them with amp orb services ensure, and share URLs with teammates. A request to a portal wakes a paused orb and resumes billing.

    Every device

    Amp runs on the web, in the terminal, and on the phone. Continue from your phone or pick up from another machine without transferring code.

    Sizing

    Five sizes, billed by the minute

    Pick a size with amp -ox "prompt" --orb-size a1.small. Enterprise pricing runs 50% higher than the listed rates.

    a1.tiny

    1 CPU, 2 GB RAM, 40 GB disk

    $0.08/hrBest for tiny fixes

    a1.small

    2 CPU, 4 GB RAM, 40 GB disk

    $0.17/hrIncluded in Megawatt

    a1.medium

    4 CPU, 8 GB RAM, 40 GB disk

    $0.33/hrBalanced step up

    a1.large

    8 CPU, 16 GB RAM, 40 GB disk

    $0.66/hrHeavy builds

    a1.xxlarge

    16 CPU, 32 GB RAM, 40 GB disk

    $1.32/hrMigrations at speed

    Pricing

    Amp plans

    PlanOrb hoursAgent usageModes
    Megawatt — $20/mo750 hours of small orbs$20 includedlow, medium
    Gigawatt — $200/mo1,000 hours of xxlarge orbs$200 includedlow, medium, high, ultra
    UnconstrainedPay-as-you-go for teams and enterprisesPay-as-you-goAll modes

    A day in the life

    What a developer's day looks like

    1. 1. Send a prompt

      Create a new thread on the web, in the CLI, or from a plugin. The orb spins up with your repo and tools ready.

    2. 2. Close the laptop

      The agent keeps working on the orb. You can check in from your phone or another machine at any time.

    3. 3. Agents coordinate

      One agent can spawn others in fresh orbs, passing messages and files to split work across a fleet.

    4. 4. Review and ship

      Browse files, open a terminal, review diffs, approve changes, and sync them back to your laptop — or ship them directly from the orb.

    More demos