agent-orchestrator

Desktop agent IDE for fleets of coding agents: each task gets a worker with its own workspace and agent CLI, while a project orchestrator plans work and handles CI fixes, conflicts and reviews.

10,772 1,500 Go Apache-2.0updated today

coding orchestration agents

View on GitHubDispute this mapping →

Curator's take

The one to try if you want a GUI cockpit rather than a terminal multiplexer — a background daemon, a Kanban over live workers, isolated workspaces and browsers per task, and an orchestrator that will actually decompose an outcome into tasks and sequence them. That framing costs scriptability: it is a desktop product first, so headless CI use and remote-only setups fit worse than tmux-style tools, and you still install and configure every agent CLI yourself. The isolated-workspace-per-worker discipline is the part worth stealing even if you don't adopt the app.

Mapped by ShipWithAI editors · links verified

README.md

Agent Orchestrator

Plan, run, and supervise coding agents from one place.

Give every coding task its own agent, workspace, and feedback loop.
Plan and delegate larger outcomes with a project-aware orchestrator.
Follow every worker, pull request, CI run, and review in a live Kanban.

Download AO • Documentation • Releases • Contributing • Discord

English · 简体中文 · 日本語 · 한국어 · Español · Français · Deutsch · Português (Brasil)

Agent Orchestrator Kanban showing worker sessions grouped by live status

A workspace for agent-driven development

One coding agent can handle a task. Running several across a project creates a different job: deciding what matters, splitting work cleanly, giving each agent the right context, preventing branch collisions, and following every change through review and merge.

AO is a local desktop workspace built for that job. Add a repository and create a worker session with the coding agent, model, and interface that fit the task. For Git-backed work, AO gives the worker its own branch and worktree. The task, conversation, terminal, changed files, browser preview, pull request, CI, and review state stay attached to that session from start to finish.

Behind the desktop app, AO's local daemon watches agent activity and source-control state. The result is a shared, live view of the project instead of a collection of disconnected terminals, branches, and browser tabs.

Install

Download the latest AO desktop app for your platform. AO checks for updates automatically.

Platform	Download
macOS (Apple silicon)	Download
macOS (Intel)	Download
Windows	Download
Linux (AppImage)	[Download](https://git

Continue your stack

What teams reach for next — and why each earns a place beside agent-orchestrator. Ranked by curator confidence.

Pairs well with

abtop

htop for AI coding agents: every Claude Code, Codex and OpenCode session in one TUI — tokens, context-window %, rate limits, child processes, orphan ports. Read-only, no API keys. Rust.

Why it fitsAO only sees the workers it spawned. abtop is an htop across every Claude Code, Codex and OpenCode session on the machine, including the ones you started by hand outside the app.

tare

Claude Code skill that reads your local session logs and answers 'where did my tokens go' in plain English: deduplicated totals, cost charged to the tool that caused it, 5-hour window state.

Why it fitsRunning fleets of coding agents in parallel worktrees is exactly what makes a quota vanish without anyone noticing — and AO's own Kanban shows task state, not token cost. tare reads the session logs afterwards and names which worker burned the window. Caveat: tare is Claude Code only, so it covers the AO workers using that CLI and nothing else.

Alternative to See all + compare →

herdr

Agent multiplexer for your terminal: every Claude Code/Codex session in real panes — blocked/working/done at a glance, detach and reattach over SSH, plus a socket API agents drive themselves.

Why it fitsBoth supervise many concurrent coding-agent sessions at a glance. Herdr is a terminal multiplexer you can detach and reattach over SSH with a socket API; AO is a desktop app with Kanban and a planning orchestrator above the workers.

squad

Multi-agent terminal collaboration for AI CLIs: a manager, workers and an inspector — Claude Code, Gemini, Codex, OpenCode — coordinating through one-shot shell commands and SQLite. No daemon.

Why it fitsSame job — several coding CLIs cooperating on one repo with a manager above workers. Squad is daemonless, coordinating through shell commands and SQLite; AO runs a daemon plus a native GUI and owns the workspaces.

alook

Self-hosted collaboration layer that turns local coding agents (Claude Code, Codex, OpenCode) into an always-on "AI company" — per-agent email, org chart, kanban, shared memory.

Why it fitsBoth wrap local coding agents into an org-shaped surface with roles, boards and shared context. alook is a self-hosted web 'AI company' with per-agent email and an org chart; AO is a native desktop IDE centred on tasks and pull requests.