Orchestrator · active

Agent Orchestrator

An open-source desktop workbench that runs coding agents in isolated Git worktrees and tracks each task through pull request, CI, review, and merge.

Visit Agent Orchestrator ↗Checked Sep 12, 2026 · review due Oct 12, 2026
Best for
Developers on GitHub who run several agent CLIs in parallel and want one board for worktrees, pull requests, CI failures, and review feedback.
Avoid if
You need GitLab or issue-tracker integration, a hosted team service, or OS-level sandboxing of agent processes.

01 / Editorial view

Where it fits

Strengths

  • 27 documented agent harnesses
  • Worktree isolation per worker
  • CI, review, and merge-conflict feedback routed back to the owning agent
  • Project-level orchestrator for planning and delegation

Limitations

  • GitHub is the only shipped source-control integration
  • Single-user local daemon; no hosted team offering is documented
  • Worktrees isolate code, not processes or network access
  • Remote telemetry is on by default in release builds

02 / Workflow

Surfaces and capabilities

Autocomplete
Unknown
Chat
Yes
Agent
Yes
Background agent
Yes
Review
Yes
Testing
Unknown

Editors

Unknown

Operating systems

macOS, Windows, Linux

Repository hosts

GitHub

Languages

Agent-dependent

Bring your own key

Yes

Bring your own model

Unknown

03 / Orchestration

Coordination model

Supported agents

Claude Code, Codex, Cursor, OpenCode, Aider, GitHub Copilot, Grok, Kimi, Pi, Amp, Auggie, Droid, Crush, Cline, Goose, Qwen, Continue, Devin, Kiro, Kilo Code, Vibe, Muse, Agy, Autohand, Kimchi, Prime Agent, OMP

Isolation

Git worktrees, Branchless scratch directories, Per-worker browser profiles

Task sources

Manual tasks, Project orchestrator delegation

Maximum parallelism

Unknown

Planning
Yes
Scheduling
Unknown
Agent communication
Yes
Review gates
Unknown
CI recovery
Yes
Merge workflow
Yes
Session persistence
Yes
Observability
Yes
Human approval
Yes

04 / Cost and deployment

What it costs to run

Individual

Apache-2.0 open-source desktop app; agent usage is billed by each harness's provider.

Team

Unknown

Enterprise

Unknown

Agent usage is billed according to the provider account or subscription used by each installed harness.

05 / Privacy

Data handling

Code processing
Runs locally; application state stays under ~/.ao on the user's disk, while installed agents and GitHub tooling follow their own provider data policies.
Indexing
Unknown
Retention
Projects, worktrees, sessions, and settings stay on local disk; local telemetry records are pruned after 30 days.
Training policy
Unknown
Enterprise controls
Loopback-only daemon listener, Desktop and daemon telemetry opt-out

06 / Evidence

Primary sources

Changelog

What changed

Next