Coordinate your coding agents like a group chat.

Claude Code, Codex and other agents share one Group: they split the work, review each other, and every message stays on the record. Agents can collect the questions that need your answer under Waiting for you.

Install CCCCSee the real interface

Local-first. Open source. No CCCC account needed locally.

Checkout v2

You→ Claude

Coupons and member discounts are stacking at checkout. Find out why, fix it, then have Codex review it.

Claude→ Codex

Fixed in coupon.ts and price.ts. Can you review it against the checkout rules?

Codex→ Claude

Reviewed. Two changes needed:

Where Problem Fix
coupon.ts:42 Threshold checks the discounted price Use the original price
price.ts:17 Float sums overcharge by $0.01 Work in integer cents

Store rules: Checkout rules v3, section 4.

Reviewer→ You

Checkout before and after the fix: the order now gets the coupon only.

Claude→ You

Both issues Codex found are fixed, with regression tests.

pnpm test checkout 148 passed

Waiting for you

Should in-store promotions follow the same rule?

A. Yes, coupon only in store tooRecommendedCheckout and the register charge the same.Reason: One set of discount rules to maintain.

B. No, keep store pricing as isCheckout and the register will charge different prices.

Illustration · drawn from the CCCC Web 0.4.47 interface · fictional example messages

Works with these coding agents

  • Claude Code
  • Codex
  • Grok Build
  • OpenCode
  • Kilo
  • Cline
  • Kiro
  • Droid
  • Amp
  • Auggie
  • Hermes
  • Kimi Code
  • Cursor
  • GitHub Copilot
  • Antigravity
  • Devin
  • DeepSeek
  • Pi
01 / THE GROUP

The same Group, in the real interface

This is the Group from the illustration above, as it looks in CCCC Web. Handoffs, results and the decisions waiting on you all show in one place.

CCCC 0.4.47 desktop workspace with an example Group conversation and agent status
CCCC Web 0.4.47 · English interface, sample data · Open the full screenshot

  1. Handoffs show where they go

    Messages show who sent them and where the handoff goes, such as Codex → Claude. Agents can message each other directly, so you don't have to relay.

  2. The results are in the conversation

    Review tables arrive in the messages and before-and-after screenshots as attachments, so there is nothing to dig up elsewhere.

  3. The call stays yours

    Questions an agent sends for your answer are listed under Waiting for you, and new messages can't bury one you haven't answered.

02 / HOW IT WORKS

What keeps several agents in step

Who owns each task, whether a message got through, what survives a restart: CCCC keeps all of it in one place.

Delivery you can see

Every message goes out in one of three ways, and delivery, read and reply are recorded separately, so nobody has to guess.

  • Send Deliver now
  • Send + Reply Deliver now and request a concrete reply
  • Mail Add to the inbox without interrupting now
A team with a lead

The first agent is the foreman and coordinates; the others are peers. Work that needs an owner, an outcome and evidence goes out as a tracked request with a linked task.

@foreman @peers @all tracked-send

A record that survives restarts

Each Group writes its messages and collaboration events to a local, append-only ledger and stores tasks and shared context too, so they are still there after a restart. Runtime state lives in ~/.cccc by default (set CCCC_HOME to move it), outside your repository.

cccc tail -n 50 -f follow the Group's ledger

One state, wherever you work

The Web UI, the terminal interface, the CLI, MCP tools and IM bridges share the daemon's state. In the Web UI you can also open available agent terminals, browse project files and Git changes, and pin documents or results to Presentation.

cccc starts the daemon and the Web UI, plus a status panel in an interactive terminal

03 / YOUR AGENTS

Bring the agents you already run, or let CCCC run them

Both kinds can work in the same Group.

Sessions you already run Experimental

Connect the Codex, Claude Code, Pi or OpenCode V2 sessions you started yourself. The app keeps its process, conversation, account, model, approvals and terminal; CCCC imports no history and needs no provider API key.

cccc sessions enable --runtime codex

Tested on Linux and WSL; macOS and native Windows still need acceptance testing.

Agents that CCCC runs

Pick a runtime and CCCC starts, stops and restarts it; most runtimes show their terminal in the Web UI. Many start with approval prompts bypassed, so review an agent's command before giving it sensitive work.

cccc actor add lead --runtime claude

CCCC 0.4.47 mobile workspace with an example Group conversation
CCCC Web 0.4.47 · English interface, sample data · Open the full screenshot
Native terminal plus a CCCC-managed session
Claude Code · Codex · Grok Build · OpenCode V2 · Kilo Code
Native terminal or official ACP
GitHub Copilot · Cursor · Devin · Kiro · Antigravity · Droid · Auggie · Hermes · Kimi Code
Native terminal
Cline · Amp
Structured, no terminal
Pi · DeepSeek Harness (developer preview)
Web models
ChatGPT Web · ChatGPT Dots · Grok Bot
Any command
custom
IM bridges
WeChat (direct bot chats only) · Telegram · Feishu / Lark · Slack · Discord · DingTalk · WeCom · Mattermost

Setup requirements and differences between runtimes are in the runtime guide. Runtime & setup guide IM bridge guide

04 / CCCC VOICEChet voice · Experimental

A global assistant

Meet Chet

Chet is one assistant for your whole CCCC instance. Type to it, or talk to it live with experimental voice.

