CLI Agent Orchestrator
CLI Agent Orchestrator (CAO)
A CLI that coordinates several coding agents: a supervisor delegates tasks to specialists in parallel or in sequence across isolated tmux sessions
- 1,548 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Launches coding agents that run commands and change project files
- Starts a local server and coordinates several processes in tmux
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/cli-agent-orchestrator-caoDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Launches coding agents that run commands and change project files
- Starts a local server and coordinates several processes in tmux
This is third-party code. Review the repository files before installing.
What it does
CAO runs a local cao-server, launches the chosen coding CLIs in isolated tmux sessions and gives a supervisor tools to coordinate workers. The agents stay full processes with their own authentication and capabilities; CAO only splits the work between them. It supports several providers: Claude Code, Codex, Cursor CLI, GitHub Copilot CLI, OpenCode, Kiro and others. It ships a localhost web UI, an operations MCP server, scheduled flows, multi-step workflows, shared memory and outcome-based learning. You drive it through cao commands: install a supervisor profile, launch and shut down sessions.
Who it is for. For developers and teams who want to run several coding agents in parallel under a shared supervisor.
Good fit when
- You want to parallelize work across several coding agents
- You need a supervisor that hands subtasks to specialists and merges the result
- You want to combine agents from different providers in one flow
Not a fit when
- A single agent without orchestration is enough
- You have no tmux, uv or an installed provider CLI
Example request
Launch a supervisor and split the work: one agent writes tests, another reviews the codeLimitations
It needs Python 3.10+, tmux 3.3+, uv and at least one supported provider CLI authenticated in advance. Providers use their own accounts and keys, and some may require access that is not directly available from Russia. Installing the main branch is a uv tool install; tagged releases are on PyPI.
How to disable. Stop the sessions with cao shutdown --all, then remove the tool: uv tool uninstall cli-agent-orchestrator.
FAQ
Which agents does it work with?
Coding CLIs: Claude Code, Codex, Cursor CLI, GitHub Copilot CLI, OpenCode, Kiro and several others. Each runs under its own account.
Does it need a cloud service?
No, cao-server runs locally and there is a web UI on localhost.
Discussion
No questions or reviews yet.
Related
CLI toolsOne runtime for Claude Code, Codex, OpenCode and more: a run counts as done only when checks the agent did not write pass
Multi-agent orchestration for Claude Code: teams, roles, autopilot and task routing across skills and subagents
A local dashboard for running many agents across machines: memory, code graph and agent-to-agent messaging
A tmux-based TUI that runs Claude Code, Codex and other agents in one list: status, quick prompts, worktrees and diff review
A memory and coordination layer for coding agents: specs and issues live in git while agents work in parallel
A CLI that lets agents in different terminals message, watch and spawn each other
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| CLI Agent Orchestrator (this card) | no | 1,548 | |
| Helmor | no | 1,306 | a desktop app that runs Claude Code |
| multi-agent-shogun | no | 1,421 | ten AI agents in tmux panes |
| Claw Orchestrator | no | 603 | one runtime for Claude Code |
README in short
The README explains that CAO coordinates several coding CLIs: a supervisor hands work to specialists in parallel or in sequence. It needs Python 3.10+, tmux 3.3+, uv and at least one authenticated provider CLI. Installation is a uv tool install from the main branch or from PyPI, then you install the code_supervisor profile, start cao-server and launch the supervisor with cao launch. You can watch the work in the terminal, in a localhost web UI or over tmux. The docs cover flows, workflows, skills, memory, tool restrictions and a Kubernetes deployment. Apache-2.0 licensed.