Go CLI · Single Binary · Open Source

Orchestrate Claude Code across every repo.

One terminal. Multiple agents. All your repos. CCCC runs Claude Code instances as subprocesses and coordinates them through a TUI dashboard.

Single Go binary No daemon required Works with your Claude subscription
~/projects — cccc
# Initialize CCCC in your workspace
$ cccc init --repos ./api ./web ./shared-lib ./mobile
✓ Discovered 4 repositories
✓ Mapped cross-repo dependencies
✓ Config written to .cccc.yaml
# Run a task across all repos
$ cccc run "Add rate limiting to all API endpoints"
Spawning 4 Claude Code agents...
api Adding express-rate-limit middleware
web Adding retry logic to API client
shared-lib Adding RateLimitError to error types
mobile Adding exponential backoff to HTTP layer
✓ 4 agents completed. 12 files changed across 4 repos.

Watch your agents work.

The TUI dashboard gives you full visibility into every agent's progress. Think lazygit, but for orchestrating AI.

CCCC v0.1.0 — Claude Code Control Center 4 agents · 2 running · 1 done · 1 queued
Agents
agent-01
~/projects/api
agent-02
~/projects/web
agent-03
~/projects/shared-lib
agent-04
~/projects/mobile
Agent-01 Output — ~/projects/api
13:04:12 Reading existing rate limit configuration...
13:04:15 Found 12 unprotected endpoints
13:04:18 Installing express-rate-limit@7.1.0
13:04:22 Creating middleware in src/middleware/rateLimit.ts
13:04:28 Applying to routes: /api/auth/*, /api/users/*
13:04:33 ✓ Tests passing (24/24)
13:04:35 Applying to routes: /api/billing/*, /api/export/*
13:04:40 Writing rate limit headers to shared-lib types...
13:04:44 ▶ Streaming...

Three commands. That's it.

01
cccc init

Point at your repos

Tell CCCC which repositories belong to your project. It maps dependencies and figures out how they connect.

02
cccc run "task"

Describe the change

One task, plain English. CCCC spawns a Claude Code agent per repo and coordinates the work across boundaries.

03
cccc dashboard

Watch it happen

The TUI shows real-time progress for every agent. See logs, diffs, and status. Intervene if needed. Review when done.

Structure beats chaos.

You can run four Claude Code sessions in tmux panes. But they don't know about each other. CCCC does.

Raw tmux / Terminal Panes

Manual orchestration

  • Each pane is isolated — no shared context
  • You manually copy types between repos
  • No visibility into what each agent is doing
  • Race conditions when repos depend on each other
  • You're the orchestrator — that's expensive
  • Can't coordinate task ordering or dependencies
CCCC

Structured orchestration

  • Agents share context about the full workspace
  • Cross-repo types and contracts stay in sync
  • TUI dashboard with real-time agent progress
  • Dependency-aware execution ordering
  • You review results — the CLI orchestrates
  • Opinionated workflows for common patterns

Built for real workflows.

>_

Single binary distribution

Written in Go. Download one binary. No runtime, no containers, no dependencies. Works on macOS, Linux, Windows.

▦▦

Subprocess management

Each Claude Code instance runs as a managed subprocess. CCCC handles lifecycle, output capture, and graceful shutdown.

Cross-repo awareness

Agents know about the full workspace. Changes in shared-lib automatically propagate context to dependent repos.

[=]

TUI dashboard

Real-time view of all agents. Navigate between them, read output streams, review diffs. Keyboard-driven, zero mouse required.

Opinionated workflows

Not just "run Claude in parallel." CCCC defines task patterns: cross-repo refactors, API migrations, type propagation.

.yaml

Declarative config

Define your workspace in .cccc.yaml. Repos, dependency order, agent limits, task templates. Version it with your code.

🔄

Built entirely with the thing it orchestrates.

CCCC is being built solo, using Claude Code as the primary development tool. Every line of Go, every TUI widget, every test — written in collaboration with Claude Code. If that's not dogfooding, nothing is.

Get early access.

CCCC is in active development. Join the waitlist to get notified when the first binary drops.

No spam. Just a ping when it's ready.

✓ You're on the list. We'll ping you when CCCC is ready.