cccc vs codeg
AI coding-agent coordination projects compared
cccc and codeg both help developers coordinate multiple AI coding agents. cccc centers on persistent groups, durable message tracking, and a daemon-owned control plane, while codeg centers on a shared workspace for agent sessions, code changes, and tasks through ACP.

cccc: Coordinate Coding Agents as a Persistent Group Chat
CCCC is a local-first, Rust-based coordinator for running coding agents as a persistent team across runtimes, machines, and trusted groups. It provides durable message history, delivery tracking, and Web and IM access, with installers for Linux, Apple Silicon macOS, and Windows.

codeg: Coordinate AI Coding Agents with Agent Client Protocol
Codeg is a collaborative workspace for running and coordinating AI coding agents through the Agent Client Protocol. It brings agent conversations, sessions, code changes, and tasks into one experience across desktop, self-hosted server, Docker, and mobile.
| cccc | codeg | |
|---|---|---|
| Language | Rust | Rust |
| License | Apache-2.0 | Apache-2.0 |
| Stars | 1.3k | 4k |
| Forks | 111 | 518 |
| Last analyzed | Oct 21, 2026 | Oct 19, 2026 |
Key differences
- cccc coordinates agents in persistent groups with an append-only collaboration ledger; codeg organizes agent conversations, sessions, code changes, and tasks in a shared workspace.
- cccc emphasizes delivery, read, reply, and task-completion status; codeg emphasizes session history, live diffs, delegation, and parallel work in isolated Git worktrees.
- cccc provides Web, CLI, MCP, and chat-platform controls; codeg provides desktop, server, Docker, mobile, and CLI access, plus chat integrations.
- cccc connects groups across instances with explicit access boundaries; codeg supports repository workflows across GitHub, GitLab, Gitea, and Forgejo.
- Both are written in Rust and use Apache-2.0. The supplied project facts list 1.3k stars and 113 forks for cccc, and 4k stars and 518 forks for codeg.
- cccc is aimed at persistent, mixed-runtime agent coordination; codeg targets developers and teams managing agent sessions and code work across multiple environments.
Choose cccc if you…
- need durable group messages with explicit delivery, read, and reply tracking.
- want a daemon-based control plane with Web, CLI, MCP, and chat-platform controls.
- coordinate persistent agent groups across instances or machines.
Choose codeg if you…
- want a shared workspace for agent conversations, sessions, code changes, and tasks.
- need to delegate parallel agent work in isolated Git worktrees.
- want desktop, self-hosted, Docker, or mobile access, or a CLI for scripts and CI.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.