cao
v2.5.3Drive CLI Agent Orchestrator multi-agent sessions from any Agent-Plugins-compatible client. Prerequisites: the `uv` toolchain must be on PATH (the MCP server is launched via `uvx`), and a CAO API server must be running locally at http://127.0.0.1:9889 (`cao-server`). All communication is localhost-only.
License: Apache-2.01.4k GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code and Agent Plugins
- Parsed components
- 5 skill or MCP entries
- Source updated
- Oct 8, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install cao for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install cao@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/awslabs/cli-agent-orchestratorClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is agent-plugin/cao/.
Plugin files
├── .claude-plugin/plugin.json├── plugin.json├── skills/cao-agent-routing/SKILL.md├── skills/cao-session-management/SKILL.md├── skills/cao-supervisor-protocols/SKILL.md├── skills/cao-worker-protocols/SKILL.md└── .mcp.json
Included Skills4
Find and select the best installed CAO agent profile for a task before delegating with assign or handoff. Use when a supervisor needs to route coding, documentation, infrastructure, review, research, or other specialist work and the user has not already chosen an agent profile.
Interact with CAO (CLI Agent Orchestrator) — launch multi-agent sessions, check status, send follow-up instructions, unblock stuck terminals, or shut down sessions. Use when working with CAO sessions in any capacity.
Supervisor-side orchestration patterns for assign, handoff, and idle inbox delivery in CAO
Worker-side callback and completion rules for assigned and handed-off tasks in CAO
MCP servers1
- command
- uvx
- args
- --from cli-agent-orchestrator==2.5.3 cao-ops-mcp-server
Plugin manifests2
{
"name": "cao",
"version": "2.5.3",
"description": "Drive CLI Agent Orchestrator multi-agent sessions from any Agent-Plugins-compatible client. Prerequisites: the `uv` toolchain must be on PATH (the MCP server is launched via `uvx`), and a CAO API server must be running locally at http://127.0.0.1:9889 (`cao-server`). All communication is localhost-only."
}{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "cao",
"version": "2.5.3",
"description": "Drive CLI Agent Orchestrator multi-agent sessions from any Agent-Plugins-compatible client. Prerequisites: the `uv` toolchain must be on PATH (the MCP server is launched via `uvx`), and a CAO API server must be running locally at http://127.0.0.1:9889 (`cao-server`). All communication is localhost-only.",
"repository": "https://github.com/awslabs/cli-agent-orchestrator",
"license": "Apache-2.0",
"keywords": [
"orchestration",
"multi-agent",
"cao",
"tmux"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[cao on Agent Plugins Marketplace](https://pluginsmp.com/plugins/cao)