Agent Orchestrator
A local control layer for supervising parallel coding-agent sessions in isolated workspaces.
What does this agent do, and when should you use it?
Agent Orchestrator (AO) is a local Agent IDE and orchestration layer for running terminal coding agents in parallel. Its desktop app and CLI supervise projects, sessions, terminals, branches, pull requests, and feedback state while the selected agents perform the coding. Each session runs in its own Git worktree to separate concurrent changes. A local daemon watches session state, terminal activity, pull requests, CI, and review feedback, then routes relevant failures, comments, and merge conflicts back to the matching session. AO ships adapters for 23 worker harnesses and lists Claude Code, Codex, and opencode as separately configured reviewer harnesses.
A user adds a project in the desktop app or CLI and starts one or more sessions. AO creates an isolated git worktree for each session and launches the selected coding agent in that session's terminal runtime. Its local daemon watches session state, terminal activity, pull requests, CI, and review feedback; CI failures, review comments, and merge conflicts can be sent back to the relevant worker session. The desktop inspector exposes the selected session's terminal, pull-request state, review runs, and browser preview.
- An engineering lead running several independent changes in one repository and needing separate branches and workspaces for each coding session.
- A developer who needs to inspect a live Claude Code, Codex, or other terminal-agent session and send it follow-up instructions.
- A team that wants CI failures on a pull request routed back to the session that produced the change.
- A maintainer who runs reviewer agents and needs requested changes returned to the correct implementation session.
- A frontend developer who wants a local application preview beside the terminal for a session.
What are this agent's strengths and limitations?
- Uses a separate Git worktree per session, directly addressing file and branch isolation for concurrent work.
- Combines terminal access, session state, pull requests, CI, and review feedback in one desktop control surface.
- Ships adapters for 23 worker harnesses, with Claude Code, Codex, and opencode available as separately configured reviewers.
- Routes CI failures, review comments, and merge conflicts back to the relevant worker session automatically.
- Actual coding and authentication depend on separately installed supported terminal-agent CLIs; their setup is not detailed in the supplied material.
- Core operation relies on local Git worktrees, terminal runtimes, and a local daemon rather than a browser-only workflow.
- The npm CLI is frozen at 0.10.0, so new deployments are directed to the desktop application.
- The supplied material does not document offline behavior, CI/PR service authentication, permission controls, or retry behavior.
How do you install or deploy this agent?
Download the desktop build for macOS (Apple silicon or Intel), Windows, Linux AppImage, Debian/Ubuntu (.deb), or Fedora/RHEL (.rpm). Open Agent Orchestrator after installation and point it at the repository to manage; the desktop app runs the daemon. The legacy CLI remains available with: npm install -g @aoagents/ao followed by ao start, but the supplied documentation says npm is frozen at version 0.10.0 and recommends the desktop build for new setups. You also need a supported coding-agent CLI; its installation and authentication are not specified in the supplied material.
How do you use this agent?
Open the desktop app, add a target project, create one or more sessions, and select an available coding agent. AO creates a separate git worktree and starts an agent terminal for each session. Use the project and session views to monitor working, waiting, finished, or blocked state. In the selected session's inspector, review terminal output, PR state, review runs, or a local browser preview, and send follow-up instructions to that session.