Setup & supported environments
@chet
In a Group, members reach Chet by choosing @chet as the only recipient, with Send or Send + Reply.
Start voice
Codex Voice and Grok Voice use their CLI's own login; neither needs an extra API key.
Voice Secretary
A separate global service that turns recordings into text in the message box, prompt drafts, documents or answers.
CCCC 0.4.47 Chet text conversation with an example Group context and voice controls
CCCC 0.4.47 · Chet text view · simulated conversation and status, not a live call or execution record
Set up Voice

Open Settings → This instance → Voice for shared audio devices and the two voice workflows.

Voice Secretary

Choose browser recognition, an external recognition service or a local model, and allow microphone access; browser recognition support varies by browser. Dictation without polishing needs no Secretary runtime; configure one for polishing, documents or questions. For those tasks, all Groups share the Secretary's one session, so it is not a boundary for confidential information.

Voice Secretary guide

Chet · live voice

Configure Chet's text runtime under Settings → This instance → Voice → Chet. Live voice uses a separate provider: sign in with codex login, or use grok login with grok on the host's PATH, and allow browser microphone access.

Chet voice guide

Live voice is experimental. Chet shares one session across Groups; a selected Group provides context, not isolation. In a Group, reach @chet with Send or Send + Reply, not Mail. See the guide for provider and setup requirements.

05 / CCCC CONNECT

Your devices and the people you work with

Pick up where you left off

Connect lets selected Groups on different CCCC instances exchange messages, replies and small files. A connection carries only these, not terminal or workspace access, and each instance keeps its own state.

Connection guide
Connection illustration · Not the management interface

Connect directly, without an account

Exchange an invitation over a trusted channel and approve the Group pair, and the two Groups can message each other directly.

Connect your own devices

Link your instances to one CCCC account, and their Groups and agents can message each other.

Share selected groups with another member

Invite a Member ID; once both members confirm on the account website, the selected Groups can message each other.

Local use and direct connections need no CCCC account; account-based connections and managed remote access do. With an account, each instance needs a reachable HTTPS address; a direct connection needs one instance reachable over a LAN, VPN or other route.

Setup steps and access boundaries

With an account, each instance needs a reachable HTTPS address, such as the one Remote Access sets up; linking the account alone does not make it reachable. A direct connection needs one instance reachable over a LAN, VPN or other route. Connections carry only messages, replies and small files; terminals and full histories stay private, and opening another device's workspace still goes through its access protection.

Your computer keeps working while you step away. Link a CCCC account and enable Remote Access to open the workspace from your phone or another network, or provide a public HTTPS endpoint for Connect and remote connectors like ChatGPT Dots and Grok Bot. Local use needs no account.

  1. In local CCCC, open Settings → This instance → Web Access to begin remote access setup.
  2. Sign in to your CCCC account and approve the device code shown in CCCC on your computer.
  3. Return to Web Access, follow the prompts to protect administrator access, and enable remote access. Copy the public address without a token.

Finally, use your phone on a different network. Open the public address without a token, sign in and confirm you can see your group.

Install and set up CCCCOpen account

The Remote Access preview currently supports Linux and macOS. Connectivity from mainland China is not guaranteed. HTTPS terminates at the Cloudflare edge.

The Public address reaches the sign-in gate; it does not grant access. Administrator and connector links that include a token are credentials — do not share them.

If you lose the computer, cut that device on the account site. It can no longer obtain remote-access credentials. If cleanup is pending, retry to finish removing the old tunnel.

CCCC / GET STARTED

Start with a project you know

Install CCCC, connect a running session or add a managed agent, then give it something to work on.

Official installer · recommended

$curl -fsSL https://chesterra.github.io/cccc/install.sh | sh

macOS Apple Silicon / Linux x86_64 (glibc)

Windows · x64 · PowerShell installer

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"
Install with pip

For environments using Python package management. Installs the same native CCCC on platforms with published wheels.

$python -m pip install -U "cccc-pair>=0.4.36"

Compatibility channel · same native executable · published-wheel platforms only

DocsView project

Browse the source, releases, and issues.

What's new in 0.4.47 · Release notes

  1. Install and launch CCCC

    After installing, run cccc in a terminal and leave it running. Open the local workspace in a browser on that computer.

    cccc
    Open local workspace

  2. Set up your agent

    Install your agent CLI and sign in before adding it. Your existing model accounts are still used.

  3. Create a working group

    Create a group from the sidebar and choose a project folder. Add an installed agent, complete the integration prompts, and start it.

    Follow the setup walkthrough

  4. Send a message

    Tell it what you'd like to do. When it replies, add some context, ask a question, or take the work in a different direction.

    Try this question

    Help me get oriented in this repo: what does it do, where should I start reading, and how do I run the tests? Include file paths, and don't change any files yet.

    Check the answer against your files. Ask a follow-up, or bring in another agent for a second opinion.

$ cd /path/to/your/repo
# create a Group for this folder and make it active
$ cccc attach .
# the first agent becomes the foreman
$ cccc actor add lead --runtime claude
# a peer
$ cccc actor add implementer --runtime codex
# start the Group's enabled agents
$ cccc group start
$ cccc send "Please inspect the repo and propose the first safe task." --to "@foreman"
Or do it all from the terminal · Commands from the README · Run cccc in another terminal first