abreu4

Fleet Dashboard — Development skill for Claude Code

Development community

A live board of every coding-agent session on your Mac — Claude Code, Codex, Antigravity — what each is doing and waiting on, beside the machine's vitals.

How to install Fleet Dashboard

This entry records only its repository, not the path inside it, so there is no exact command to give. Open abreu4/fleet-dashboard and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Fleet Dashboard does

A live board of every coding-agent session on your Mac — Claude Code, Codex, Antigravity — what each is doing and waiting on, beside the machine's vitals. In-page terminals, a per-run graph window, 26 themes. Reads what the agents already write to disk; nothing to install in them.

Alternatives in Development

Continuous Claude — Run Claude Code in a continuous loop, autonomously creating PRs, waiting for checks, and merging 1.3k ★
Opencove — Your infinite canvas workspace for agents, tasks, knowledge, and research 1.2k ★
Agentlas Login — Sign this machine into Agentlas (opens the browser sign-in window) 1.1k ★

README

Fleet Dashboard

**One screen for every coding-agent session on your Mac.**

![The board in the default console theme: the HUD along the top, one lane per agent, one tile per session](docs/img/board-console.png)

Claude Code, Codex and Antigravity sessions, grouped by agent and project, each with what it was asked to do and where it has got to — beside the machine's own vitals. It is built to sit fullscreen on a second screen and be read from a metre away while something else has your attention.

Nothing is installed into the agents. The board is assembled from what they already write to disk — transcripts, job files, SQLite rows, the process table — so no session has to report on itself, and no line on the board was summarised by a model on demand.

What you get

**The board** — one tile per session: its name, what it was asked, and what it is doing now. Status colours are fixed across every theme: *blocked* red, *running* green, *idle* blue, *done* amber. Lanes and projects grow with the work in them, so the busy corner of the fleet takes the room.
**The HUD** — sessions live, tokens per minute, the open five-hour Claude usage window, the fullest context on the board, memory pressure, and what got finished today. Optional panels (cpu / gpu / memory trace) switch on in settings when the screen has room.
**Terminals in the page** — real shells in a docked sheet, one tab each: open a shell in any session's folder, attach to or resume a session, drag tabs to reorder. Loopback only, token-gated.
**The graph window** — one run's trail, drawn live: a spine of model responses, the files it read above, the files it changed below, your prompts as rings. Lazy — read only when you open it.
**26 themes** — a plain console, paper, neutral… and then Portal, Skyrim, Doom, LCARS, Severance, a corporate intranet and more, each an instrument panel over the same numbers.

![The same board as LCARS: the status line along the foot carries the st