awslabs

cli-agent-orchestrator: Coordinate AI Coding Agents

CLI Agent Orchestrator runs AI coding CLIs in isolated tmux sessions and gives a supervisor tools to delegate work to specialist agents. It suits developers who want to coordinate parallel or sequential coding tasks while keeping each agent’s native CLI.

Stars
1.4k
Forks
285
Stars, last 15 days
+65

Our take

Health score

75/100

How it is scored
Activity
79
Community
85
Issues
73
Pull requests
62

+65 stars in the last 15 days

  • Merges more pull requests than 89% of the projects we track

Overview

CLI Agent Orchestrator (CAO) is a local orchestration layer for AI coding command-line tools. It starts provider CLIs in isolated tmux sessions and lets a supervisor coordinate specialist agents, rather than replacing those agents or their native authentication and capabilities.

It is useful when a single coding assistant is not enough for a task that can be split across workers, or when a team wants to manage agent sessions through a CLI, web interface, or integrations. See the official repository and documentation for details.

Key Features

  • Coordinates multiple coding agents in parallel or in sequence.
  • Runs provider CLIs as full processes in isolated tmux sessions.
  • Supports multiple providers, including Claude Code, Kiro, Codex, GitHub Copilot CLI, Cursor CLI, and others.
  • Provides a local server and supervisor workflow for launching and managing agents.
  • Offers several control surfaces, including a shell CLI, Web UI, and operations MCP server.
  • Includes workflows, scheduled runs, reusable skills, and persistent cross-session memory.
  • Documents HTTP API and PTY WebSocket interfaces for integrations.

Use Cases

  • A developer can delegate separate implementation tasks to specialist agents and coordinate their results from a supervisor.
  • A team can run coding agents against a project in isolated terminal sessions when it needs to inspect or manage each agent independently.
  • Operators can build multi-step or scheduled agent workflows for recurring development tasks.
  • Teams managing multiple repositories can use the documented AI-DLC portfolio example to coordinate parallel intents across repositories and isolated worktrees.

Getting Started

Install the current main branch with uv:

uv tool install git+https://github.com/awslabs/cli-agent-orchestrator.git@main --upgrade

Then follow the README for setup and launch instructions.

Alternatives

  • ruflo: Ruflo is a TypeScript harness for Claude Code and Codex, with persistent memory and workflow automation, rather than a Python tmux-based CLI supervisor.
  • clowder-ai: Clowder adds agent roles, shared memory, and peer review for multiple coding CLIs, while cli-agent-orchestrator delegates through isolated tmux sessions.
  • oh-my-claudecode: oh-my-claudecode focuses on orchestrating Claude Code workers through in-session skills or terminal launches, rather than supporting a general CLI supervisor.
  • claude-code-by-agents: Agentrooms coordinates coding agents in a macOS app across local and remote machines, using @mentions and threaded rooms instead of a CLI supervisor.
ProjectLanguageLicenseStarsStatus
cli-agent-orchestratorPythonApache-2.01.4kNot checked yet
rufloTypeScriptMIT73.8kActive
clowder-aiTypeScriptMIT3.3kActive
oh-my-claudecodeTypeScriptMIT39.6kActive
claude-code-by-agentsSwiftMIT892Quiet

Considerations

CAO requires Python 3.10 or later, tmux 3.3 or later, uv, and at least one supported provider CLI authenticated before launch. The provider CLIs remain separate dependencies, so users need to install and configure their chosen provider. CAO coordinates agents but does not remove the need to supervise their work. The repository is not archived, and its license is Apache-2.0.

Found this useful?

Share it with someone who would like cli-agent-orchestrator.

Comparisons