awslabs/cao
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.
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.
Find available CAO (CLI Agent Orchestrator) agent profiles, and talk to the conductor and worker terminals of a running CAO session, including unblocking a stuck worker. Use when choosing a profile to launch, messaging or unblocking workers, or diagnosing a stuck session. For preflight, launching, session commands, statuses, delegation and safety, run cao --skill first.
Coordinate, delegate, and split work across CAO worker agents as a supervisor — choose between assign (async fire-and-forget) vs handoff (sync wait-for-result), fan out tasks to parallel specialists, manage idle-based inbox delivery, or debug why worker callbacks aren't arriving. Covers dispatch patterns, result collection, and multi-agent orchestration planning. Not for worker-side task execution, creating skills, managing plugins, or session lifecycle (cao launch/shutdown).
Worker-side callback and completion rules for assigned and handed-off tasks in CAO