CCCC
中 EN 日
Docs Get started
CCCC VoiceExperimental

CCCC / A SHARED WORKSPACE FOR CODING AGENTS

Different minds.Common ground.

Bring your coding agents into a shared workspace. Keep their strengths, share context, and hand work between them. Talk through an idea. Give it somewhere to go.

Get startedExplore Voice

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

Enter the shared workspace
Works with the agents you choose
Claude CodeCodexChatGPT WebExplore runtimes ↗

02 / A CONVERSATION BECOMES COLLABORATION

A word becomes work.

Ask about progress, investigate the details, and hand a clear next step to a named team. One voice entry connects the conversation to the work.

YOU SAYCCCC Voice
“Check the homepage team’s progress.”
CCCC Voice ExperimentalReleased interface · example data
Example view of the CCCC v0.4.37 voice console, rendered from released UI components with sample data, not a live call.
v0.4.37 interface preview · illustrative conversation and terminal content, not an execution recordOpen the full voice console preview
CCCC / WORKSPACEThe actual product
CCCC Web control plane showing groups, agents, messages, and runtime state
CCCC Web · English interface example · Open the full screenshot Open the full CCCC mobile interface screenshot

Ask a follow-up. Interrupt naturally.

Investigate with working context.

Hand off to a named team. Follow the reply.

One shared voice entry across CCCC working groups. Actions target an explicitly identified group.

How a conversation reaches the work

Interactive illustration · no audio or live execution

Start with what you want to know.

“Check the homepage team’s progress. What needs my attention?” Name the working group so the investigation has a clear target.

YOUR QUESTION → homepage group

A conversation backed by investigation.

The Voice Analyst inspects the named group’s messages and tasks, and project files when needed. Findings return to the conversation, where you can ask follow-ups or clarify the goal.

NAMED TARGET → working context → explanation

Make the next step explicit.

“Ask the homepage foreman to prepare the next-step plan. Don’t change the code yet.” The explicit request reaches the named team through CCCC’s existing task and message records.

EXPLICIT REQUEST → named foreman → linked handoff

Bring the reply back into the conversation.

The assigned agent’s linked reply returns to the Analyst and can rejoin the active voice conversation. Delivery, a reply, and completed work remain different facts.

LINKED REPLY → conversation → your next decision

03 / WORK LEAVES A TRACE

Every step stays with you.

01

One shared working context

Goals, tasks, messages, and runtime status belong to a persistent local group. Return to its history and current progress.

CONTEXTTASKSHISTORY
02

Know what happened to a handoff

Send delivers actively, Send + Reply requests a response, and Mail waits in the Inbox. Delivery, reading, and replies are recorded separately.

SendSend + ReplyMail
03

Keep the work in your hands

Manage the same daemon state through Web, CLI, or MCP. Choose runtimes, set permissions, review results, and decide what comes next.

WebCLIMCP

04 / DISTINCT STRENGTHS, SHARED POSSIBILITIES

Your tools. Common ground.

Connect the tools you already use. Explore the runtime guide for supported surfaces and setup.

Claude CodeCodexChatGPT WebDeepSeekGrokCursorCopilotClineDevinKiroKimiOpenCodeHermesAmpDroidAuggieKiloAntigravity
Runtime & setup guide ↗

Local work. More ways in.

Follow progress and send tasks through Web, the terminal, or configured IM bridges. Remote access requires separate setup.

Local groupTrusted remote groupExplicit trust

Connect trusted teams

Group Bridge connects working groups across machines. Each keeps its own state, with explicit trust and permissions for cross-group access.

Explore Group Bridge ↗

Reach preview · Linux · macOS

Open your own CCCC from the public internet

Remote access

Your computer keeps working while you step away. Link a CCCC account and enable Reach to return from your phone or another network. Local use needs no account.

CCCC working-group state lives on your machine. Remote access, model calls, and integrations retain their own data and permission boundaries.

  1. Link this installation in local Settings → Account, or start from Web Access.
  2. Sign in to your CCCC account and approve the device code shown for this installation.
  3. Return to Web Access, set an Admin Access Token, then explicitly turn Reach on and copy the tokenless public address.

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

Installation link status and Web Access entry point in the global CCCC Account page
Account manages installation linking; Reach setup and controls remain in Web Access
Security, Cut, and availability limits

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.

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

Managed accounts and remote access are available from CCCC 0.4.35. View release notes ↗

Install and set up CCCC Open account

05 / MAKE IT YOURS

The next idea starts with you.

Install and sign in to your chosen agent CLI first. CCCC coordinates the work; model services use your own accounts.

Official installer · recommended

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

macOS / Linux · native CCCC · shell installer

Windows · native CCCC · 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"
pip install · compatibility channel

For environments that already use Python package management. It installs the same native CCCC product, with no Python backend or fallback.

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

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

View project Read the docs

Make one small thing happen.

  1. Open your workspace

    After installation, run cccc in a terminal and leave it running. Open the address below in a browser on that computer.

    cccc
    http://127.0.0.1:8848/

  2. Bring in a project and an agent

    Use + in the sidebar to choose a project folder and create a group. Use Add Actor to add an installed runtime, complete MCP setup, then start the agent.

    Follow the setup walkthrough ↗

  3. Give it a task you can check

    In Chat, select that agent as the recipient and send the task below. When it replies, check the files it references.

    Map this repository’s entry points, main modules and verification commands. Include the relevant file paths. Do not change any files yet.

A reply you can verify is your first successful use. Add a second agent to review the findings, then build from there.

CORE / GITHUB github.com/ChesterRa/cccc

Browse the source, releases, and issues.
OFFICIAL CLIENT SDK github.com/ChesterRa/cccc-sdk ↗
Connect external apps to the same coordination record

Built for backend services, bots, IDEs, and automation. The SDK connects to a running CCCC daemon instead of creating another state store.

pip install -U cccc-sdk npm install cccc-sdk cargo add cccc-sdk