CCC
Your coding agents outgrew your terminal.
CCC puts every session on one local board and tells you which one needs you.
Start the next while Claude builds the first.
One local dashboard that attaches to every Claude Code, Codex, Cursor, Antigravity, Kilo Code, and Kimi Code session on your machine, however you launched it. Spawn, monitor, and ingest all six; steer five of them with follow-up. Local, source-available, free for non-commercial use.
📢 Shipping fast. Watch → Releases (top-right) to get pinged on new versions without the noise.
Install with curl:
curl -fsSL https://raw.githubusercontent.com/amirfish1/claude-command-center/main/scripts/install.sh | CCC_FROM=readme bash
With Homebrew:
brew tap amirfish1/ccc
brew install ccc
ccc
Or download the macOS DMG and drag CCC.app to Applications:
github.com/amirfish1/claude-command-center/releases/latest
Try the read-only demo first: ccc.amirfish.ai/demo (or amirfish1.github.io/claude-command-center/demo) - full kanban with seeded fake data, no install required.
See CCC at work
Scan every coding-agent session, then open the one that needs you.
Organize projects and sessions on the Flow canvas.
Move work across the kanban, then jump into its session.
All captures use seeded demo data.
CCC latches onto every Claude Code, Codex, Cursor, Antigravity, and Kilo Code session on your machine: terminal sessions, headless processes, and sessions you spawned from the dashboard. It treats each agent's on-disk state as the source of truth, so nothing slips through. Spawn the next task while the first is still building. Switch between projects without losing context. Ship multiple things at once.
See the engine support matrix below for what each engine does. Spawn, monitor, and transcript ingestion work across all six; follow-up (steering a dormant session) works on five (Kilo Code is fire-and-forget), and Cursor IDE sync is metadata-only by design.
What you get
See your whole fleet, past one session. The way you build faster is a session per workstream: one on the feature, one on its go-to-market, one on the next feature, one on research. CCC puts every model and engine on one board, every row enriched so you read status without clicking in: a needs-you signal, live context left, a cost tier, and, with the Token Optimizer plugin, a quality score. Pin strategy sessions, nest workers under them, group by project, or lay the whole fleet out on a canvas.
Stop wasting tokens, keep quality where it matters. Your best model leads; execution fans out to cheaper models, or another platform entirely, through spawns, queues, and workers you point at any engine. CCC shows your pace against your plan's limits before you hit the wall, attributes a spend spike to the exact session or automation that caused it, and flags sessions running on a tier they don't need.
Sessions that exchange context on their own. Two sessions on one goal stay in sync through group chats and a sibling-ask API, instead of you reading one agent's output off one screen and retyping it into the other. Post once and every participant is pinged; ask a sibling synchronously when you need an answer right now; hand a problem to a fresh spawned session that reports back when it finishes.
Workers that specialize over time. Each worker reads its queue's shared learnings file before it starts and writes back to it when it ends, so a queue handling the same kind of ticket for months keeps getting faster and more accurate, not just busier. Ships via WatchTower, which CCC installs on first launch as its queue engine — Python 3.11+, and CCC still starts (on a reduced built-in queue) if the install doesn't take.
Find anything, from any session. The problem you solved two weeks ago in some other session, found in seconds instead of solved again: full-text search across your session history, built in, zero setup, with an optional deeper semantic mode for when you can't remember the words you used. Covers Claude Code and Codex today.
Work from anywhere. Two sides of one opt-in: your phone as a client to the fleet, and CCC installed on any machine you can reach, a VM or a home server, open in any browser on your trusted network. Loopback by default, never the open internet.
Why this exists
Most Claude Code orchestration tools are opinionated wrappers. They want to
own execution. You launch agents through them, and in return you get a
dashboard. That's fine until it isn't. The moment you open a terminal,
claude --resume something, and iterate on it by hand, you're outside the
tool's universe. The dashboard can't see it. The work you just did doesn't
show up on the kanban, against the issue, in the review queue.
This goes the other way. It treats Claude Code's on-disk state as the
source of truth: ~/.claude/projects/*.jsonl transcripts, the
~/.claude/sessions/<pid>.json live registry, and per-tool-call sidecar
files written by two hooks we install into ~/.claude/settings.json. If
Claude Code is running anywhere on your machine, it shows up here. If you
close the dashboard, your sessions keep running. If you open a terminal and
iterate by hand, the card updates.
The dashboard also knows how to spawn headless sessions (via
claude -p --input-format stream-json) and resume dormant ones on demand,
but those are additive. The thing it's built around is attaching to work
that already exists.
How it compares
| Raw terminal + tmux | Wrapper that owns execution | CCC | |
|---|---|---|---|
| Sees sessions you launched by hand | if you remember the tab | no, only what it spawned | yes, reads on-disk state |
| Survives closing the dashboard | yes | varies | yes, the dashboard is a lens, not a runtime |
| One board across engines | no | usually one engine | yes, six engines |
| Tells you which session needs you | no | no | yes, read from the transcript |
| Coordinates sessions without you as the relay | no | no | yes, group chats + sibling-ask |
| Setup | none | proxy or routing config | one curl line, no accounts |
The whole point is the first row: the moment you touch a terminal, a tool that owns execution goes blind. CCC reads the state the engines already write, so it never does.
Recent
- 2026-07-20: v5.9.0. Kimi Code joins as the sixth engine (spawn, steer, live token streaming, guided setup in Settings). Plus a FIRST FLIGHT onboarding tour, a searchable full settings modal (Cmd/Ctrl+,), a cost-aware cold-session composer that offers ranked cheaper routes instead of a blind expensive resume, a 12-skill orchestration pack, plan-to-fleet queue import, and a perf pass that gets new sessions into the list in seconds.
- 2026-06-25: v5.4.0. Project tree: the "By objects" sidebar now splits a live "Current sessions" triage band over a hierarchical map of your day, sessions grouped under nestable, draggable Flow objects. Plus a new
/api/sessions/eventsSSE stream (subscribe to session-state changes instead of polling) and a broad Codex, sidebar, and Total Recall search polish wave. - 2026-06-03: v4.6.0. Major performance pass: the dashboard idles instead of pinning a CPU core, group-chat opens ~40x faster, long conversations open near-instantly (windowed load + scroll-up to load earlier), and Codex sessions with screenshots no longer stall on multi-MB images. New CCC self-health readout in the footer.
- 2026-05-21: v4.0.0. Antigravity (Google DeepMind) joins the dashboard as a first-class engine alongside Claude Code and Codex.
- 2026-05-21: Drag any conversation row outside the window to pop it into a focused side pane, with 24 per-conversation accent colors.
- 2026-05-19: Template gallery mechanism for reusable new-session prompts, driven by
static/templates.json. (#46) - 2026-05-19: VS Code extension v0.1.0 published, spawn a session from the active workspace folder. (#52)
- 2026-05-19: One-command
curl | bashinstaller;git clonedemoted to a "From source" section. (#58) - 2026-05-19: Static GitHub Pages demo with seeded mock data (no install required). (#49)
- 2026-05-18: Local macOS
saytext-to-speech button on conversations.
If you install it, I'd love to hear how. Drop a ⭐, open an issue with what worked or what broke, or j