Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR branches for local UI review; and diagnose stale Electron processes, port conflicts, or preload bridge mismatches. Use whenever asked to run, open, show, or visually…
Catalog of the AO (Agent Orchestrator) ao CLI: spawning workers, managing sessions and projects, sending messages, controlling the shared browser, previewing pages, and daemon control. Use when using the ao CLI, 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. Tabs in this worker share an ephemeral browser profile, while…
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 agent session in a registered project. The session runs the chosen agent in a fresh git worktree. Register the project first with ao project add.
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.