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.
$ 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.
Three commands. That's it.
Point at your repos
Tell CCCC which repositories belong to your project. It maps dependencies and figures out how they connect.
Describe the change
One task, plain English. CCCC spawns a Claude Code agent per repo and coordinates the work across boundaries.
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.
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
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.
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.
✓ You're on the list. We'll ping you when CCCC is ready.