teamlisted

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.
ethanhq/cc-fleet · ★ 142 · AI & Automation · score 86

Install: claude install-skill ethanhq/cc-fleet

# team — long-lived provider teammates Run a third-party provider model as a real Claude Code teammate in a tmux pane: same tool stack and team coordination as a native teammate, LLM backend swapped to the provider. Your main session's own auth stays untouched. **Wrong lane?** A fire-and-forget one-shot or flat batch → /cc-fleet:subagent; a scripted multi-phase run → /cc-fleet:workflow; full arbitration in cc-fleet-shared/routing.md. When this skill cites `cc-fleet-shared/<file>.md`, OPEN it with the Read tool at `../cc-fleet-shared/<file>.md` relative to this SKILL.md — the cited content is load-bearing, not optional background. **Precondition — agent-teams must be ON:** check your own tool list for `SendMessage` / `TeamCreate`; absent → do NOT spawn (an unmessageable pane bills the provider with no work) — enablement + fallback in cc-fleet-shared/routing.md. --- ## Core loop Steps 1, 3, 6 are **native tools**; steps 2, 5, 6a are `cc-fleet` via Bash with `--json`. ``` 1. TeamCreate({team_name: "<team>"}) ← native, FIRST — the main session becomes the lead 2. cc-fleet spawn [<provider>] --as <name> --team <team> [--model <slot|id>] --json ← Bash; check ok:true, grab .pane_id / .agent_id The provider arg is OPTIONAL — omitted, the default provider applies (see "The provider ask ladder"). Full flag table: cc-fleet-shared/cli-reference.md. 3. SendMessage({to: "<name>", message: "<task>. When done, send your result back with SendMessage."}) ← native; a