ccc-ao

/ao — Composio Agent Orchestrator

Wraps the ao CLI (@composio/ao). Spawns parallel agents across projects with git worktree isolation.

When activated:

Check if ao CLI is available:

which ao

If not found, display:

ao CLI not installed.
Run: npm i -g @composio/ao
Then re-invoke /ao once installed.

If found, check the version:

ao --version

Then present via AskUserQuestion:

Option	What it does
Spawn agents on current project (Recommended)	Ask: how many, what tasks, model selection
Spawn from config file	Read agent-orchestrator.yaml, show configured projects
Check running agents	Run ao status — show active sessions
Stop agents	Run ao stop — kill running sessions
Something else	Free text

Spawn Flow

When user picks "Spawn agents on current project":

1. Ask number of agents via AskUserQuestion:

   • 2 agents
   • 3 agents
   • 5 agents
   • Custom number

2. Ask model via AskUserQuestion:

   • Claude (Recommended)
   • Codex
   • Aider
   • OpenCode

3. Ask task assignment strategy via AskUserQuestion:

   • One shared task (agents collaborate on the same goal)
   • One task per agent (assign a separate task to each agent)
   • Auto-split from description (describe overall goal, split automatically)

4. Collect task(s) — one per agent if individual, or one overall goal if auto-split.

5. Run the spawn command:

   ao spawn --agents [n] --model [model] --task "[task]" --worktree
   

6. Show spawned summary:

   ao spawn complete
   Agents: [n] | Model: [model] | Worktree: isolated
   Task(s):
     Agent 1: [task]
     Agent 2: [task]
     ...
   

Spawn from Config File

When user picks "Spawn from config file":

1. Check for config:

   ls agent-orchestrator.yaml 2>/dev/null || ls .ao/config.yaml 2>/dev/null
   

2. If found, read and display the configured projects and agents.

3. Ask which project/config to run via AskUserQuestion.