orchestratorinc/agent-orchestrator/using-ao

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, or ao preview here. Every command is ao help for the authoritative list.

Conventions

• ao list --json prints machine-readable output; --all includes terminated

workers (hidden by default).

• --agent is an alias for --harness on ao 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 ao commands above are the only channel between sessions.

• A send to a worker whose sandbox is still provisioning is queued by the

control plane and delivered when the worker's agent is ready — check runtimeConnected in ao list --json to 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.

• Opening pull requests and submitting review verdicts use socket helpers

described in commands/pull-requests.md; claiming a PR and starting an AO review use ao.