ComposioHQ / agent-orchestrator

Agent Orchestrator — The Orchestration Layer for Parallel AI Agents Spawn parallel AI coding agents, each in its own git worktree. Agents autonomously fix CI failures, address review comments, and open PRs — you supervise from one dashboard. --- Agent Orchestrator manages fleets of AI coding agents working in parallel on your codebase. Each agent gets its own git worktree, its own branch, and its own PR. When CI fails, the agent fixes it. When reviewers leave comments, the agent addresses them. You only get pulled in when human judgment is needed. **Agent-agnostic** (Claude Code, Codex, Aider) · **Runtime-agnostic** (tmux, Docker) · **Tracker-agnostic** (GitHub, Linear) See it in action Quick Start > **Prerequisites:** Node.js 20+, Git 2.25+, tmux, CLI. Install tmux via (macOS) or (Linux). Install Permission denied? Install from source? If fails with EACCES, prefix with or fix your npm permissions. To install from source (for contributors): Start Point it at any repo — it clones, configures, and launches the dashboard in one command: Or from inside an existing local repo: That's it. The dashboard opens at and the orchestrator agent starts managing your project. Add more projects How It Works • **You start** — launches the dashboard and an orchestrator agent • **Orchestrator spawns workers** — each issue gets its own agent in an isolated git worktree • **Agents work autonomously** — they read code, write tests, create PRs • **Reactions handle feedback** — CI failures and review comments are automatically routed back to the agent • **You review and merge** — you only get pulled in when human judgment is needed The orchestrator agent uses the AO CLI internally to manage sessions. You don't need to learn or use the CLI — the dashboard and orchestrator handle everything. Configuration auto-generates with sensible defaults. You can edit it afterwards to customize behavior: CI fails → agent gets the logs and fixes it. Reviewer requests changes → agent addresses them. PR approved with green CI → you get a notification to merge. See for the full reference, or run for the complete schema. Plugin Architecture Eight slots. Every abstraction is swappable. | Slot | Default | Alternatives | | --------- | ----------- | ------------------------ | | Runtime | tmux | docker, k8s, process | | Agent | claude-code | codex, aider, opencode | | Workspace | worktree | clone | | Tracker | github | linear | | SCM | github | — | | Notifier | desktop | slack, composio, webhook | | Terminal | iterm2 | web | | Lifecycle | core | — | All interfaces defined in . A plugin implements one interface and exports a . That's it. Why Agent Orchestrator? Running one AI agent in a terminal is easy. Running 30 across different issues, branches, and PRs is a coordination problem. **Without orchestration**, you manually: create branches, start agents, check if they're stuck, read CI failures, forward review comments, track which PRs are ready to merge, clean up when done. **With Agent Orchestrator**, you: and walk away. The system handles isolation, feedback routing, and status tracking. You review PRs and make decisions — the rest is automated. Documentation | Doc | What it covers | | ---------------------------------------- | ------------------------------------------------------------ | | Setup Guide | Detailed installation, configuration, and troubleshooting | | CLI Reference | All commands (mostly used by the orchestrator agent) | | Examples | Config templates (GitHub, Linear, multi-project, auto-merge) | | Development Guide | Architecture, conventions, plugin pattern | | Contributing | How to contribute, build plugins, PR process | Development See docs/DEVELOPMENT.md for code conventions and architecture details. Contributing Contributions welcome. The plugin system makes it straightforward to add support for new agents, runtimes, trackers, and notification channels. Every plugin is an implementation of a TypeScript interface — see CONTRIBUTING.md and the Development Guide for the pattern. License MIT