Catalog of the AO (Agent Orchestrator) ao CLI: spawning workers, managing sessions and projects, creating reusable Cues, sending messages, controlling the shared browser, previewing pages, and daemon control. Use when using the ao CLI, creating Cues, spawning workers, or managing AO sessions in an AO workspace.
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, navigation state, and WebContentsView; the runtime remains usable while the Browser panel is hidden, except for commands that need the page to be painted (see…
Import reads the legacy Agent Orchestrator flat-file store (/.agent-orchestrator) read-only and ports its projects and per-project settings into the rewrite database. Legacy files are never modified, and a re-run skips rows that already exist, so it is safe to run more than once. The daemon must be stopped before…
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 .ao/launch.json.
Spawn a worker or orchestrator agent session in a registered project, or a standalone worker session that is not tied to a project. Standalone sessions run in an AO-managed directory. Register a project first with ao project add for project-scoped sessions.
Fetch (if needed) and open the Agent Orchestrator desktop app. The desktop app owns the daemon, state, and updates. ao start no longer runs a daemon: it resolves the installed app (or downloads the latest release), opens it, and exits.
All five commands talk to the AO control plane with this session's rotating worker credential. spawn, list, send, and kill require the worker:orchestrate scope, which only orchestrator sessions hold; report requires a parent orchestrator. A command run without the required scope fails with SCOPEREQUIRED.
Workers do not push with personal credentials. The sandbox provides two socket helpers (their exact invocations are in the $AOPULLREQUESTHELP and $AOREVIEWHELP environment variables) plus one ao command.
Create and inspect reusable Cues for a local AO project. Both orchestrators and workers can use this command from their sessions. The project defaults to AOPROJECTID, then the current session's project, then the registered project containing the current directory. Pass --project when the target differs.
★not rated 13k 5d agoA0 tokens
originalApache-2.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: