Guide
CCCC coordinates coding agents as a durable group chat: messages are routed, read state is visible, operations are controlled through one daemon, and the same group can be reached from Web UI, CLI, MCP, and IM bridges.
Use this section based on what you are trying to do next.
If You Are New to CCCC
- Getting Started for a 10-minute first setup
- Web UI Quick Start if you prefer visual control
- CLI Quick Start if you prefer terminal-first workflow
If You Need Practical, High-ROI Patterns
- Use Cases for production-like collaboration scenarios
- Workflows for common execution patterns
- Best Practices for stable collaboration behavior
If You Operate CCCC in Daily Work
- Operations Runbook for triage, recovery, and upgrade flow
- Web UI Guide for control-plane behavior
- Supported Runtimes for Claude Code, Codex, ChatGPT Web, Grok, Kimi, and other actor runtimes
- CCCC Connect for same-account instance aggregation and collaboration
- Capability Allowlist Baseline for MCP/skill curation levels
- Contributor Quality Gates for local checks, CI boundaries, and native release verification
- Grok Bot Web Model for Grok Bot setup
- ChatGPT Web Model Runtime for MCP-capable ChatGPT GPT-5.x setup
- IM Bridge for mobile/remote operations
If You Need Troubleshooting
Core Concepts (Short Version)
- Working Group: the collaboration unit with durable history
- Actor: an agent runtime session (foreman/peer)
- Scope: a directory context attached to a group
- Ledger: append-only collaboration event stream
- Daemon: single writer and source of operational truth
- CCCC Connect: same-account collaboration with independent instance state