Using Ao

Reference catalog for the AO (Agent Orchestrator) `ao` CLI covering worker spawning, session and project management, messaging, page previewing, and daemon control. Use it when working with the `ao` CLI within an AO workspace.

Tasks

Run `ao status` to verify the AO daemon is running and healthy before executing other commands.
Spawn a worker agent in a fresh git worktree with `ao spawn` when starting a new task or issue.

Inputs

Project names or IDs (via `-p / --project`) to scope session subcommand lookups
The `--json` flag on read commands for machine-readable output
Session and project IDs as shown by `ao session ls` and `ao project ls`

Outputs

Machine-readable JSON output when `--json` is passed to read commands
Daemon status from `ao status`
Version information from `ao version`
Shell completion scripts from `ao completion`

Limitations and checks

Every command's authoritative flag list is only available via `ao <command> --help`, not fully enumerated in this catalog
The `--agent` flag is an alias for `--harness` only on `ao spawn`
Detailed command documentation requires consulting the linked per-command reference files
Confirm the daemon is up and healthy with `ao status` before running commands that depend on it.
Verify the correct project is scoped by passing `-p / --project` when running session subcommands.
Use `ao doctor` to run local health checks if AO setup problems are suspected.
Check the authoritative flags for any command with `ao <command> --help` rather than assuming defaults.

Search

Find projects, verify facts, compare options, and filter by your requirements

Try a searchA click only fills the search box; you stay in control

Collection Scenario Project type License Deployment Resource form

Using Ao

Tasks

Inputs

Outputs

Limitations and checks

Search

Project Details