From Fleet Deck
Shows the Fleet Deck board URL and a live summary of every Claude Code session on this machine, grouped by status with conflict and mail status.
How this command is triggered — by the user, by Claude, or both
Slash command
/fleetdeck:fleetThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
## Fleet state (raw)
!`TOKEN=$(cat "${FLEETDECK_HOME:-$HOME/.fleetdeck}/token" 2>/dev/null); curl -sf -m 2 ${TOKEN:+-H "Authorization: Bearer $TOKEN"} http://127.0.0.1:4711/state || echo FLEET_DAEMON_DOWN`
## Your task
Report on the fleet using ONLY the raw state above. Print exactly this, nothing more:
If the raw state is `FLEET_DAEMON_DOWN` (or empty / not JSON):
> Board: http://127.0.0.1:4711/
> fleet daemon not running — it starts with your next session
Otherwise a compact summary (aim for under 15 lines):
1. `Board: http://127.0.0.1:4711/`
2. Sessions grouped by column, in this ...!TOKEN=$(cat "${FLEETDECK_HOME:-$HOME/.fleetdeck}/token" 2>/dev/null); curl -sf -m 2 ${TOKEN:+-H "Authorization: Bearer $TOKEN"} http://127.0.0.1:4711/state || echo FLEET_DAEMON_DOWN
Report on the fleet using ONLY the raw state above. Print exactly this, nothing more:
If the raw state is FLEET_DAEMON_DOWN (or empty / not JSON):
Board: http://127.0.0.1:4711/ fleet daemon not running — it starts with your next session
Otherwise a compact summary (aim for under 15 lines):
Board: http://127.0.0.1:4711/working (2): NOVA — fleetdeck (main) · editing derive.mjs, ... using each session's callsign, repo_name, branch, and note/task when present. Skip empty columns; summarize offline as a count only (e.g. offline: 3).conflicts is non-empty, one line per conflict: ⚠ <rel_path> — <severity> — sessions: <callsigns or ids>. Otherwise conflicts: none.mail_pending > 0: mail: N queued — delivered at the next turn boundary. Otherwise omit the line.npx claudepluginhub lacion/fleet-deck --plugin fleetdeck/gm-statusChecks the current state of operations by querying daemon status, listing tasks, and agent sessions, then produces a concise summary report.
/team-statusDisplays real-time status of the Company Model team, including task board, git worktree changes, and potential conflicts. Produces a formatted report with actionable recommendations.
/sprint-statusReports status across all active Claude Code sessions, detecting parallel branches and tasks, then compiling a sprint view with COMPLETE, BLOCKED, or NEEDS_INFO statuses.
/f5-statusDisplays F5 Framework project status dashboard, runs health checks (doctor mode), and self-diagnostics (selftest mode). Supports --verbose, --fix, suite options.
/sessionsLists active Claude Code sessions across terminals, showing branch and task for each. Also supports cleaning stale sessions and grounding the current session with git and project context.