Pin strategy sessions on top. Fan out sub-sessions for execution. Stay above the noise across 30+ agent sessions. Local, open source, MIT.
curl -fsSL https://raw.githubusercontent.com/amirfish1/claude-command-center/main/install.sh | bash
The biggest is Antigravity. Google's new coding agent is now a first-class engine alongside Claude Code and Codex, including the app-only sessions other tools cannot drive.
Both AGY CLI and app-only sessions are drivable. CCC reads the Antigravity app's local HTTPS language server and posts follow-up messages through the cascade RPC.
WIP indication, TTY display, and token usage tracking for Antigravity rows. Same telemetry surface as the Claude rows.
Pin any session to the top of the list. Strategy stays visible while execution scrolls below. The foundation for the pin-and-fan workflow.
Most tools want to own execution. You launch agents through them, and the moment you open a terminal and resume something by hand, the dashboard goes blind. CCC works the other way.
CCC reads each engine's on-disk state as the source of truth. Open a terminal, run claude --resume or agy --conversation, and the row appears. Close the dashboard, sessions keep running.
~/.claude/projects/*.jsonl ~/.claude/sessions/<pid>.json ~/.claude/command-center/live-state/
Pin five strategy sessions at the top. Each one spawns sub-sessions for execution. Strategy stays visible. Execution fans out under it. The workflow most people invent the hard way after their tenth session.
📌 launch coordination [CLAUDE] 📌 product roadmap [CLAUDE] └─ draft post [CLAUDE] └─ render video [AGY] └─ QC draft [CODEX]
One click turns a GitHub issue into a session. Verify closes the issue with a commit-SHA comment. Spawn headless claude -p or agy --conversation sessions from the dashboard and keep typing at them from the browser.
gh issue → session → PR → verify claude -p --input-format stream-json agy --conversation <sid>
The audience is anyone who tried to run more than 10 agent sessions and felt the bottleneck stop being the model and start being them.
Two repos in flight. Claude builds feature A while Codex refactors feature B while Antigravity drafts the migration. You pin the two strategy sessions and the sub-sessions are visible across both.
Each client gets a pinned strategy session. Spawn sub-sessions per ticket from their GitHub issues. The "All repos" view shows everything in flight across every client, with PR badges and time-gap markers.
Spawn a research swarm: 10 parallel Claude sessions each evaluating a different hypothesis. Per-turn auto-summaries let you scan 10 transcripts in two minutes instead of reading each one. Group-chat sessions coordinate.
Triage issues into the kanban. One click spawns a headless session against the issue. Rows move Working → Review → In Testing automatically as the agent ships. Then you review, not write.
Tools in this category make different bets. Here is where each one wins and where each one loses. We listed where CCC loses too.
| CCC v4 | claude-squad | Conductor | Chorus | Sculptor | |
|---|---|---|---|---|---|
| Sees terminal sessions you didn't spawn | ✓ | no | no | no | no |
| Multi-engine (Claude + Codex + Antigravity) | ✓ all 3 | Claude only | Claude only | Claude only | Claude only |
| Antigravity app-session support | ✓ | no | no | no | no |
| Row pinning + sub-session hierarchy | ✓ | no | no | no | no |
| GitHub issue → session in one click | ✓ | no | partial | no | no |
| Local. Survives dashboard close. | ✓ | ✓ | ✓ | cloud | ✓ |
| Source you can read in an afternoon | ✓ stdlib | Go | closed | closed | closed UI |
| Polished native app (DMG) | v4.1 | CLI | ✓ | ✓ | ✓ |
| Windows / Linux | best-effort | ✓ | macOS | ✓ | ✓ |
macOS, Python 3, Claude Code (and optionally Codex CLI, Antigravity CLI for those engines).
# downloads, installs, opens the dashboard curl -fsSL https://raw.githubusercontent.com/amirfish1/claude-command-center/main/install.sh | bash # launch later ccc start open http://localhost:8090
Installs two hooks into ~/.claude/settings.json so every Claude Code session writes the sidecar state CCC reads. Idempotent.
# DMG installer coming with v4.1 open https://ccc.amirfish.ai/download/CCC.dmg # or, today, brew tap brew tap amirfish1/ccc brew install ccc
A signed DMG with the dashboard, launchd agent, and engine adapters bundled. Shipping in the v4.1 follow-up. Star the repo to be notified.
Other tools want to own execution. You launch agents through their dashboard, and in return you get a card on a kanban. That's fine until you open a terminal.
The moment you claude --resume or agy --conversation something by hand, you're outside the tool's universe. The dashboard can't see it. The work you just did doesn't show up against the issue, in the review queue, or anywhere.
CCC goes the other way. Each engine's on-disk state is the source of truth. If Claude Code, Codex, or Antigravity is running anywhere on your machine, it shows up here. Close the dashboard. Sessions keep running. Reopen tomorrow. Everything still there.
~/.claude/command-center/. Rewriteable by hand.