Open Source · MIT Licensed · 6.3k GitHub Stars

Run 30 AI agents in parallel.
One dashboard.

Agent Orchestrator spawns Claude Code, Codex, Cursor, Aider, and OpenCode in isolated git worktrees. Each agent gets its own branch, creates PRs, fixes CI, and addresses reviews autonomously.

$ npx @aoagents/ao start
Read DocsView on GitHub
agent-orchestrator — my-saas-app
The problem

You're running AI agents in 10 browser tabs. Checking if PRs landed. Re-running failed CI. Copy-pasting error logs.

Agent Orchestrator replaces that with one YAML file. Point it at your GitHub issues, pick your agents, and walk away. Each agent spawns in its own git worktree, creates PRs, fixes CI failures, addresses review comments, and moves toward merge. If you are new, start with the docs quickstart and configuration guides.

agent-orchestrator.yaml
agent: claude-code
tracker: github
workspace: worktree
runtime: tmux
notifier: slack
Works with your favorite AI agents
Anthropic
Claude Code
OpenAI
Codex
Cursor
Cursor
Aider
Aider
OpenCode
OpenCode
PARALLEL

Multi-agent execution

Run Claude Code, Codex, Cursor, Aider, and OpenCode simultaneously. Each agent gets its own git worktree, its own branch, its own context.

RECOVERY

Autonomous CI + review handling

CI fails? The agent reads the logs and pushes a fix. Review comments land? The agent addresses them. You sleep, your agents ship.

PLUGINS

7 swappable slots

Runtime, Agent, Workspace, Tracker, SCM, Notifier, Terminal. Use tmux or process. GitHub or GitLab. Slack or webhooks. Swap anything.

DASHBOARD

Real-time Kanban + terminal

Every agent's state in one view. Attach to any terminal via the browser. SSE updates every 5 seconds. WebSocket for live terminal I/O.

Lifecycle

From issue to merged PR

Issue assigned
#42
Agent spawns
claude-code
Worktree created
feat/auth
PR opened
PR #312
CI passes
✓ 48/48
Merged
main
Use cases

What teams run with AO

Clear a bug backlog overnight

Before

10 issues, 3 days of context-switching

After

10 agents, 10 PRs by morning

$ ao batch-spawn 101 102 103 104 105 106 107 108 109 110

Ship a feature sprint in hours

Before

5 feature tickets, 1 dev, 1 week

After

5 agents in parallel, PRs landing same day

$ ao batch-spawn --label feature-sprint

Migrate an API across 20 files

Before

Manual find-and-replace, missed edge cases

After

Agent rewrites, runs tests, fixes failures, opens PR

$ ao spawn 42 --agent claude-code
Process

Three steps to orchestration

01

Configure & assign

Point Agent Orchestrator at your repo with a YAML config. Choose your agent, set up trackers and notifiers. One file, full control.

$ ao batch-spawn 42 43 44 45 46
 
⟡ Loading config from agent-orchestrator.yaml
⟡ Resolving 5 issues from GitHub
⟡ Spawning sessions in worktrees...
✓ Session s-001 spawned → issue #42
✓ Session s-002 spawned → issue #43
✓ Session s-003 spawned → issue #44
✓ Session s-004 spawned → issue #45
✓ Session s-005 spawned → issue #46
 
5 agents working · Dashboard → http://localhost:3000
02

Agents work

Each agent spawns in an isolated worktree. They write code, create PRs, run tests, and fix failures. Monitor everything from the live dashboard, or let them run.

my-saas-app · 5 sessions
Working
Add user auth flow
#42 · feat/auth
claude-code
Fix pagination bug
#43 · fix/pagination
codex
Pending
Add rate limiting
#44 · PR #312
aider
Review
Update API tests
#45 · PR #310
claude-code
Merged
Refactor DB layer
#46 · PR #308
opencode
03

PRs land

Agents create pull requests, address review comments, fix CI failures, and get them to mergeable state. Your morning starts with merged PRs, not a backlog.

feat/user-auth
Add user authentication flow
✓ Merged
fix/pagination-offset
Fix off-by-one in cursor pagination
✓ Merged
feat/rate-limiting
Add Redis-backed rate limiter
✓ Merged
refactor/db-layer
Extract repository pattern from services
✓ Merged
Why Agent Orchestrator

The only open-source, web-based agent orchestrator

Conductor, T3 Code, and Codex App are native Mac apps. AO runs in your browser, works on any OS, and you can self-host or extend it.

FeatureAOOthers
Web-based dashboardNative Mac apps only
Open source (MIT)Closed source
Multi-agent (Claude, Codex, Aider, OpenCode)Single agent
Auto CI failure recoveryManual
Plugin architecture (7 slots)Fixed integrations
Git worktree isolationShared workspace
See it in action
6,314
GitHub Stars
855
Forks
628
Open Issues
21
Watchers
6,314stars on GitHub
Built with itself — this repo is managed by Agent Orchestrator
What engineers say

Trusted by builders

Set up 12 agents on our backlog before lunch. By end of day, 8 PRs were merged.

01
Staff Engineer
Series B Startup

The auto CI recovery alone saves me hours a week. Agents fix their own broken tests. I just review and merge.

02
Solo Founder
Indie SaaS

We went from 3 PRs/day to 15 PRs/day. The plugin system means we swapped in GitLab and Linear without changing our workflow.

03
Eng Lead
20-person team
Get started in 60 seconds

Three commands to launch

STEP 01

Install

One command. No dependencies beyond Node.js.

$ npm i -g @aoagents/ao
STEP 02

Configure

Create an agent-orchestrator.yaml. Pick your agents, tracker, and notifiers.

$ ao start
STEP 03

Launch

Assign issues and watch agents spawn.

$ ao batch-spawn 1 2 3

Stop babysitting.

Start orchestrating.

$ npm i -g @aoagents/ao