Queue the work. Claude works on it.
A local task board for Claude Code. Add tasks, drag them into the queue, and Claude picks up
the next one. Everything runs on your machine — no accounts, no cloud, nothing left running.
Requires Bun 1.3 or newer (curl -fsSL https://bun.sh/install | bash).
In Claude Code:
/plugin marketplace add yeahitsmejayyy/command-center
/plugin install command-center@command-center
There is no compile step and nothing is downloaded at runtime. Before you install it, SECURITY.md says exactly what it runs, reads, and writes — worth two minutes for anything that hooks your sessions.
Start a session in a project. command-center offers to set it up; run /command-center:enable and the board opens in your browser.
From there:
- Add tasks on the board — a title, instructions for Claude, and any files worth attaching. Drag them into Queue when they're ready.
- Run
/command-center:start. Claude takes the next queued task and works it. The board follows along. - Review. Finished work lands in In Review. Approve it, or send it back for another pass.
The board and the session stay in step in both directions: what Claude does shows up on the board, and what you drag on the board is what Claude picks up next.
| In Claude | |
|---|---|
/command-center:enable |
Use command-center in this project |
/command-center:skip |
Leave this project alone |
/command-center:start |
Start the next queued task |
| In a terminal | |
|---|---|
cmc list |
Show the board (--json for scripting) |
cmc add "…" |
Add a task (--body, --plan, --queued) |
cmc advance / finish / approve / revise |
Work the queue by hand |
cmc doctor |
Diagnose problems, with the fix for each |
cmc cleanup |
Stop an unused board server |
Run cmc doctor first. Every failure it knows about has a name and a command that fixes it.
| Symptom | Cause | Fix |
|---|---|---|
| No board when a session starts | Project not enabled | /command-center:enable |
| "command-center needs Bun" | Bun missing, or not on the hook's PATH |
curl -fsSL https://bun.sh/install | bash, then restart the session |
| Board says "Server not responding" | The server stopped; the port is gone | Reload — a new session starts a fresh one. Or cmc cleanup |
| Board is stale or empty | State file unreadable | cmc doctor prints the path and the command to move it aside |
Nothing happens on /command-center:start |
Nothing queued, or a task is already running | The command says which |
Logs are per project: cmc doctor prints the path.
No database — JSON files under a lock. No daemon — servers live and die with your sessions. Loopback only. One task in progress at a time, on purpose.
- SECURITY.md — what it touches, what it writes, and how to audit it yourself
- docs/architecture.md — the state machine, the layer boundaries, the on-disk layout
- docs/decisions/ — why the significant calls were made, and what was weighed against them
- docs/build-log/ — how it was built, in order, including what broke
- CHANGELOG.md — what changed in 2.0.0, and how to migrate from v1
Licensed under MIT.