lacion/fleet-deck

README preview

<p align="center">
  <img src="docs/assets/banner.png" alt="The Fleet Deck crew at their stations." width="100%">
</p>

# Fleet Deck ⚡

[![CI](https://github.com/lacion/fleet-deck/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/lacion/fleet-deck/actions/workflows/ci.yml)
[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
[![Bun ≥ 1.3.14](https://img.shields.io/badge/bun-%E2%89%A5%201.3.14-brightgreen.svg)](https://bun.sh)

**One reliable control plane for every Claude Code session on your machine.**

Run more than two or three Claude Code sessions and you lose track of them: which terminal is which, which one is blocked on a permission prompt, and which two are editing the same file. Fleet Deck puts all of them on one local board at **http://127.0.0.1:4711**, with a callsign, a live status column, and a mailbox each.

Fleet Deck is deliberately an accessory, never a dependency of the developer loop. If its daemon,
board, network, or hooks are unhealthy, Claude Code must remain usable from the terminal. That rule is
the reliability boundary every feature below is built around.

<p align="center">
  <img src="docs/assets/fleet-deck-demo.gif" alt="The board: four agents working one repo in separate worktrees, cards moving between columns as each turn lands, and the conflict radar flaring when two of them touch the same file." width="100%">

View full repository on GitHub →