AO Cloud CLI Catalog
ao inside a cloud sandbox is a thin client over the AO control plane. It is a
different, smaller CLI than the desktop ao: there is no ao session,
ao project, ao status, ao preview, or ao browser here. Every command is
ao help for the authoritative list.
| Command | What it does | Who can run it | Details |
|---|---|---|---|
spawn | Create a worker session in its own fresh sandbox | Orchestrators only | commands/orchestration.md |
list (ls, status) | List the workers this orchestrator spawned, with branch, status, and PR facts | Orchestrators only | commands/orchestration.md |
send | Send a message into a worker's conversation | Orchestrators only | commands/orchestration.md |
kill (delete, rm) | Terminate a worker session and its sandbox | Orchestrators only | commands/orchestration.md |
report | Send a message to the orchestrator that spawned this session | Workers with an orchestrator parent | commands/orchestration.md |
claim-pr | Attach an existing pull request to this session | Any session | commands/pull-requests.md |
Conventions
ao list --jsonprints machine-readable output;--allincludes terminated workers (hidden by default).--agentis an alias for--harnessonao spawn.- Session ids are UUIDs shown by
ao list. - Every session runs in its own isolated sandbox. Never try to reach another
session's sandbox directly (no ssh, no shared filesystem); the
aocommands above are the only channel between sessions. - A
sendto a worker whose sandbox is still provisioning is queued by the control plane and delivered when the worker's agent is ready — checkruntimeConnectedinao list --jsonto see whether a worker is live. - Spawning and messaging are idempotent server-side; a command that prints a success line has been durably accepted even if the effect is not visible yet.
- Pull requests and reviews are handled through socket helpers described in
commands/pull-requests.md, not through
ao.

