fleet

Dependency-aware multi-stage orchestration of parallel sessions. Spawn stage 1 in parallel; the always-on rules engine then spawns stage 2 once stage 1 is all done, stage 3 once stage 2 is done, and so on. The skill itself returns immediately — chains survive the chat session ending. Use when the user says "fleet chain", "/fleet:chain", "spawn A then B", "after BDP-N finishes spawn BDP-M", or any phrasing about multi-stage orchestration of sessions.

Find sessions in the multi-session command center whose PRs have already merged on GitHub, and kill+cleanup each (with confirmation). Closes the loop on "spawn → ship → tidy up" without manual bookkeeping. Use when the user says "fleet cleanup", "/fleet:cleanup", "kill the merged sessions", "tidy up", "sweep done agents", or any phrasing about reclaiming finished sessions.

Spawn a dedicated reviewer session for a given session's open PR. The reviewer agent reads the diff, posts inline + summary review comments on GitHub, then exits. Works two ways — invoked by you in chat against any open PR, or invoked autonomously by an implementer session (auto-detects parent and ties the reviewer in as a child). Use when the user says "fleet review", "/fleet:review", "spawn a reviewer for BDP-N", "have someone review BDP-N's PR", or when an implementer session has just opened its PR and wants a second LLM pair of eyes.

Install thin wrappers in ~/.local/bin/ so the fleet plugin's public CLIs (claude-sessions, claude-sessions-web, spawn-claude-feature) are callable from the user's interactive zsh / bash, not just from the Claude Code tool host. The wrappers resolve to the latest installed plugin version at exec time, so they survive `/plugin update`. Idempotent — re-running it overwrites stale wrappers but refuses to clobber foreign files at the same path. Use when the user says "setup cli", "/fleet:setup-cli", "claude-sessions: command not found", "put fleet on my PATH", "wire up the fleet wrappers", or any phrasing about getting the fleet CLI onto an interactive shell PATH.

Spawn one or many parallel Claude agents on Jira tickets, with full-auto mode and Jira-aware prompt construction. Single-ticket form replaces a manual bytedesk-feature-start when you already know the ticket; multi-ticket form fires N sessions in parallel ("kick off the whole sprint"). Use when the user says "fleet spawn", "/fleet:spawn", "kick off these tickets", "spawn agents for", "/fleet:spawn BDP-N BDP-M", or any phrasing about launching one or more sessions from existing Jira tickets.

Chat-friendly snapshot of the multi-session Claude command center. Shows every running agent grouped by state (working / needs-input / error / done / idle), with branch, last activity, and a one-line peek at what each is currently doing. Use when the user asks "what's my fleet doing", "fleet status", "what are my agents working on", "/fleet", or any phrasing about checking the parallel-session dashboard.

Spawn N variant agents on the same Jira ticket, each with a different strategy hint, then auto-spawn a judge that reads all the resulting PRs and merges the best one. Recursive orchestration — implements the variants pattern from the Multi-Session Claude roadmap (#5.1). Use when the user says "fleet tournament", "/fleet:tournament", "spawn N variants on BDP-X", "tournament for BDP-X", "race variants", or any phrasing about parallel-strategy A/B/C-testing on a single ticket.

Block until one or more sessions reach a target state (default done). Closes the no-event-callback gap in the multi-session system — anything that needs to react when an agent finishes uses this. Use when the user says "fleet wait", "/fleet:wait", "wait until BDP-N is done", "wait for these to finish", or any phrasing about pausing for sessions to reach a state. Also called internally by /fleet:chain, /fleet:cleanup, and /fleet:review.

2 hooks across 2 events

Polls fleet sessions for state transitions, ceiling breaches, and tool-level events; dispatches notifications via desktop / bell / fifo / slack per ${CLAUDE_PLUGIN_DATA}/projects/<KEY>/notify/config.toml.

Per-project HTTP dashboard server. Hash-based port assignment under ${CLAUDE_PLUGIN_DATA}/projects/<KEY>/web/config.toml; PID lock + stand-by polling so multiple Claude Code sessions in the same project coordinate cleanly. Discovery via `claude-sessions web` (no args) which prints the URL.