browser
Inspect and control the current AO session's target-isolated browser. The desktop app must be open. The agent and user share the same live page, cookies,…
Manage AO code reviews of a worker's PR.
$ npx -y skills add Untrivial-ai/agent-orchestrator --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/reviewContext preview
What this command does when you run it.
Manage AO code reviews of a worker's PR.
Manage AO code reviews of a worker's PR.
ao review <subcommand> [args] [flags]
---
Record a reviewer's result for a worker's PR.
**Syntax:**
ao review submit [worker-session-id] [flags]
**Flags:**
| Flag | Meaning | Default / Required | |---|---|---| | `--body string` | Review body: a path to a Markdown file, or `-` to read from stdin | - | | `--review-id string` | Id of the GitHub PR review just posted (the `.id` from the `gh api` POST that created the review) | - | | `--reviews string` | JSON review results array or object: a path, or `-` to read from stdin | - | | `--run string` | Review run id | Required | | `--session string` | Worker session id (or pass it as the positional argument) | - | | `--verdict string` | Review verdict: `approved` or `changes_requested` | Required |
If the local daemon is restarting when a result is submitted, AO retains the parsed result in memory and retries the same idempotent request for up to 30 seconds. Validation errors return immediately. If the daemon remains unavailable, the command reports failure and can be repeated safely; daemon idempotency handles the case where an earlier connection dropped after committing the result.
# Submit an approved review for session mer-3 ao review submit mer-3 --run review-run-1 --verdict approved
# Submit a changes-requested review with a body from stdin echo "Please fix the null check on line 42." | ao review submit --session mer-3 --run review-run-1 --verdict changes_requested --body -
Run and supervise teams of coding agents from planning to merge. Any harness (Claude code, codex, +25 more). Desktop, web, mobile, and cloud agents.
Inspect and control the current AO session's target-isolated browser. The desktop app must be open. The agent and user share the same live page, cookies,…
Run local AO health checks. Use this to diagnose setup problems or verify the environment is correctly configured.
Import reads the legacy Agent Orchestrator flat-file store (`~/.agent-orchestrator`) read-only and ports its projects and per-project settings into the rewrite…
Open a URL or workspace file in the desktop browser panel for the current session, or start a deterministic session-owned dev server from an existing…
Manage projects: register repos, inspect, configure per-project settings, and remove.