Most questions are answered by these resources:
| Resource | What it covers |
|---|---|
cccc doctor |
Environment check — verifies Python, runtimes, daemon status |
cccc --help |
Complete CLI command reference |
| Online docs | Getting started, use cases, operations runbook, architecture |
| FAQ | Common questions and troubleshooting |
Open a GitHub Issue and include:
- Version: output of
cccc version - OS and Python version: e.g., macOS 14.2, Python 3.11.7
- Runtime: which agent runtime(s) you're using (claude, codex, etc.)
- Exact command: the full command you ran
- Actual output: copy-paste the error or unexpected behavior
- Expected behavior: what you expected to happen
- Reproduction steps: minimal steps to trigger the issue
If the issue involves the daemon, include relevant lines from ~/.cccc/daemon/ccccd.log.
Open a GitHub Issue with:
- Problem statement: what workflow is difficult or impossible today
- Proposed behavior: how you'd like it to work
- Operational impact: how this affects your multi-agent setup
Please report security vulnerabilities privately. See SECURITY.md for instructions.
- CCCC is local-first. All runtime state lives under
CCCC_HOME(default~/.cccc/), not in your repository. - The daemon is the single source of truth. If something looks wrong, check
cccc daemon statusfirst. - For recovery procedures, see the Operations Runbook.