dispatch

# Orchestrating agents with `ccmux invoke` You are the orchestrator. ccmux gives you one uniform CLI that launches and observes every harness the same way (claude, codex, cursor, opencode, pi, gemini, plus custom agents). This skill teaches the **mechanics** of driving those workers. It is deliberately generic: the **agent-per-task policy comes from the user's prompt** ("plan with claude, implement with codex, search with gemini"), not from this file. Your job is to apply judgment to that policy and thread results between steps. ccmux never runs a model itself, not even to summarize a worker's output. Digesting a large result is your job (prompt the worker for brevity, or spawn a cheap summarizer over its full output). Keep that in mind throughout: the discipline that keeps an orchestration tractable is controlling how much each worker hands back. ## When to use - The user names a multi-agent workflow ("plan with X, implement with Y, search with Z"). - You need to fan a task out across several agents and combine their answers. - You want to delegate a long task to another agent without blocking your own work. - You want a second agent's independent take (review, verify, alternative implementation). ## When NOT to use - A single quick turn you can run inline: just `ccmux invoke <agent> "..."` once; you don't need the fire-and-poll machinery below. - Work you should do yourself. Delegation costs a cold start (5-15s) plus the worker's own round-trip; don't farm out wha...