Fleet Deck

Fleet Deck ⚡

Mission control for every Claude Code session on your machine.

You know how it goes. You start one Claude Code session. Then one in a worktree, because you're organized. Then a third one "just to look something up," and a fourth because the second one seemed stuck. It is now 6 PM, two of them are editing util.js at the same time, one has been silently waiting forty minutes for you to approve rm -rf node_modules, and you honestly could not say which terminal tab is which.

Fleet Deck is the air-traffic control tower for that situation.

Every session on the machine appears on one local board — http://127.0.0.1:4711 — with a callsign (falcon-a3f2, otter-91c4, or raven-PROJ-123 when it's working a Jira ticket... yes, the banner is literally the roster), a live column derived from what it's actually doing, and a mailbox. Sessions get whispered at when they're about to trample each other's files. Questions land in an amber rail you can answer from across the room. And when you're feeling ambitious, the board will spawn new workers, route tasks to whoever's idle, and file their plans in a library.

What it does

• See everything. queued → working → verifying → needs-you → idle → offline, derived from hook telemetry — never self-reported, because sessions, like people, believe they are almost done. The model badge is derived the same way: Claude Code only reports the model at startup, so Fleet Deck reads it from the session transcript instead and the badge follows a mid-session /model switch rather than freezing on whatever the session happened to launch with.
• Conflict radar. Two sessions touching the same file within 30 minutes get warned in context ("coordinate, don't clobber"), the board flashes hazard-red, and yes, it's worktree-aware — the same file edited in two worktrees of one repo is a merge conflict introducing itself early.
• Needs-you rail. Permission prompts, multiple-choice questions, MCP forms, and trailing "should I use bcrypt or argon2?" questions all become cards you answer from the board. The terminal never even asks — it just prints ⎿ Allowed by PermissionRequest hook and carries on, slightly smug.
• Mail with honest latency. Message any session, a whole repo, or everyone. Delivered at the next turn boundary — idle sessions usually wake within seconds (a small watcher taps them on the shoulder). The board never promises "instant," because we don't lie to you, even about milliseconds.
• An orchestrator with no brain, on purpose. assign auto: fix the flaky test picks the best candidate — idle first, least buried, right repo — with a SQL query, not a model call. The core makes zero model calls. Your tokens are yours.
• A dynamic fleet. The + Spawn button starts a fresh interactive claude in a daemon-owned tmux window. Watch it work on the board, attach to the pane if you're nostalgic for terminals, kill it when it's done (there's a confirm; we've all misclicked).