Skip to content
FunCoding

using-ao

Catalog of the AO Cloud `ao` CLI available inside a cloud sandbox: spawning worker sessions, listing them, messaging them, reporting to the orchestrator, killing them, claiming pull requests, and starting AO reviews. Use when orchestrating or coordinating AO cloud sessions with the ao CLI.

Star
13,116
License
Apache-2.0
Last commit
Oct 13, 2026

cloud/internal/skillassets/using-ao/SKILL.md

View on GitHub

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.

CommandWhat it doesWho can run itDetails
spawnCreate a worker session in its own fresh sandboxOrchestrators onlycommands/orchestration.md
list (ls, status)List the workers this orchestrator spawned, with branch, status, and PR factsOrchestrators onlycommands/orchestration.md
sendSend a message into a worker's conversationOrchestrators onlycommands/orchestration.md
kill (delete, rm)Terminate a worker session and its sandboxOrchestrators onlycommands/orchestration.md
reportSend a message to the orchestrator that spawned this sessionWorkers with an orchestrator parentcommands/orchestration.md
claim-prAttach an existing pull request to this sessionAny sessioncommands/pull-requests.md
review triggerStart AO's reviewer on this session's open pull requestsAny sessioncommands/pull-requests.md

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.

Similar Skills

using-git-worktrees

OBobra/superpowers298k2,631 new stars in the last 7 days

verification-before-completion

OBobra/superpowers298k2,631 new stars in the last 7 days

finishing-a-development-branch

OBobra/superpowers298k2,631 new stars in the last 7 days

wizard

MAmattpocock/skills288k10,178 new stars in the last 7 days

git-guardrails-claude-code

MAmattpocock/skills288k10,178 new stars in the last 7 days

triage

MAmattpocock/skills288k10,178 new stars in the last 7 days