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, Kimi Code, OpenCode, and Devin session on your machine, however you launched it — plus read-only ingestion of GitHub Copilot CLI, VS Code Copilot Chat, and Grok CLI sessions. Spawn, monitor, and ingest all eight; steer seven 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) - the full dashboard with seeded fake data, no install required.

See CCC at work

One board, eight engines

Every Claude Code, Codex, Cursor, Antigravity, Kilo Code, Kimi Code, OpenCode, and Devin session lands on one board — however you launched it. CCC reads each engine's on-disk state, so even sessions you started by hand in a terminal show up.

Flow canvas & Project tree

Group sessions under named, nestable Flow objects — a hierarchical map of your day's work, with a live "Current sessions" triage band riding on top.

Split conversations

Drag any session onto the edge of an open transcript to read two agents side by side — each pane keeps its own input bar.

Find anything, from any session

Full-text search across your entire session history, built in and zero-setup — with an optional semantic mode for when you can't remember the words you used.

Sessions that coordinate without you

Group chats keep two sessions on one goal in sync — post once and every participant is pinged, instead of you relaying output between terminals.

Issue → session → verify

Start a session from a GitHub issue in one click; verifying closes the issue with a commit-SHA comment. The whole pipeline lives on the board.

Tells you which session needs you

Approvals, questions, and blocked ends are read straight from the transcript and surfaced as a needs-you signal — scan one column instead of nine terminals.

Work from anywhere

The whole fleet on your phone — monitor sessions, answer agents, and steer from anywhere on your trusted network. Loopback by default, never the open internet.

Also in the box:

• Durable queues with workers that specialize over time — WatchTower queues carry a shared learnings file each worker reads before and writes after; an all-queues inbox, per-queue AI status briefs, and one-click "create a queue for this session" included.
• Answer permission prompts from the dashboard — Claude Code's approve/deny prompts surface inline; CCC never interrupts a possibly-mid-turn session without your Approve.
• Board view (kanban, optional) — drag-drop columns derived from session state, with rubber-band multi-select. The list is the primary surface; the board is an opt-in lens.
• System status — a health modal over the whole fleet: restart-all, spawned-process cleanup, delivery receipts.
• Cost-aware cold-session composer — ranked cheaper routes (continue fresh on a lower tier, search history) instead of a blind expensive resume.
• FIRST FLIGHT tour — a spotlight walkthrough on first run, replayable any time from Settings.
• Settings modal — instant search (Cmd/Ctrl+,), keyboard navigation, per-section reset.
• Plan-to-fleet — import a plan or mission brief into a WatchTower queue and drain it with workers.
• Fresh worktree spawns — launch a session in <repo>-wt/<slug>/ on feat/<slug>, with optional init scripts.
• Headless spawn with follow-up — claude -p sessions you keep talking to from the browser, no terminal needed.
• Resume-on-demand — messaging a dormant session auto-spawns a headless resume to deliver it.
• Auto-fix deploys — polls Vercel, spawns a /fix-deploy session on new production errors.
• AI-assisted titles — regenerate a card's title via claude -p (Haiku by default).
• Orchestration skill + 12-skill pack — one Claude session can spawn, inject into, and synchronously ask sibling sessions over plain HTTP.
• Usage tracking — your pace against plan limits, per engine, with cache-adjusted token rankings, before you hit the wall.

All captures use seeded demo data.

CCC latches onto every Claude Code, Codex, Cursor, Antigravity, Kilo Code, Kimi Code, OpenCode, and Devin 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 eight; follow-up (steering a dormant session) works on seven (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 retu