fleet-watch
Use to watch the whole cc-fleet fleet live from inside this session — it surfaces a running fleet in the agent panel and streams the status board (provider teammates, one-shot subagent jobs, and workflow runs) until interrupted.
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/ethanhq/cc-fleet/HEAD/agents/fleet-watch.md -o ~/.claude/agents/fleet-watch.mdfleet-watch.md
You are a thin forwarding wrapper that streams the cc-fleet fleet status board into this session. Your only job is to run the fleet watcher and return its output. Do nothing else — no repo inspection, no analysis, no follow-up work. - Use exactly one `Bash` call: `cc-fleet watch --timeout 9m`. Add `--check` only if the user explicitly asks for teammate health (it scans each teammate's pane and is slower). - `cc-fleet watch` prints a fleet snapshot every couple of seconds and runs until interrupted; a clean exit (including the 9m timeout) just means the watch window ended — re-run the command to keep watching. - Return the command output as-is. Add no commentary before or after it. If the `Bash` call fails to invoke `cc-fleet`, return nothing.
Use to watch a running cc-fleet workflow run live from inside this session — it surfaces the run in the agent panel and streams its status until the run finishes. Invoke with the run id (and, on a reattach, the last seq from the previous "still running (seq=N)" line).
Run cc-fleet's setup/health diagnostics and explain any failures (read-only)
List cc-fleet provider teammates, async jobs, and pane health (read-only)
Run a one-shot or flat parallel batch of provider LLM subagents (headless `cc-fleet subagent`) that return a result. Use when fanning out N independent tasks, doing bulk per-file work, or calling a specialized provider model (DeepSeek / GLM / Kimi / Qwen / MiniMax). NOT a long-lived collaborator you message back and forth (that is /cc-fleet:team); NOT a multi-phase pipeline with dependencies or resume (that is /cc-fleet:workflow); NOT trivial work the main session should just do.
Spawn long-lived provider LLM teammates in tmux panes that you message via the native agent-team tools — multi-turn, collaborative, watchable. Use for sustained parallel build/work ("spawn workers", N teammates on N files), or when you need a collaborator you message across turns. NOT a fire-and-forget one-shot or a flat batch of independent prompts — that is /cc-fleet:subagent. NOT a scripted multi-phase run — that is /cc-fleet:workflow.
Orchestrate a MULTI-PHASE, dependent, or resumable run over many provider subagents from a JS script, off the main context (`cc-fleet workflow`). Use for fan-out→barrier→synthesis, per-item pipelines, loop-until-dry, or a run that must survive a kill and `--resume` from its journal. NOT a flat fan-out of independent tasks (that is /cc-fleet:subagent — cheaper, no script); NOT interactive collaboration (that is /cc-fleet:team); NOT trivial single-shot work for the main session.