CCCC
Coordinate your coding agents like a group chat
Local-first coordination for coding agents: durable Group history, explicit message status,
cross-instance collaboration, and access from the Web, the terminal and IM.
Connect the Claude Code, Codex, Pi and OpenCode sessions you already run, or let CCCC run agents for you, as one persistent team.
One install command. No Rust toolchain, database server, message broker or Docker required.
English | 中文 | 日本語
Quick start · Documentation · Community
What CCCC does
When several coding agents share work, you need to know who owns a task, whether a message reached its recipient, and what survives a restart. CCCC keeps that in one place:
- A durable Group chat. Each Group records messages and events in an append-only ledger; tasks and shared context are stored as well.
- Explicit delivery. Messages go out as Send, Send + Reply or Mail, and delivery, read and reply are recorded as separate facts.
- Your sessions or CCCC's. Connect sessions you already run, or let CCCC manage agents on many CLI and Web runtimes, in the same Group.
- One control plane. The Web UI, the terminal interface, the CLI, MCP tools and IM bridges share the daemon's state.
- Chet, a global assistant you can write or talk to.
- CCCC Connect links Groups across machines and teams; each instance keeps its own state.
- Local-first. Runtime state stays in
CCCC_HOME (default ~/.cccc/), outside your repository.
What's new in 0.4.55
- A backlog next to your tasks. A Markdown file in your project, such as
BACKLOG.md, holds long-lived topics and ideas. Tasks shows its entries under a Tasks | Backlog switch, edits them in place and links each entry to the tasks made from it; agents use the new cccc_backlog tool. The file stays the only copy.
- Fewer new conversations after a
PATH change. When only the launch PATH changed, eligible managed agents can resume their saved conversation; the release notes give the conditions.
- Group rules only when due. When a native session reads one message by its ID, the full Group rules come with it only when they are due, not every time.
- Coordination notes removed. The Coordination log tab, the note actions of
cccc_coordination and the note lists of the recovery pack are gone. Notes saved earlier stay in the Group's stored context.
- Fixes. A task no longer stays blocked after the tasks it waited for are done (#201). Interrupting a managed Claude Code agent sends the request fields that Claude Code 2.1.317 requires; that version refused the previous request. A delivery that used up its retries no longer runs them again after every restart. Configuring a Web model connector no longer replaces its credential unless you ask to rotate it (#216).
- Two contributed commands.
cccc ledger search (#217) and cccc actor new-session (#207).
Upgrade notes. Before upgrading, let sends and recordings finish, restore or discard waiting sends, then send or copy every unsent draft and save unsaved edits in Files: all of these live only in the open page. Check whether a message already arrived before sending it again. Then restart the daemon and Web and reload open pages: a page opened before the upgrade sends a removed field with some replies across Groups, and those replies are refused until it is reloaded. A native session keeps the MCP server it started with, and that server's previous tools, until the server is started again, for example by restarting the session. Coordination notes are no longer shown: to keep a copy that is easy to read, copy their text from the Coordination log tab before upgrading.
Details: 0.4.55 release notes.
Quick start
Install
# macOS / Linux
curl -fsSL https://chesterra.github.io/cccc/install.sh | sh
# Windows CMD or PowerShell
powershell.exe -NoProfile -ExecutionPolicy Bypass -Command "[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12; Invoke-RestMethod 'https://chesterra.github.io/cccc/install.ps1' | Invoke-Expression"
# Or through pip: the same native executable in a platform wheel
python -m pip install -U "cccc-pair>=0.4.36"
CCCC runs on Linux x86-64 (glibc 2.28+), Apple Silicon macOS 11+ and Windows x86-64. See Installation and upgrades for more.
Launch
cccc
cccc starts the daemon and the Web UI. In an interactive terminal it also opens a status panel; type / for its commands, and /quit or Ctrl+C stops what this launch started. Open http://127.0.0.1:8848 for the full Web UI; local use needs no password.
On servers, in containers and in scripts, use cccc --headless (the same as cccc web). If port 8848 is in use, choose another with cccc --port 9000. cccc doctor checks the installation and the agent CLIs it detects.
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗
