Run a fleet of coding agents while keeping branches, reviews, and CI failures manageable.
Get Orchestrator.inc • Documentation • Releases • Contributing • Discord
English · 简体中文 · 日本語 · 한국어 · Español · Français · Deutsch · Português (Brasil)
One coding agent can handle a task. Running several means splitting the work, keeping branches from colliding, and following every change through CI, review, and merge. Orchestrator.inc is a local desktop workspace for that: every task gets its own agent, branch, and worktree, and your code stays on your machine.
Tell a project's main agent what you want built. It plans the work, starts a worker for each piece in its own worktree, and comes back only when something needs you.
Sessions sort themselves into lanes from the agent, its PR, CI, and reviews, so whatever needs you is on top.
Failed checks, review comments, and merge conflicts go back to the worker that owns the branch until the PR is approved. A reviewer agent can read every PR before a person does.
Pick the agent and model per task, then work in structured chat or the agent's own terminal UI. Each worker also gets a browser to preview and test its app.
Worker, Chat, and reviewer support differ by agent; the agent setup guides have the current matrix.
 Claude Code |
 Codex |
 |
 |
 Aider |
 |
 |
 |
 Pi |
 |
 |
 |
 Crush |
 |
 |
 |
 |
 |
 Kiro |
 |
 Vibe |
 Muse |
 Agy |
 |
 Kimchi |
 Prime Agent |
 OMP |
 |
 |
 MiMo Code |
 Gemini CLI |
 |
|
 |
 |
 |
Control the agents running on your desktop from your phone. Install the app for iPhone or Android. Scan the QR code in Settings → Connect Mobile to pair it with your desktop. It works on your home Wi-Fi and away from home.
- Get alerts. A push notification tells you when an agent has a question or needs approval.
- Reply. Answer in chat, approve the request, or open the agent's terminal.
- Start work. Create a new worker and pick its agent and model.
- Review. Check pull requests and reviewer results.
Run workers in hosted workspaces instead of on your machine. Choose Clone to the cloud and pick a GitHub repository to start.
- Keep running. Tasks keep going with your laptop closed.
- Follow along. Open the chat, files, and terminal from the desktop app.
- Nothing on your machine. The code, worktrees, and agents all live in the cloud.
See the Cloud guide for setup.
Download from orchestrator.inc/download or GitHub Releases. The app updates itself.
| Platform | Download |
|---|---|
| macOS (Apple silicon) | agent-orchestrator-darwin-arm64.dmg |
| macOS (Intel) | agent-orchestrator-darwin-x64.dmg |
| Windows | agent-orchestrator-win32-x64.exe |
| Linux (AppImage) | agent-orchestrator-linux-x64.AppImage |
| Linux (Debian/Ubuntu) | agent-orchestrator-linux-x64.deb |
| Linux (Fedora/RHEL) | agent-orchestrator-linux-x64.rpm |
Open Orchestrator.inc and point it at the repository you want it to manage. The desktop app runs the daemon for you, so no CLI is required. See the installation guide for agent CLI setup and troubleshooting.
| Document | Start here when you need |
|---|---|
| Product documentation | Installation, agent setup, and day-to-day product usage. |
| docs/documentation-map.md | Which docs are human-facing, which are machine-readable contracts, and which wins on drift. |
| docs/architecture.md | Backend mental model, lifecycle, persistence, CDC, status derivation, and daemon boundaries. |
| docs/backend-code-structure.md | Package ownership and where each backend concern belongs. |
| docs/cli/README.md | CLI behavior and daemon route mapping. |
| docs/development.md | Prerequisites, build steps, running tests, and troubleshooting for local development. |
| docs/STATUS.md | What currently ships on main and what remains in flight. |
Start with the development guide for prerequisites, local setup, and test commands. Read CONTRIBUTING.md before opening a pull request, and use GitHub Issues for bugs and feature requests.
Open a bug report from your own GitHub account. A few sentences on what you did and what went wrong are enough; version, OS, and repro steps help if you have them.
A local coding agent can help gather evidence with the bug-triage skill; keep its logs and notes in attachments, and review the draft before submitting it yourself. Please don't have a bot file issues for you.
For help describing a problem, join the bug-triaging channel on Discord. See contribution guidance for more detail.
Join Discord for help and contributor discussion, follow @useOrchestrator for updates, or start a conversation in GitHub Issues.
Orchestrator.inc collects limited usage and reliability telemetry, never your code, prompts, agent conversations, or credentials. It includes an installation ID and your GitHub username; if you sign in to AO Cloud it also includes your AO Cloud user ID and the email address of that account, set once as a PostHog person property (never read from git config). Turn it all off in Settings > General > Privacy > Share usage analytics, which covers the desktop, the daemon, and a paired phone. Learn exactly what we collect and how to opt out.
Orchestrator.inc is available under the Apache License 2.0.