cccc vs comet
Group-chat orchestration for coding agents: Claude Code, Codex, ChatGPT Web and others in one durable group with an append-only ledger, read receipts, and Web/IM/mobile ops. — versus — Zeron: control Claude Code, Codex, Cursor, Grok, Hermes and Pi from a local Rust daemon — sessions live on the device, with optional sign-in to drive them from another machine.
Both control Claude Code, Codex, Hermes, Pi etc. from a local Rust daemon with remote access; comet is per-session control, CCCC is inter-agent messaging with read receipts.
| cccc | comet | |
|---|---|---|
| Stars | 1.2k | 1.6k |
| Forks | 110 | 168 |
| Language | Rust | Rust |
| License | Apache-2.0 | MIT |
| Last activity | yesterday | 2 days ago |
| Topics | orchestration, coding | coding |
| Curated connections | 6 | 6 |
cccc — the curator's take
Reach for CCCC when the problem is *coordination* between several long-running agents - who owns a task, whether a message was actually delivered/read, what survives a daemon restart - and you want to supervise from a phone via Telegram/Mattermost. The ledger + delivery/read/reply facts are the real differentiator; most multiplexers just tile terminals. Not for a single agent in one repo (herdr or plain tmux is lighter), and not a workflow engine: it doesn't compile plans or DAGs, it routes messages between a foreman and peers. Rust binary, pip-installable, no broker/DB/Docker - but it is a daemon that owns state, so expect one more always-on process.
comet — the curator's take
The pick when you want agent sessions that outlive the laptop lid: a per-device engine owns the data directory, a fresh install is local-only with no account and no network, and signing in adds a synced workspace you can start on one box and follow from another — a VPS keeps agents working after you close the laptop. The profile boundary is unusually honest: login and logout refuse to touch credentials while an engine holds the data dir, and signing in never uploads or imports your existing local sessions. Caveats: the repo is named comet but the product is `zeron`, Linux installs via a `curl | sh` daemon, macOS wants the desktop release or a source build, and it's young enough that the docs are the architecture file.