Agent Orchestrator

What is Agent Orchestrator?

Agent Orchestrator is a meta-harness agent IDE for running AI coding agents in parallel. It gives terminal-based agents like Claude Code, Codex, Cursor, Aider, Goose, and others a shared workspace where their sessions, terminals, branches, pull requests, and feedback loops can be supervised from one place.

The agents still do the coding. AO provides the harness around them: isolated workspaces, live terminal access, session state, PR awareness, and automatic loops that send CI failures, review comments, and merge conflicts back to the right agent. Instead of manually coordinating a pile of agent terminals, AO turns parallel agent work into a managed workflow.

Why Agent Orchestrator?

AI coding agents become much more useful when they can work in parallel, but parallel work gets messy quickly. Branches overlap, terminals get lost, CI failures need follow-up, review comments need replies, and merge conflicts have to reach the right worker.

Agent Orchestrator is built to keep that loop visible and manageable. It helps you:

• Start multiple agents from the same project without mixing their work
• Keep every session in a separate git worktree
• See which agents are working, waiting, finished, or blocked
• Route CI failures, review comments, and merge conflicts back to the right session
• Use different agent CLIs through one common supervisor

How it works

At a high level, Agent Orchestrator follows a simple loop:

1. Add a project you want agents to work on.
2. Start one or more sessions from the desktop app or CLI.
3. AO creates an isolated git worktree for each session.
4. AO launches the selected coding agent in that session's terminal runtime.
5. The local daemon watches session state, terminal activity, pull requests, CI, and review feedback.
6. The desktop app and CLI show the current state and let you send follow-up instructions to the right session.

The result is a local control layer for agentic coding: agents still do the coding, while Agent Orchestrator keeps their workspaces, status, terminals, and feedback loops organized.

Witness AO's Journey on X

Visit	Visit
Visit	Visit

What is Agent Orchestrator? • Why Agent Orchestrator? • How it works • Features • Quick Start • Architecture • Documentation • Contributing

Features

Supported Agents

Works with 23+ CLI-based coding agents including Claude Code, OpenAI Codex, Cursor, OpenCode, Aider, Amp, Goose, GitHub Copilot, Grok, Qwen Code, Kimi Code, Crush, Cline, Droid, Devin, Auggie, Continue, Kiro, and Kilo Code.

If it runs in a terminal, it runs on Agent Orchestrator.

Quick Start

Prerequisites

Optional:

• tmux (Darwin/Linux) - For Unix runtime
• gh (GitHub CLI) - For authenticated GitHub API calls

Installation

Download the latest release for your platform:

Direct Download: Latest Release

Telemetry

Agent Orchestrator collects minimal telemetry for reliability and product understanding. Data is stored locally by default; remote transmission is opt-in via environment variables. Read the full telemetry policy.

Architecture

Agent Orchestrator is a long-running Go daemon built around inbound/outbound port contracts with swappable adapters.

Core mental model: OBSERVE external facts → UPDATE durable facts → DERIVE display status / ACT

Key components:

• Frontend - Electron + React UI with TanStack Router/Query and shadcn/ui
• Backend Daemon - Go-based HTTP server with controllers, services, and adapters
• Runtime - Platform-specific: tmux on Darwin/Linux, conpty on Windows
• Storage - SQLite with change-data-capture (CDC) for real-time updates
• Adapters - 23+ agent adapters, git worktree workspace, GitHub SCM integration

For detailed architecture diagrams, data flows, and load-bearing rules, see architecture.md.

Documentation

Testing

# Backend tests
cd backend
go test -race ./...

# Frontend tests
cd frontend
pnpm test

# Full CI validation locally
npx @redwoodjs/agent-ci run --all

Configuration

All configuration is environment-driven. The daemon takes no config file.

Health Checks

curl localhost:3001/healthz   # Liveness probe
curl localhost:3001/readyz    # Readiness probe

Contributing

We love contributions! Join our community on Discord to get started.

Join us on Discord

Daily contributor sync: Every day at 10:00 PM IST

Get your issues verified by core contributors, ask questions, share progress, and learn from the community. New contributors are always welcome!

Why join Discord?

• Get your issues and PRs verified by core contributors before investing time
• Learn from experienced contributors in daily sync calls
• Share your progress and get feedback
• Get help troubleshooting in real-time
• Stay updated on the latest developments and roadmap

Quick Start

1. Join the Discord - Connect with the community and get guidance
2. Read the contributor contract - See AGENTS.md for repo layout, daemon/API boundaries, and coding conventions
3. Pick a focused problem - Browse open issues and choose one small enough for a focused PR
4. Open a clear PR - Keep changes narrow, explain user-visible impact, link issues, include tests
5. Iterate with contributors - Use review feedback to tighten the PR until verified

License

Apache License 2.0 - see LICENSE for details.