podium

CCCC

49 of 51 criteria have a sourced finding; 49 were also cross-checked by a second agent. Every comparison that includes CCCC links here for scope, limitations, atomic answers and sources.

Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.

Rubric
0.3 · 51 criteria
Source checks
2026-11-13
Agent cross-checked
49 criteria
Comparisons
1

Access and agent choice

ACC-01

Client access

Agent cross-checked partial

Daemon + CLI run on Linux x86-64 (glibc 2.28+), Apple Silicon macOS 11+ and Windows x86-64; the React Web UI works in desktop and mobile browsers and as an installed standalone-display web app (PWA manifest, iOS Home Screen from 16.4 for push). No native desktop or mobile app and no editor extension ship. Start/steer/approve/review/resume run in Web, terminal panel, CLI and IM; Web Push plus IM/automation notices cover notifications; the same Group continues across devices via remote access or Connect.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • No native desktop/mobile apps or editor extension; phone Files read-only; drafts and reading places are per-browser, not synced.
9 atomic answers
  • Desktop os [supported] Desktop OS coverage is the daemon/CLI plus browser: Linux x86-64 glibc 2.28+, Apple Silicon macOS 11+, Windows x86-64. Intel Macs stop at 0.4.37; Linux ARM64/Alpine/musl and native Windows ARM64 Python envs do not match current wheels. Sources: cccc:readme, cccc:faq.
  • Mobile apps [partial] No native iOS/Android app ships. The Web UI is responsive with phone layouts and a PWA manifest (standalone display); iPhone/iPad use is via browser or Home Screen web app. Phone Files view is read-only. Sources: cccc:manifestweb, cccc:webui.
  • Browser [supported] The Web UI is the primary client at 127.0.0.1:8848/ui, usable over LAN/tunnel/Tailscale/Reach with an Admin token; read-only exhibit mode exists for sharing. Sources: cccc:webui, cccc:cliref.
  • Mobile browser [supported] Mobile browsers work including swipe/pull-to-refresh/touch menus; Cloudflare Tunnel + Access recommended for phone access; iOS/iPadOS 16.4+ Home Screen apps get Web Push with 18.4+ link-opening. Sources: cccc:faq, cccc:webui, cccc:features.
  • Cli [supported] Product-owned cccc CLI covers daemon lifecycle, groups, actors, messaging, inbox, ledger search, IM, space, setup, update, web and mcp, plus an interactive terminal interface with status panel and Waiting-for-you rows. Sources: cccc:cliref, cccc:readme.
  • Editor extensions [unsupported] Client access, editor extensions: bounded search of the site, docs, CLI reference and pinned repo found no editor/IDE extension; editing happens in the Web file browser or the agent runtime terminals. Sources: cccc:negsearch, cccc:readme, cccc:faq, cccc:webui.
  • Task actions [supported] Start, steer, approve, review and resume run from Web (run controls, in-place answers, diffs), the terminal panel (group/actor pages), the CLI (group/actor/send/reply/deliver) and IM (/send /status /pause /resume). Sources: cccc:webui, cccc:cliref, cccc:imbridge.
  • Notifications [supported] Web Push per browser (message addressed to user + open requests, bounded retries), IM bridge updates, automation notify rules with Mail/reply notices, terminal panel Waiting-for-you counts. Sources: cccc:features, cccc:webui, cccc:imbridge.
  • Cross device continuity [supported] The same Group is reachable from another device via LAN/tunnel/Tailscale/Reach remote access, IM bridges and Connect; drafts and reading places stay per browser (unsent drafts live only in the open page). Sources: cccc:webui, cccc:connect, cccc:releasenotes.

Sources: cccc:cliref, cccc:connect, cccc:faq, cccc:features, cccc:imbridge, cccc:manifestweb, cccc:negsearch, cccc:readme, cccc:releasenotes, cccc:webui

Agent cross-checked partial

Each agent picks one of 21 named runtimes (Claude Code, Codex, Grok Build, OpenCode, Kilo, Copilot, Cursor, Devin, Kiro, Antigravity, Droid, Auggie, Hermes, Kimi, Cline, Amp, Pi, DeepSeek, ChatGPT Web, ChatGPT Dots, Grok Bot) or any command via custom, and mixed runtimes share one Group. Model choice stays runtime-side (model-label is declarative only). CCCC injects its MCP into managed sessions and hooks native ones; provider logins stay with the runtimes and CCCC needs no provider API key.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Model choice and provider login stay with each runtime; actor model-label is declarative and unchecked.
5 atomic answers
  • Harnesses [supported] 21 named runtimes plus custom any-command fallback; native terminal, official ACP, structured RPC/headless and browser-delivered surfaces per runtime; runtime list and availability via cccc runtime list and cccc doctor. Sources: cccc:runtimes, cccc:faq.
  • Model providers [partial] Model selection is inherited from each runtime (explicit model choices applied at start/resume; no CCCC model catalog or guessing). actor --model-label is a human-declared label CCCC does not check or use to launch. ChatGPT Web uses GPT-5.x chats via the bound conversation. Sources: cccc:cliref, cccc:runtimes, cccc:webmodel.
  • Custom adapters [supported] custom runtime runs any command; capabilities install from explicit local path, URL or GitHub target with recorded provenance; slash skills dispatch skill: packs. Sources: cccc:runtimes, cccc:capsimportcode, cccc:skillcode.
  • Session integration [supported] Managed sessions get an agent-scoped MCP server (preflight verified before launch); native user-run Codex/Claude/Pi/OpenCode sessions integrate via MCP plus hooks/plugin/extension; Web models use a remote MCP connector. Sources: cccc:runtimes, cccc:localsessions, cccc:webmodel.
  • Mixed harness operation [supported] Each agent chooses its own runtime and both managed and connected sessions work in the same Group; workflows document Claude + Codex + Kimi style mixes with a reviewer runtime for diversity. Sources: cccc:runtimes, cccc:readme, cccc:workflows.

Sources: cccc:capsimportcode, cccc:cliref, cccc:faq, cccc:localsessions, cccc:readme, cccc:runtimes, cccc:skillcode, cccc:webmodel, cccc:workflows

Agent cross-checked partial

Agents run on the user own existing subscriptions and logins: connected sessions keep their app process, account, model, approvals and terminal, and CCCC needs no provider API key. Managed agents are launched from the user-installed CLIs. No vendor credits, paid CCCC plans or card exist; per-actor private environment supports different model/API stacks per agent. The only account is the optional free CCCC account for Connect/Reach; local use needs none.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • No CCCC-side billing or credits; all inference spend stays on the user runtime accounts.
7 atomic answers
  • Agent subscriptions [supported] Bring your own agent subscription: managed agents launch from installed, signed-in CLIs; connected sessions keep their own conversation, account, model and approvals; ChatGPT/Grok voice reuse their CLI logins with no extra API key. Sources: cccc:readme, cccc:localsessions, cccc:voicesec.
  • Api accounts [partial] Runtime accounts stay runtime-side (CLI logins, ChatGPT sign-in + remote MCP connector, Google credential for NotebookLM, IM bot tokens). CCCC keeps IM credentials and actor secrets but owns no provider billing account. Sources: cccc:webmodel, cccc:groupspace, cccc:features, cccc:imbridge.
  • Vendor credits [unsupported] Subscriptions, vendor credits: bounded search of the site, docs, account pages and CLI reference found no vendor credits; automation notices may use model credits via the user own runtime logins. Sources: cccc:negsearch, cccc:readme, cccc:localsessions.
  • Local models [unknown] Subscriptions, local_models: no local-model runtime or guide was located; whether an arbitrary local-model CLI works through custom is unproven in the checked sources.
  • Account switching [supported] Runtime-only actor secrets give each agent different model/API stacks; ChatGPT connector credentials are agent-specific; multiple runtime logins coexist across agents in one Group. Sources: cccc:features, cccc:cliref, cccc:webmodel.
  • Vendor account requirement [supported] Local CCCC works with no account and no sign-in; the free CCCC account is only needed for Connect and managed Remote Access, and direct Connect pairs need no account at all. Sources: cccc:connect, cccc:account, cccc:cliref.
  • Provider restrictions [partial] Documented runtime restrictions: Antigravity cannot join as a connected session, Web models need public HTTPS + pairing, DeepSeek is developer preview, managed agents may bypass approvals (review commands first), test boundaries Linux/WSL only. Sources: cccc:localsessions, cccc:runtimes, cccc:readme.

Sources: cccc:account, cccc:cliref, cccc:connect, cccc:features, cccc:groupspace, cccc:imbridge, cccc:localsessions, cccc:negsearch, cccc:readme, cccc:runtimes, cccc:voicesec, cccc:webmodel

Agent cross-checked partial

Install (shell/PowerShell/pip/Docker/source), run cccc, create a Group, add an installed signed-in agent and send the first message. Any local directory attaches as a scope with no Git requirement; Git clones get read-only diffs (CCCC never stages/commits). Prerequisites are an agent CLI install + sign-in (plus Node 24 for JS code mode, Xvfb for projected browsers). Managed cloud does not exist; a BYO VPS path runs headless under a supervisor with LAN/tunnel/Tailscale/Reach access (Reach helper Linux/macOS only).

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • No managed-cloud option; Reach remote publishing is a Linux/macOS preview.
7 atomic answers
  • First task setup [supported] Install, cccc launch, create Group, add agent from detected runtimes, start Group, send message; CLI (attach/actor add/group start/send) and Web (sidebar create, + add agent) flows both documented with troubleshooting. Sources: cccc:readme, cccc:gettingstarted, cccc:webquick, cccc:cliref.
  • No git [supported] Onboarding, no_git: cccc attach works on any local directory and a Group without a project folder simply has no backlog; no Git requirement is stated in the install/launch flows. Sources: cccc:cliref, cccc:webquick.
  • Local git without remote [supported] Local Git repos work: Files shows untracked/ignored files, Changes lists working-tree/staged/conflicts/untracked items with diffs; a created BACKLOG.md is excluded via the clone-local exclude, not .gitignore. Sources: cccc:webui, cccc:arch.
  • Hosted git [partial] Works inside a hosted-git clone like any checkout (agents use git/runtime tools there); no hosted-git-specific onboarding or integration is documented. Sources: cccc:webui, cccc:runtimes.
  • Prerequisite guidance [supported] At least one supported agent runtime CLI installed and signed in; source builds need Rust 1.88+/Node 24/npm/Python 3.11+; MCP JavaScript code mode needs Node on the host; projected browsers need Xvfb/x11vnc on Linux. Sources: cccc:faq, cccc:readme, cccc:cliref.
  • Managed cloud setup [unsupported] Onboarding, managed_cloud_setup: bounded search found no managed-cloud compute offering; Remote Access publishes the user own machine and explicitly uploads neither repository nor ledger. Sources: cccc:negsearch, cccc:readme, cccc:gettingstarted.
  • Byo vps onboarding [partial] Headless/server/container operation under a service manager with LAN binding, tunnels, Tailscale or Reach; Reach install/publish is a Linux/macOS preview needing an Admin token, and its Windows helper is not in this release. Sources: cccc:operations, cccc:webui, cccc:cliref.

Sources: cccc:arch, cccc:cliref, cccc:docker, cccc:faq, cccc:gettingstarted, cccc:negsearch, cccc:operations, cccc:readme, cccc:runtimes, cccc:webquick, cccc:webui

Agent cross-checked partial

A complete product-owned CLI plus MCP surfaces (daemon tools over stdio for agents; Python/TypeScript/Rust SDK clients for integrators; documented Web API endpoints), but no generic public REST API with stability promises and no generic outgoing webhooks. Create/inspect/steer/stop/review run through CLI, MCP, Web and IM; auth is loopback-local principal plus Admin Access Tokens for non-local use.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • No versioned public REST API or generic webhooks; automation-capable surface is CLI/MCP/Web/IM.
8 atomic answers
  • Cli [supported] Full cccc CLI: daemon/groups/actors/messaging/inbox/ledger/IM/space/setup/update/web/mcp with JSON doctor output and documented env vars; the terminal panel adds an interactive command menu. Sources: cccc:cliref, cccc:faq.
  • Api [partial] Documented Web API endpoints exist (push config/subscription, capabilities allowlist, files/AGENTS.md, backlog, group operations) but no versioned public REST API with stability guarantees is stated. Sources: cccc:features, cccc:allowlist, cccc:arch.
  • Sdk [supported] Separate cccc-sdk with Python, TypeScript and Rust clients connecting to a running cccc; daemon owns lifecycle/delivery, SDK carries no daemon. Sources: cccc:readme.
  • Mcp server [supported] cccc mcp serves collaboration tools over stdio; agents see a compact core (bootstrap/help/inbox/messaging/files/context/coordination/task/connect) with capability-managed expansion packs. Sources: cccc:cliref, cccc:arch, cccc:features.
  • Webhooks [unsupported] Programmable access, webhooks: bounded search found no generic outgoing webhooks; provider-side Webhook Routines (Grok Bot) and ChatGPT event tasks are runtime-specific inbound mechanisms. Sources: cccc:negsearch, cccc:cliref, cccc:arch.
  • Operations [supported] Create/inspect/steer/stop/review via CLI (groups/actor/send/reply/deliver/inbox/tail/ledger search), MCP (group/actor/messaging/automation/terminal/debug), Web run controls and IM commands. Sources: cccc:cliref, cccc:arch, cccc:imbridge.
  • Authentication [supported] Local loopback gets a passwordless in-memory administrator principal; non-local clients need an Admin Access Token (account linking initializes one); IM credentials via env-var references preferred. Sources: cccc:webui, cccc:readme, cccc:features.
  • Stability [partial] Daemon IPC is a versioned contract (CCCS/daemon-IPC standards docs); Web API/MCP evolution follows release notes with upgrade caveats, but no API stability/SLA statement exists. Sources: cccc:arch, cccc:releasenotes.

Sources: cccc:allowlist, cccc:arch, cccc:cliref, cccc:faq, cccc:features, cccc:imbridge, cccc:negsearch, cccc:readme, cccc:releasenotes, cccc:webui

Agent cross-checked partial

Capabilities install as mounted skill packs from explicit local paths, URLs or GitHub targets with provenance; slash skills dispatch them. CCCC sets up its own MCP into most runtimes itself (prompt-assisted where the runtime requires it) and governs tool visibility with a foreman/user allowlist. No external-MCP consumption by CCCC itself and no plugin framework beyond capability packs were established; repo instructions import through the AGENTS.md editor, watched instruction files and cccc_file.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Capability governance is tool visibility, not process sandboxing; no third-party MCP consumption.
7 atomic answers
  • Mcp client [unsupported] External tools, mcp_client: bounded inspection of the docs and daemon/MCP sources found CCCC exposing MCP to agents (server side) but no consumption of third-party MCP servers by CCCC itself. Sources: cccc:negsearch, cccc:arch, cccc:runtimes.
  • Plugins [partial] Capability packs mount/enable/pin/block per group or globally; third-party sources are discoverable by default with a conservative safety mode. No general plugin framework beyond capability packs is documented. Sources: cccc:allowlist, cccc:arch.
  • Custom tools [supported] Custom runtime runs any command; finite MCP shell/Git tools, local code execution (web_model), repo inspection tools and snippets/automation actions extend behavior; cccc_code_exec/cccc_shell exist behind capability use. Sources: cccc:runtimes, cccc:webmodel, cccc:features.
  • Instructions import [supported] AGENTS.md editor in Project Context, watched instruction files (AGENTS/CLAUDE variants) with change nudges, protocol reference customization, skill/capability import with provenance. Sources: cccc:bestpractices, cccc:webui, cccc:capsimportcode.
  • Authentication [partial] IM tokens as env-var references or literals (env preferred); actor/runtime secrets stored daemon-side with key-metadata-only reads; ChatGPT/Google credentials via their own sign-in flows. Sources: cccc:features, cccc:imbridge, cccc:webmodel, cccc:groupspace.
  • Permission scope [supported] Foreman/peer/user permission matrix kernel-enforced by the daemon; capability allowlist overlays group vs global scope; workspace+Group permission checks on file/media reads; exhibit read-only mode. Sources: cccc:arch, cccc:allowlist, cccc:webui.
  • Integration owner [partial] CCCC-owned per-session MCP setup for most runtimes with preflight repair; Cursor/Kilo/Antigravity use prompt-assisted contracts and session-owned MCP, inheriting runtime-side setup. Sources: cccc:runtimes, cccc:cliref.

Sources: cccc:allowlist, cccc:arch, cccc:bestpractices, cccc:capsimportcode, cccc:cliref, cccc:features, cccc:groupspace, cccc:imbridge, cccc:negsearch, cccc:runtimes, cccc:skillcode, cccc:webmodel, cccc:webui

Agent cross-checked partial

No installable desktop or native mobile client ships: access is the React+TypeScript+Vite+Tailwind+xterm Web UI in desktop/mobile browsers (installable as a standalone-display PWA) plus the Rust CLI/daemon and terminal panel. Implementation evidence is pinned source: web/package.json dependency set, PWA manifest, Rust workspace members. No hybrid wrappers were found.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Browser+PWA+CLI only; no native or hybrid clients.
4 atomic answers
  • Desktop implementation [unsupported] Client implementation, desktop_implementation: bounded search found no desktop client implementation; desktop access is the browser Web UI plus the native CLI executable. Sources: cccc:negsearch, cccc:readme, cccc:manifestweb.
  • Mobile implementation [partial] No native iOS/Android implementation; the mobile surface is the responsive Web UI with phone layouts plus the standalone-display PWA manifest (Home Screen use). Sources: cccc:webui, cccc:manifestweb.
  • Hybrids [unsupported] Client implementation, hybrids: bounded source inspection found no Electron/Tauri/React-Native/wrapper shells; installers ship the native Rust executable plus the web bundle. Sources: cccc:negsearch, cccc:readme, cccc:manifestweb.
  • Implementation evidence [supported] Pinned source evidence: web/package.json (react, xterm, tailwind, vite, typescript), web/public/manifest.webmanifest, Rust workspace crates (daemon/web/runtime/cli/mcp), install.ps1/install.sh shipping native executables. Sources: cccc:manifestweb, cccc:pyproject, cccc:readme.

Sources: cccc:manifestweb, cccc:negsearch, cccc:pyproject, cccc:readme, cccc:webui

Planning and context

Agent cross-checked partial

Groups, tasks and backlog entries are created natively by humans (composer, CLI, Web) with durable task/event IDs, and the Group ledger is the authoritative record for product-owned work. There is no import from Linear/GitHub/Jira or other external trackers and no chat/Git triggers; CCCC-to-CCCC Connect relays messages between instances rather than syncing trackers, so no external round-trip exists.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Self-contained issue tracking; no external tracker integration of any kind.
9 atomic answers
  • Local creation [supported] Groups created in Web sidebar or via cccc attach/group create; tasks created in the board editor, from backlog topics, or linked via tracked-send with owner/outcome. Sources: cccc:webquick, cccc:webui, cccc:cliref.
  • Prompt intake [supported] Composer messages with @mentions, CLI send/tracked-send, and IM /send take work in as chat addressed to foreman/peers/agents. Sources: cccc:webui, cccc:cliref, cccc:imbridge.
  • External import [unsupported] Intake, external_import: bounded inspection of guides, CLI reference and daemon ops found no import from external trackers; the only file-based intake is the project BACKLOG.md. Sources: cccc:negsearch, cccc:arch, cccc:cliref.
  • Chat git triggers [unsupported] Intake, chat_git_triggers: no chat triggers or git-event triggers start work; automation triggers are interval/cron/one-time rules only. Sources: cccc:negsearch, cccc:arch, cccc:cliref.
  • Authoritative tracker [supported] The Group ledger plus context/tasks store is the authoritative record (append-only events, ctxv revisions); no external tracker is required or designated. Sources: cccc:arch, cccc:tasklistcode.
  • Stable ids [supported] Durable task IDs, ledger event IDs, backlog hidden entry IDs and CLI idempotency keys keep identity across restarts, copies and renames. Sources: cccc:arch, cccc:webui, cccc:cliref.
  • Sync [unsupported] Intake, sync: no two-way sync with external trackers exists; Connect relays messages/replies/files between CCCC instances with each keeping its own state. Sources: cccc:negsearch, cccc:arch, cccc:cliref.
  • Supported edits [partial] Tasks edit in Web/CLI/agent tools with conflict guards; external-tracker edits do not apply since no external tracker is integrated. Sources: cccc:webui, cccc:contextcode.
  • External roundtrips [unsupported] Intake, external_roundtrips: no operations require a trip back to an external tracker; repository work happens through the workspace and runtimes. Sources: cccc:negsearch, cccc:arch, cccc:cliref.

Sources: cccc:arch, cccc:cliref, cccc:contextcode, cccc:imbridge, cccc:negsearch, cccc:tasklistcode, cccc:webquick, cccc:webui

Agent cross-checked supported

Tasks carry title, status, assignee, priority, outcome, checklist, notes, subtasks and handoff/blocking links, editable in the Web board, CLI-tracked sends and agent tools with optimistic-concurrency revisions. Plans amend freely mid-run, link to backlog topics and handoffs, and persist across restarts in the daemon-owned context store.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
7 atomic answers
  • Plans [supported] Tasks with goal/focus/coordination brief, outcome, checklist and notes; tracked-send creates task + linked delegation message with owner and outcome. Sources: cccc:webui, cccc:cliref, cccc:features.
  • Acceptance criteria [supported] Outcome field plus task-type requirements and per-item checklist states record what done means; a done task without an outcome gets a suggestion to add one. Sources: cccc:webui.
  • Editors [supported] Web task editor, CLI tracked-send fields (--checklist/--notes/--task-priority), backlog entry editing, and agent task tools all mutate the same store. Sources: cccc:webui, cccc:cliref, cccc:contextcode.
  • Revisions [supported] ctxv optimistic revisions with expected-version saves; conflicting saves are refused with the edits kept for copying; import preserves event IDs. Sources: cccc:webui, cccc:contextcode, cccc:features.
  • Amendment [supported] Tasks move across Planned/Active/Done, subtasks/checklists/outcomes edit in place, backlog topics move/close/reopen; type requirements describe completeness but never block a change. Sources: cccc:webui.
  • Restart persistence [supported] Tasks/context persist in CCCC_HOME context store across daemon restarts; imported groups start idle with actors stopped and history intact. Sources: cccc:arch, cccc:operations, cccc:features.

Sources: cccc:arch, cccc:cliref, cccc:contextcode, cccc:features, cccc:operations, cccc:webui

Agent cross-checked partial

Tasks form a parent/subtask tree with assignees and blocked_by/waiting-on attention states derived into blocked badges (recomputed, cf. fix #201), linked to backlog topics that outlive them. No epic entity, readiness gate or dependency enforcement exists: type requirements never block a change and Mail never starts an agent. No rigid workflow is required by design.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Derived (not enforced) blockers; no epics, gates or mandatory workflows.
9 atomic answers
  • Epics [unsupported] Hierarchy, epics: bounded inspection found no epic entity with rollup state; backlog topics group ideas but carry no status rollup or dispatch semantics. Sources: cccc:negsearch, cccc:webui, cccc:faq.
  • Hierarchy [partial] Parent tasks with subtasks (progress counts of direct non-archived subtasks), backlog sections/topics nesting ideas; arbitrary-depth nesting beyond one subtask level is unproven. Sources: cccc:webui.
  • Blockers [supported] blocked_by/waiting-on fields with blocked/waiting attention filters and badges; a task whose waited-on tasks complete stops counting as blocked (#201). Sources: cccc:webui, cccc:tasklistcode, cccc:releasenotes.
  • Readiness [partial] Waiting/on-hold states surface via attention filters and Waiting for you; no dispatch readiness gate was located (Mail does not start an agent). Sources: cccc:tasklistcode, cccc:operations.
  • Enforcement [unsupported] Hierarchy, enforcement: task-type requirements describe completeness but never block a change; blockers are displayed/derived, not dispatch-enforced. Sources: cccc:negsearch, cccc:webui, cccc:faq.
  • State propagation [partial] Status columns, attention badges and Waiting-for-you counts propagate state across the board; cross-task propagation is limited to derived blocked states. Sources: cccc:webui.
  • Task to epic [partial] Backlog topics persist while tasks complete (finishing never closes the topic) with task links and outcome write-back, but no epic promotion primitive exists. Sources: cccc:webui, cccc:releasenotes.
  • Identity retention [supported] Task IDs, backlog hidden entry IDs and event IDs survive edits, moves, renames, restarts and group copies; concurrent saves conflict instead of forking identity. Sources: cccc:webui, cccc:contextcode, cccc:features.
  • Workflow constraints [supported] No rigid preselected workflow is required: a quick send needs no preset, and CCCC is explicitly not a DAG workflow orchestrator. Sources: cccc:faq, cccc:positioning, cccc:workflows.

Sources: cccc:contextcode, cccc:faq, cccc:features, cccc:negsearch, cccc:operations, cccc:positioning, cccc:releasenotes, cccc:tasklistcode, cccc:webui, cccc:workflows

Agent cross-checked partial

Repository instructions live in the workspace AGENTS.md editor plus watched AGENTS/CLAUDE variants with change nudges; project docs in Files; working memory in Tasks/context/Agent State and the NotebookLM work/memory notebooks; skills as installable capability packs with self-evolving candidates surfaced per Group. Provenance is ledger attribution with staleness marks; correction/deletion run through editors, archive/delete and version conflicts; no spec-drift detection exists.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Chet cross-group context is instruction-level, not isolated; memory search/update tooling retired.
10 atomic answers
  • Instructions [supported] AGENTS.md editor at the workspace root, watched AGENTS.override/AGENTS/CLAUDE variants with one-line change nudges on next delivery, optional team re-read notification; each runtime keeps its own discovery/precedence. Sources: cccc:bestpractices, cccc:webui.
  • Skills [partial] Skills panel shows self-evolving candidates from the Group; capabilities install from explicit sources and dispatch via skill: packs; full candidate lifecycle (promote/retire) is unstated. Sources: cccc:webui, cccc:capsimportcode, cccc:skillcode.
  • Project docs [supported] Workspace Files browser with Markdown/Mermaid/CSV/PDF viewers, Presentation slots, pinned documents and message attachments all read the same workspace. Sources: cccc:webui.
  • Memory [partial] Agent State latest reports with timestamps/staleness, context brief/decisions/handoffs, NotebookLM memory notebook via explicit ingest; legacy memory files are retained in copies but no dedicated search/update tool remains. Sources: cccc:webui, cccc:groupspace, cccc:features.
  • Scope [partial] Group vs instance settings, per-group protocol reference, per-workspace AGENTS.md, per-actor secrets; Chet reads every Group as context but forwarding/isolation between Groups is instruction-only, not enforced. Sources: cccc:webui, cccc:readme, cccc:features.
  • Provenance [partial] Ledger records sender (by) per event; Agent State shows timestamps and staleness; task saves are versioned. Citation-grade provenance of external knowledge is unstated. Sources: cccc:arch, cccc:webui.
  • Correction [supported] Tasks, backlog topics, AGENTS.md and files edit in place with conflict guards; automation/snippet and guidance documents are user-editable. Sources: cccc:webui.
  • Deletion [supported] Delete for never-started planned tasks, archive otherwise, pin/message removal, backlog close/reopen, capability uninstall, account/device deletion flows. Sources: cccc:webui, cccc:account, cccc:features.
  • Freshness [partial] Staleness shown on Agent State and instruction nudges on file change; no systematic freshness/retention policy for memory beyond compaction/retention windows. Sources: cccc:webui, cccc:bestpractices, cccc:account.
  • Takeover continuity [supported] Same Group continues from another device via remote access or Connect; managed agents resume saved conversations (PATH-change improvements in 0.4.55); native sessions rejoin with recovery guidance. Sources: cccc:webui, cccc:connect, cccc:localsessions, cccc:releasenotes.

Sources: cccc:account, cccc:arch, cccc:bestpractices, cccc:capsimportcode, cccc:connect, cccc:features, cccc:groupspace, cccc:localsessions, cccc:readme, cccc:releasenotes, cccc:skillcode, cccc:webui

Agent cross-checked partial

Agents read the workspace through Files, message attachments (images/video/PDF/audio), Mermaid/PDF viewers, repo inspection tools and explicit NotebookLM ingestion (files, pasted text, URLs, YouTube, Drive). Bounded repo inspection and scoped editing exist for web runtimes. No product-wide code indexing, citation model, conflict detection or review-time enforcement was established.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Retrieval is tool- and file-scoped; no index, citations model or enforcement.
10 atomic answers
  • Indexing [unsupported] Architecture, indexing: bounded inspection of the pinned tree (crates/*/src, web/src, docs/**) finds no repository-indexing service; retrieval is tool- and attachment-scoped, NotebookLM ingestion is explicit per item. Sources: cccc:negindex.
  • External knowledge [supported] NotebookLM work/memory notebook binding with explicit file/URL/YouTube/Drive ingestion, query and jobs via agent/CLI tools; web URL content reachable the same way. Sources: cccc:groupspace, cccc:cliref.
  • Multimodal inputs [supported] Image/video/PDF/audio attachments with viewers, Mermaid diagrams, before/after screenshots in reviews, live voice transcripts and documents via Chet/Secretary. Sources: cccc:webui, cccc:features, cccc:voicesec.
  • Freshness [partial] Reload paths (Reload file, refresh, re-ingest) and staleness marks exist; source freshness tracking and enforcement are unstated. Sources: cccc:webui, cccc:groupspace.
  • Access scope [supported] Reads stay in the active workspace with Group permission checks; symlinks/outside-workspace targets disabled with reasons; exhibit mode hides Files. Sources: cccc:webui.
  • Api retrieval [supported] cccc_file/cccc_file_send/cccc_repo/message-history/space-query tooling plus ledger search give agents and users programmatic retrieval. Sources: cccc:arch, cccc:cliref, cccc:groupspace.
  • Citations [partial] Quotes, references, message links and file-path mentions carry provenance; no formal citation/conflict model exists. Sources: cccc:webui, cccc:features.
  • Conflict detection [unsupported] Architecture awareness, conflict_detection: bounded inspection found no architectural conflict detection; concurrent task saves conflict, which is edit concurrency, not knowledge conflicts. Sources: cccc:negsearch, cccc:arch, cccc:runtimes.
  • Review enforcement [unsupported] Architecture awareness, review_enforcement: no review-time conformance enforcement exists; review outcomes are recorded as messages, not gates. Sources: cccc:negsearch, cccc:arch, cccc:runtimes.

Sources: cccc:arch, cccc:cliref, cccc:features, cccc:groupspace, cccc:negsearch, cccc:runtimes, cccc:voicesec, cccc:webmodel, cccc:webui

Agent cross-checked partial

A complete native task system: create/edit/discuss/prioritize/assign/search/filter/archive/reopen in the board, idea parking in the project BACKLOG.md, explicit dispatch via tracked-send, durable Planned/Active/Done states and task/session separation with per-task metadata. No labels/tags, no epic views, no external tracker: nothing external is needed or integrated.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • No labels/tags, estimates or epic views; single-product tracking only.
17 atomic answers
  • Create [supported] Tasks created in the board editor, from backlog topics (Create task), or linked via tracked-send; backlog topics and ideas created in the file view. Sources: cccc:webui, cccc:cliref.
  • Edit [supported] Title/status/assignee/priority/outcome/checklist/notes/subtasks edit with version-conflict guards; backlog entries edit in place with file-hash fencing. Sources: cccc:webui.
  • Discuss [supported] Messages with @mentions, reply/quote/forward, review tables and outcome discussion carry task discussion; Waiting for you collects open questions. Sources: cccc:webui, cccc:features.
  • Prioritize [supported] Per-task priority field plus attention filters (blocked/waiting/handoff/unassigned) and Waiting-for-you ordering surface what matters. Sources: cccc:webui, cccc:tasklistcode.
  • Label [unsupported] Native issues, label: bounded inspection of the board editor, task ops and CLI found priority/assignee/attention but no label/tag field. Sources: cccc:negsearch, cccc:webui.
  • Assign [supported] Assignee per task, @foreman/@peers addressing, tracked-send --assignee/--waiting-on/--handoff-to delegation fields. Sources: cccc:webui, cccc:cliref.
  • Filter [supported] Status columns, attention filters, sender filters, assignee filters and message tabs (Waiting/All/Pinned/User-related). Sources: cccc:webui, cccc:tasklistcode.
  • Archive [supported] Archive for finished tasks (Restore returns prior status); backlog Closed section for finished topics with Reopen. Sources: cccc:webui.
  • Reopen [supported] Restore archived tasks, Reopen closed backlog topics, resume stopped groups and restart agents on new or resumed sessions. Sources: cccc:webui, cccc:cliref.
  • Project epic views [partial] Board columns plus per-group sidebar status cover projects; no epic rollup or cross-group portfolio view exists. Sources: cccc:webui.
  • Idea parking [supported] BACKLOG.md holds long-lived topics/ideas beside Tasks with entry-to-task links and outcome write-back; tasks work without one. Sources: cccc:webui, cccc:releasenotes.
  • Explicit dispatch [supported] tracked-send creates a task and sends one linked delegation with owner and outcome; automation one-time rules dispatch operations. Sources: cccc:cliref, cccc:features.
  • Task session separation [supported] Tasks (durable records) are distinct from agents/sessions (runtimes); several agents can attach to work on tasks and sessions restart independently. Sources: cccc:webui, cccc:arch.
  • Metadata [partial] Status/assignee/priority/outcome/checklist/notes/subtasks/handoff/blocking/type; no labels, estimates or custom fields. Sources: cccc:webui, cccc:cliref.
  • Durable states [supported] Planned/Active/Done/Archived with transitions, restore semantics and daemon-persisted context across restarts. Sources: cccc:webui, cccc:tasklistcode, cccc:arch.
  • External tracker requirement [supported] No external tracker is required or used: tasks, ledger, context and files all live under CCCC_HOME; IDE/GitHub/Linear round-trips do not exist. Sources: cccc:arch, cccc:operations.

Sources: cccc:arch, cccc:cliref, cccc:features, cccc:negsearch, cccc:operations, cccc:releasenotes, cccc:tasklistcode, cccc:webui

Agent cross-checked partial

Agents share the same durable task IDs humans use: list/get via cccc_task-class tools, create via tracked delegation, update with optimistic-concurrency batches under foreman/peer role gates, assign/state/subtask/result through context ops, all visible in the Web board with ledger attribution. Self-claim and agent-set dependencies are only partly established; conflicts surface as explicit task_conflict errors.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Agent self-claim and agent-set dependencies only partly established.
14 atomic answers
  • Shared ids [supported] Task/event/backlog IDs are identical across Web, CLI, MCP and IM; agents quote them in replies and links. Sources: cccc:webui, cccc:cliref, cccc:arch.
  • Read [supported] Agents read tasks via task list/get tools, message history and context projections with attention lists and counts. Sources: cccc:arch, cccc:cliref.
  • Create [supported] tracked-send creates a task plus its linked delegation message; backlog-sourced creation and CLI task fields cover human creation; agent creation flows through the same daemon ops. Sources: cccc:cliref, cccc:features, cccc:contextcode.
  • Update [supported] Validated batch mutations with compare-and-swap revisions; conflicting saves are refused with edits preserved for copying. Sources: cccc:contextcode, cccc:webui.
  • Claim [partial] Assignees record ownership and foreman assigns work; agent self-claim of unassigned tasks is not separately established. Sources: cccc:webui, cccc:cliref.
  • Assign [supported] Foreman (and user) may add/manage actors and set assignees; tracked-send carries --assignee/--waiting-on/--handoff-to. Sources: cccc:arch, cccc:cliref.
  • State changes [supported] Status moves (Planned/Active/Done/Archived) through board, CLI and task ops with version guards. Sources: cccc:webui, cccc:tasklistcode.
  • Dependencies [partial] blocked_by/waiting-on fields derive blocked attention; whether agents may set them via tools (vs Web) is not separately established. Sources: cccc:webui, cccc:tasklistcode.
  • Children [supported] Subtasks with progress counts under Advanced details; backlog topics parent linked tasks. Sources: cccc:webui.
  • Results [supported] Outcomes, checklists, notes and reply evidence recorded per task; completion evidence stays in the ledger. Sources: cccc:webui, cccc:features.
  • Human visibility [supported] Board, messages, Waiting for you and Agent State reflect agent writes immediately with live updates. Sources: cccc:webui.
  • Attribution [supported] Every ledger event carries its sender; task/editor actions attribute to user, foreman or peer actors. Sources: cccc:arch.
  • Permissions [supported] Daemon RBAC: peers manage only self, foreman manages any actor; task ops are role-gated; capability allowlist overlays group/global scope. Sources: cccc:arch, cccc:contextcode, cccc:allowlist.
  • Conflicts [supported] Concurrent mutations fail closed with task_conflict errors naming the change; idempotency keys prevent double-apply. Sources: cccc:contextcode, cccc:cliref.

Sources: cccc:allowlist, cccc:arch, cccc:cliref, cccc:contextcode, cccc:features, cccc:tasklistcode, cccc:webui

Agent cross-checked partial

Long-lived requirements persist in the project BACKLOG.md (topics outlive tasks with outcome write-back) and in AGENTS.md guidance; both are human-editable with version/hash guards. Agents write outcomes and notes and read topics/files via tools, with later retrieval through ledger search and context. No formal requirement objects, approval records or drift detection exist.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • File-based persistence, not a requirements database; no drift detection or approval records.
9 atomic answers
  • Persistent requirements [partial] Backlog topics and AGENTS.md persist across tasks/releases as ordinary versioned files; no dedicated requirement records with status exist. Sources: cccc:webui, cccc:releasenotes, cccc:bestpractices.
  • Human edits [supported] Backlog entries, AGENTS.md, tasks and guidance documents edit in place with conflict fencing. Sources: cccc:webui.
  • Agent edits [partial] Agents record outcomes/notes and ingest sources via tools; direct agent edits to backlog/AGENTS.md files are possible through file tools but requirement-level authorship is not separately established. Sources: cccc:webui, cccc:arch.
  • Revisions [supported] Whole-file SHA fencing for backlog edits, ctxv revisions for tasks, ledger history for everything; conflicting writes are refused, not merged. Sources: cccc:webui, cccc:contextcode.
  • Approvals [partial] User answers to agent questions are recorded decisions; no formal approval records or approval rules on specs exist. Sources: cccc:features.
  • Later retrieval [supported] Ledger search, message history, context projections and file reads retrieve prior requirements during later work. Sources: cccc:cliref, cccc:arch.
  • Drift detection [unsupported] Living specs, drift_detection: bounded inspection found instruction-file change nudges only; no specification-drift detection or conformance re-checks. Sources: cccc:negsearch, cccc:webui, cccc:bestpractices.
  • Review integration [partial] Reviews happen in chat with tables/evidence and outcomes recorded; no formal review gate binds specs to delivery. Sources: cccc:workflows, cccc:features.

Sources: cccc:arch, cccc:bestpractices, cccc:cliref, cccc:contextcode, cccc:features, cccc:negsearch, cccc:releasenotes, cccc:webui, cccc:workflows

Coordination and automation

COORD-01

Parallel work

Agent cross-checked partial

Several agents run concurrently in a Group and several Groups run side by side; the sidebar, terminal panel and status counts show running, waiting, failed and finished work across them. No concurrency quotas are documented; observed-concurrency evidence is limited to status/running counts rather than measured parallelism.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • No quotas; concurrency visibility is status-level, not measured.
5 atomic answers
  • Concurrent sessions [supported] Multiple agents per Group plus multiple Groups; terminal view pages up to four agents; start/stop per agent or per Group. Sources: cccc:webui, cccc:cliref.
  • Concurrent tasks [supported] Planned/Active/Done tasks coexist with several agents working in parallel; tracked-send fans work out with owners. Sources: cccc:webui, cccc:cliref.
  • Quotas [unsupported] Parallelism, quotas: bounded search of docs, CLI reference and daemon sources found no documented concurrency quotas or limits. Sources: cccc:negsearch, cccc:webui, cccc:cliref.
  • Observed concurrency [partial] RUNNING counts, status dots, activity rings and progress bubbles show live work; no measured concurrency figures are published. Sources: cccc:webui, cccc:cliref.
  • Status visibility [supported] Sidebar Group rows with status and Waiting-for-you counts, terminal panel status dots, Group pages with task-state counts, /status and cccc groups/actor list. Sources: cccc:webui, cccc:cliref, cccc:imbridge.

Sources: cccc:cliref, cccc:imbridge, cccc:negsearch, cccc:webui

Agent cross-checked partial

Users and the foreman assign and route work (@mentions, default_send_to policy, tracked-send ownership); peers manage only themselves under daemon RBAC. Dispatch is guarded by idempotency keys and single-writer rules. No queues and no duplicate-prevention beyond idempotency were established.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • No queues; claiming semantics thin.
7 atomic answers
  • Human assignment [supported] Users add/start/stop agents, set assignees and address work via composer, CLI and IM. Sources: cccc:webui, cccc:cliref, cccc:imbridge.
  • Agent assignment [supported] Foreman coordinates peers, may add/start/stop any actor and receives default-addressed messages; tracked-send assigns owners. Sources: cccc:arch, cccc:cliref, cccc:features.
  • Claims [partial] Assignment and assignee fields are established; agent self-claim semantics for unassigned work are not separately documented. Sources: cccc:webui, cccc:cliref.
  • Queues [unsupported] Ownership, queues: bounded inspection found no work queues; Mail inboxes hold deferred messages, not queued dispatch. Sources: cccc:negsearch, cccc:arch.
  • Routing [supported] Default recipient policy (@foreman/@all), explicit @ addressing, Mail vs Send vs Send+Reply routing, cross-Group and Connect addressing. Sources: cccc:features, cccc:arch, cccc:connect.
  • Duplicate prevention [supported] Idempotency keys on sends/task ops, save-conflict guards, and no-double-apply semantics on retried creation. Sources: cccc:cliref, cccc:contextcode.
  • Ownership enforcement [supported] Daemon-enforced RBAC permission matrix (user/foreman/peer) plus capability allowlist scoping; advisory locks are not used in place of enforcement. Sources: cccc:arch, cccc:allowlist.

Sources: cccc:allowlist, cccc:arch, cccc:cliref, cccc:connect, cccc:contextcode, cccc:features, cccc:imbridge, cccc:negsearch, cccc:webui

Agent cross-checked partial

The foreman coordinates peers in a daemon-owned Group: handoffs via direct agent-to-agent messages with delivery/read/reply facts, per-agent runtime/model-label/private-env configuration, mixed-harness teams, live activity plus retained terminals, and retained results in ledger/tasks/Agent State. Follow-up runs through replies, retries, new sessions and restarts across CLI, MCP, Web and IM.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Effort/turn budgets are runtime-side; auth partly inherits runtimes.
12 atomic answers
  • Roles [supported] First enabled agent is foreman (coordinates + works, manages any actor); later agents are peers (manage only self); user sits above both. Sources: cccc:arch, cccc:faq, cccc:cliref.
  • Model harness effort [partial] Per-agent runtime, command override, private environment and declarative model-label; effort/turn-budget controls are runtime-side, not product controls. Sources: cccc:cliref, cccc:runtimes.
  • Messages [supported] Agent-to-agent sends with @ addressing, quote/reply threading, Mail inbox, cross-Group and Connect addressing with receipts. Sources: cccc:features, cccc:connect.
  • Results return [supported] Send+Reply obligations, outcomes on tracked tasks, Agent State reports and review tables return results to requesters. Sources: cccc:features, cccc:webui.
  • Cross harness [supported] One Group mixes runtimes (Claude + Codex + Kimi style); handoffs name Codex→Claude style routes across providers. Sources: cccc:runtimes, cccc:workflows, cccc:site.
  • Orchestration owner [supported] The CCCC daemon owns orchestration: single writer for ledger/tasks/lifecycle with the foreman as product-designated coordinator role. Sources: cccc:arch, cccc:readme.
  • Activation [supported] Group start/stop/resume, actor start/stop/restart/new-session, native session join/leave/recovery via CLI, Web and IM. Sources: cccc:cliref, cccc:webui, cccc:localsessions.
  • Authentication [partial] Per-runtime MCP setup (CCCC-owned or prompt-assisted/session-owned), provider logins inherited, Connect member IDs and Admin tokens for remote scope. Sources: cccc:runtimes, cccc:localsessions, cccc:connect.
  • Live progress [supported] Activity snapshots, runtime dock rings/bubbles, terminal views, status dots and Waiting-for-you counts during work. Sources: cccc:webui, cccc:arch.
  • Retained results [supported] Ledger history, task outcomes/checklists, Agent State reports, pins and Presentation slots retain results after completion. Sources: cccc:features, cccc:webui.
  • Followup [supported] Reply/forward, deliver retries, cancel-reply, actor new-session/restart, Run-now automation and re-ingest continue finished work. Sources: cccc:cliref, cccc:features.
  • Invocation [supported] Delegate from Web composer, CLI send/tracked-send, IM /send, MCP message/task tools and automation actions. Sources: cccc:cliref, cccc:imbridge, cccc:arch.

Sources: cccc:arch, cccc:cliref, cccc:connect, cccc:faq, cccc:features, cccc:imbridge, cccc:localsessions, cccc:readme, cccc:runtimes, cccc:site, cccc:webui, cccc:workflows

Agent cross-checked partial

Daemon-owned automation runs interval, cron and one-time rules with notify plus one-time group-state/actor-control actions, completion semantics and Run-now; delivery retries are bounded and uncertain handoffs need explicit retry confirmation. No external event triggers exist. Automation needs the daemon host running (service manager for unattended); paused/stopped groups run nothing and missed fires are not replayed.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • No external event triggers; unattended operation needs a supervisor.
8 atomic answers
  • Schedules [supported] Interval (every N minutes), recurring (daily/weekly/monthly cron with timezone) and one-time (countdown/exact) rule triggers with max_runs. Sources: cccc:features, cccc:automationcode.
  • Events [partial] IM messages, automation notices and Mail/reply notices move work; generic external event triggers (webhooks/repo events) do not exist. Sources: cccc:imbridge, cccc:features.
  • Recurring tasks [supported] Cron recurring reminders/operations with timezone handling and progress/completion lists. Sources: cccc:features, cccc:webui.
  • Completion conditions [supported] One-time rules complete and disable after firing; max_runs bounds repeats; past-due fires while paused/stopped do not run late. Sources: cccc:features, cccc:automationcode.
  • Scheduler location [supported] The daemon owns scheduling; rule/automation state lives in groups/<id>/state/automation.json under CCCC_HOME. Sources: cccc:arch, cccc:automationcode.
  • Overlaps [partial] Resume restarts clocks without replaying missed fires; concurrent-fire overlap semantics are unstated. Sources: cccc:features.
  • Retries [supported] Bounded delivery retries with ambiguous settlement (no auto-retry of uncertain handoffs); Run now does not retry unknown outcomes; failed deliveries offer Retry. Sources: cccc:deliverycode, cccc:features, cccc:faq.
  • Client independence [supported] Automation and deliveries proceed with no open browser or client; quitting the foreground cccc stops what that launch started, so unattended use runs headless under a supervisor. Sources: cccc:operations, cccc:webui, cccc:cliref.

Sources: cccc:arch, cccc:automationcode, cccc:cliref, cccc:deliverycode, cccc:faq, cccc:features, cccc:imbridge, cccc:operations, cccc:webui

Agent cross-checked supported

Pause/stop/resume/steer from Web run controls, CLI and IM; Web Push, IM and automation notices plus in-place pending decisions under Waiting for you; delivery failures surface with reasons and Retry; chat and terminal views share the ledger with documented native-session limits; history persists in the ledger, tasks and pins.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
10 atomic answers
  • Pause [supported] Pause message delivery per Group (Web) or per chat/thread (IM /pause); paused groups run no automation and record answers without delivering. Sources: cccc:webui, cccc:imbridge, cccc:features.
  • Stop [supported] Group stop halts managed agents and native delivery; daemon stop ends managed processes; Ctrl+C stops what the launch started. Sources: cccc:cliref, cccc:operations.
  • Resume [supported] Resume running restarts delivery (starting enabled agents if none run); daemon restart settles claims and restores from ledger authority. Sources: cccc:webui, cccc:deliverycode.
  • Steer [supported] Mid-run @ sends, tracked-send delegation, reply steering, actor restart/new-session and terminal input redirect running work. Sources: cccc:cliref, cccc:webui, cccc:features.
  • Notifications [supported] Web Push, IM updates, automation notify rules and bounded Mail/reply notices announce pending work across Web/IM/terminal. Sources: cccc:features, cccc:webui, cccc:imbridge.
  • Pending decisions [supported] Waiting for you lists open requests per Group with cross-Group counts; questions render options+recommendation with in-place answers. Sources: cccc:features, cccc:webui.
  • Escalation [partial] Bounded Mail/reply notices and stand-up reminders nudge; no escalation chain or paging beyond notifications exists. Sources: cccc:features.
  • Visible errors [supported] Delivery failure reasons with Retry, inbox/terminal diagnostics, cccc doctor checks and troubleshooting tables per symptom. Sources: cccc:faq, cccc:features, cccc:cliref.
  • Chat terminal parity [partial] Composer sends and ledger history are shared across chat/terminal/CLI/IM; native-session terminal mirroring and approval specifics stay runtime-side with documented limits. Sources: cccc:webui, cccc:localsessions.
  • Retained history [supported] Append-only ledger, task/context stores, pins, terminal retention and Copy Groups keep history across pause/stop/restart. Sources: cccc:arch, cccc:features, cccc:terminalhistory.

Sources: cccc:arch, cccc:cliref, cccc:deliverycode, cccc:faq, cccc:features, cccc:imbridge, cccc:localsessions, cccc:operations, cccc:terminalhistory, cccc:webui

Agent cross-checked partial

The sidebar lists every Group with lifecycle status and Waiting-for-you counts (including archived totals), each Group page shows run controls, task-state counts and attention filters, and terminals page per agent with waiting/stuck indicators. Subtasks and blocked_by show on cards, but there is no fleet-level dependency, workload or navigation-error view and no fixture/demo mode.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • No fleet dependency/workload views; navigation-error behavior unstated.
8 atomic answers
  • Fleet fixture [supported] Sidebar group list with status dots/counts, terminal panel with per-agent pages, Group pages with tasks/agents/actions cover the fleet without a fixture mode. Sources: cccc:webui, cccc:cliref.
  • Parent child [partial] Parent/subtask cards render inside a Group; no cross-group nesting or fleet tree exists. Sources: cccc:webui.
  • Dependencies [partial] blocked_by/waiting-on badges on cards; no fleet-level dependency graph or readiness board exists. Sources: cccc:webui, cccc:tasklistcode.
  • Attention [supported] Waiting-for-you counts per Group and cross-Group totals, attention filters, unread Mail badges and stuck-agent indicators. Sources: cccc:webui, cccc:features.
  • History [supported] Per-group ledger/tail/message history, task revisions and archived Groups with retained history. Sources: cccc:arch, cccc:cliref.
  • Workload [partial] RUNNING counts and per-agent status show load; no workload balancing or capacity view exists. Sources: cccc:webui, cccc:cliref.
  • Navigation errors [unknown] Fleet navigation, navigation_errors: missing/deleted-group navigation behavior is not established in the checked docs.
  • Fixture mode [unknown] Fleet navigation, fixture_mode: no sample/fixture mode is documented; the checked sources describe the live UI only.

Sources: cccc:arch, cccc:cliref, cccc:features, cccc:tasklistcode, cccc:webui

Agent cross-checked partial

A plain send starts work with no mandatory workflow or preset; snippets and the opt-in stand-up are optional. Agents reconfigure per runtime/command/private-env mid-run, roles show live (foreman badge, status, activity), and ledger/task/pin links retain relationships. Management is discoverable via docs, /help, doctor and IM commands; local use is passwordless while remote actions need tokens.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Optional snippets only; no workflow presets or NL workflow definitions.
10 atomic answers
  • Quick task [supported] One prompt starts work: attach a folder, add an agent, send — no preset or project scaffolding required. Sources: cccc:webquick, cccc:workflows.
  • Growing epic [partial] Topics link tasks and outcomes write back, but no epic object or promotion primitive carries growth. Sources: cccc:webui, cccc:releasenotes.
  • Presets [unsupported] Flexibility, presets: bounded inspection found optional snippets and an opt-in stand-up example only; no mandatory or selectable workflow presets exist, by design. Sources: cccc:negsearch, cccc:features, cccc:workflows.
  • Natural language [partial] Chat/IM/auto-managed MCP tooling configures and steers work in language; no natural-language workflow-definition surface exists beyond prompts and snippets. Sources: cccc:imbridge, cccc:arch, cccc:features.
  • Agent configuration [supported] Per-agent runtime, command override, private environment and model-label; switch runtime, restart with new session, edit mid-run. Sources: cccc:cliref, cccc:runtimes, cccc:features.
  • In run changes [supported] Add/stop/restart/edit agents, move tasks, edit automation and guidance while work runs; resume restarts clocks without replay. Sources: cccc:webui, cccc:cliref, cccc:features.
  • Live roles [supported] Foreman labels, member status rings, activity/progress indicators and receipt/read/reply states expose coordinator/peer roles live. Sources: cccc:webui, cccc:features.
  • Retained relationships [supported] Ledger, task/handoff/topic links, pins and Presentation slots persist relationships during and after work. Sources: cccc:arch, cccc:webui, cccc:features.
  • Discoverability [partial] Docs site, /help, cccc doctor, runtime lists and IM /help surface actions; no guided workflow discovery tour exists. Sources: cccc:cliref, cccc:faq, cccc:imbridge.
  • Auth friction [partial] Local use is passwordless; remote/Connect/Reach need Admin tokens and account linking with documented setup; no per-action auth beyond RBAC. Sources: cccc:webui, cccc:connect, cccc:arch.

Sources: cccc:arch, cccc:cliref, cccc:connect, cccc:faq, cccc:features, cccc:imbridge, cccc:negsearch, cccc:releasenotes, cccc:runtimes, cccc:webquick, cccc:webui, cccc:workflows

Execution and reliability

Agent cross-checked partial

Execution is local on the user machine (plus self-hosted headless/Docker/service-manager deployments and BYO remote access to that machine over LAN, tunnel, Tailscale or Reach). There is no vendor cloud compute: Reach publishes the user own host (uploads neither repo nor ledger) and Connect relays only messages/files. Work survives client disconnects and continues from other devices; disconnecting the launching terminal stops what it started.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • No vendor cloud; regions/resources/payer are user-side and unstated.
12 atomic answers
  • Local [supported] Daemon + agents run on the local machine with state in CCCC_HOME; localhost use needs no token. Sources: cccc:arch, cccc:webui.
  • Byo remote [supported] LAN binding, Cloudflare tunnel, Tailscale and Reach-published own host give remote/phone access to the same instance. Sources: cccc:webui, cccc:workflows, cccc:cliref.
  • Self hosted [supported] Headless/systemd/container deployments documented with backup/restore runbook; Docker image ships agent CLIs. Sources: cccc:operations, cccc:docker.
  • Managed cloud [unsupported] Execution, managed_cloud: bounded inspection found no vendor cloud compute; Remote Access serves the user own machine and Managed Access is a tunnel, not hosted execution. Sources: cccc:negsearch, cccc:webui, cccc:connect.
  • Hybrid [partial] Connect mixes instances across machines/teams with per-instance state; compute always stays on member machines, never pooled. Sources: cccc:connect.
  • Provisioning [partial] Installers and reach install provision the pinned tunnel helper; compute provisioning itself is the user own hardware/VPS. Sources: cccc:readme, cccc:cliref.
  • Payer [unknown] Execution, payer: no vendor-billed compute exists, so there is no payer schedule; who pays for BYO hardware/provider usage is outside product sources. Business fact.
  • Resources [unknown] Execution, resources: compute resources are the user own hardware; no product-stated CPU/RAM/disk schedule exists.
  • Region [unknown] Execution, region: no product regions exist; tunnel/provider routing regions are unstated in checked sources.
  • Expiry [partial] No sandbox expiry applies; quick tunnel URLs are temporary by nature and web-push payloads keep for a day; automation states persist. Sources: cccc:workflows, cccc:features.
  • Client disconnect [supported] Closing the browser/IM never stops the daemon; reconnect resumes views, cursors and retained terminals from ledger authority. Sources: cccc:webui, cccc:deliverycode.
  • Other device continuation [supported] Phone/browser/IM/Connect continue the same Groups from other devices; in-flight page drafts stay per browser. Sources: cccc:webui, cccc:connect, cccc:imbridge, cccc:releasenotes.

Sources: cccc:arch, cccc:cliref, cccc:connect, cccc:deliverycode, cccc:docker, cccc:features, cccc:imbridge, cccc:negsearch, cccc:operations, cccc:readme, cccc:releasenotes, cccc:webui, cccc:workflows

Agent cross-checked partial

Agents share the Group checkout by default with workspace-scoped file checks; Claude managed sessions additionally default to background worktrees unless configured otherwise. No product containers, VMs, OS sandboxes or process/network isolation exist — capability allowlists govern tool visibility, not agent processes — and the Web UI is explicitly high-privilege. Secrets stay in CCCC_HOME with owner-only permissions and out of copies.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Shared-checkout default; isolation is scoping, not sandboxing.
12 atomic answers
  • Checkout [supported] Groups attach project scopes as shared checkouts; Files/Changes/agents operate on the same working copy unless a runtime isolates. Sources: cccc:arch, cccc:webui, cccc:runtimes.
  • Branch [partial] Branch work happens through runtime CLIs, not product operations; worktree/branch identity guidance is documented for handoffs. Sources: cccc:runtimes, cccc:webui.
  • Worktree [partial] CCCC creates and cleans up no worktrees; managed Claude Code defaults to background worktrees (configurable off), agents may create their own with manual cleanup guidance. Sources: cccc:runtimes, cccc:faq.
  • Container [partial] Docker deployment image exists for self-hosting; per-task containers do not exist. Sources: cccc:docker.
  • Vm [unsupported] Isolation, vm: bounded inspection found no VM-based execution or isolation. Sources: cccc:negsearch, cccc:runtimes, cccc:allowlist.
  • Os sandbox [unsupported] Isolation, os_sandbox: no OS sandbox exists; the allowlist guide states it is not a sandbox for agent processes. Sources: cccc:negsearch, cccc:runtimes, cccc:allowlist.
  • Filesystem [partial] Workspace/root scoping enforced on reads, uploads and ingestion with outside-scope rejection; agents themselves run with user filesystem rights. Sources: cccc:webui, cccc:groupspace, cccc:arch.
  • Process [unsupported] Isolation, process: agent processes are user-owned with daemon lifecycle supervision only; no process boundary is documented or located in code. Sources: cccc:negsearch, cccc:runtimes, cccc:allowlist.
  • Network [partial] Loopback IPC is trusted-local and never exposed; remote access requires tokens/HTTPS; agent egress itself is unrestricted. Sources: cccc:webui, cccc:arch.
  • Secrets [supported] Per-actor secrets under CCCC_HOME/state/secrets, key-metadata-only reads, excluded from Copy Groups; IM tokens via env references preferred. Sources: cccc:features, cccc:cliref.
  • Code separation [partial] Per-scope workspaces separate Groups; a shared checkout has no per-agent separation unless the runtime isolates. Sources: cccc:arch, cccc:runtimes.
  • Security boundary [unsupported] Isolation, security_boundary: no hostile-code containment is claimed; do not expose the high-privilege Web UI or share runtime homes with untrusted users. Sources: cccc:negsearch, cccc:runtimes, cccc:allowlist.

Sources: cccc:allowlist, cccc:arch, cccc:cliref, cccc:docker, cccc:faq, cccc:features, cccc:groupspace, cccc:negsearch, cccc:runtimes, cccc:webui

Agent cross-checked partial

The append-only ledger plus context/mail cursors and delivery facts is the recovery authority: daemon restarts settle claims, resume automation clocks and restore views/terminals; actor/group/daemon restart ladders and native-session recovery are documented. Transient terminal modes are not transferred and uncertain handoffs are never auto-replayed; idempotency prevents double-apply and the operations runbook covers manual repair.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Transient UI/provider state is not reconstructed; uncertainty never auto-replays.
12 atomic answers
  • Client disconnect [supported] Browser/IM disconnects never stop the daemon; retained terminals, cursors and views reattach on return. Sources: cccc:webui, cccc:deliverycode.
  • Worker crash [partial] Actor/group/daemon restart ladder with delivery-failure surfacing and Retry; crash-detection specifics are unstated. Sources: cccc:operations, cccc:faq.
  • Service restart [supported] Daemon stop/start recovery with claim settlement to ambiguous, automation clock restart and ledger-authority restore; version-mismatch notices name the remedy. Sources: cccc:operations, cccc:deliverycode, cccc:webui.
  • Expiry [partial] No compute expiry exists; retained hidden terminals expire (32 views/5 min), quick tunnel URLs are temporary, push payloads keep a day. Sources: cccc:webui, cccc:features.
  • Transcript reload [supported] Terminals retain scrollback/selection with bounded opt-in transcript persistence; ledger reloads full message history. Sources: cccc:webui, cccc:terminalhistory, cccc:arch.
  • Process reconnect [supported] Retained views reattach to live output; native sessions rejoin with status/recovery panes and refreshable checks. Sources: cccc:webui, cccc:localsessions.
  • Task resume [supported] Resume running, group start, actor restart/new-session and saved-conversation resume continue tasks, including PATH-change improvements. Sources: cccc:cliref, cccc:runtimes, cccc:releasenotes.
  • State reconstruction [supported] Ledger + context/tasks/cursors + delivery facts reconstruct state; Copy Groups and CCCC_HOME backups restore it wholesale. Sources: cccc:arch, cccc:features, cccc:operations.
  • Context loss [partial] Restarting a provider process does not transfer transient input mode or hot terminal ring; durable ledger/cursor/reply facts remain authoritative. Sources: cccc:runtimes.
  • Duplicate actions [supported] Idempotency keys, no-double-apply creation, conflict-refused saves and non-replay of uncertain handoffs prevent duplicates. Sources: cccc:cliref, cccc:contextcode, cccc:deliverycode.
  • Manual repair [supported] Operations runbook: doctor/daemon status/tail triage, per-level restart playbooks, backup/restore, escalation checklist. Sources: cccc:operations, cccc:faq.
  • Multi day continuity [partial] 24/7 positioning with daemon-owned durable state and overnight-task patterns; unattended continuity needs a supervisor and evidence is vendor-stated, not measured. Sources: cccc:site, cccc:workflows, cccc:operations.

Sources: cccc:arch, cccc:cliref, cccc:contextcode, cccc:deliverycode, cccc:faq, cccc:features, cccc:localsessions, cccc:operations, cccc:releasenotes, cccc:runtimes, cccc:site, cccc:terminalhistory, cccc:webui, cccc:workflows

Agent cross-checked partial

Agent CLIs stay user-installed with doctor/runtime-list diagnostics and per-runtime setup repair; ports are configurable with collision guidance; actor secrets and remote-access setup are documented. No dependency provisioning, dev services, snapshots or automatic repair of environments exists, and worktree/duplicate hygiene stays manual.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • User owns dependencies and hygiene; product diagnoses more than it repairs.
10 atomic answers
  • Dependencies [partial] Targets are existing CLI installs verified by doctor/setup preflight (missing runtimes reported, stale MCP entries repaired); provisioning them is the user job. Sources: cccc:faq, cccc:runtimes, cccc:cliref.
  • Caches [unknown] Environment, caches: dependency/node_modules cache handling is unstated in the checked docs and pinned sources.
  • Snapshots [partial] Ledger snapshot/compaction exists for history size; environment snapshots for workspaces do not. Sources: cccc:faq, cccc:arch.
  • Services [unsupported] Environment, services: bounded inspection found no dev-service (DB/queue) provisioning for workspaces; agents use their own means. Sources: cccc:negsearch, cccc:faq, cccc:runtimes.
  • Ports [supported] Configurable Web port with env/saved-setting/flag precedence and documented collision handling (including Windows excluded ranges). Sources: cccc:cliref, cccc:faq, cccc:webui.
  • Secrets [supported] Actor secrets commands, env-var token references, owner-only CCCC_HOME storage and exclusion from copies. Sources: cccc:features, cccc:cliref.
  • Duplicate installs [partial] doctor reports duplicate/conflicting cccc commands and PATH ownership; deduplication itself is manual. Sources: cccc:faq, cccc:cliref.
  • Collisions [partial] Port-range and duplicate-install diagnostics with manual remedies; worktree cleanup is explicitly manual. Sources: cccc:faq, cccc:runtimes.
  • Remote setup [supported] Headless/systemd/container operation plus LAN/tunnel/Tailscale/Reach remote setup with token hardening. Sources: cccc:operations, cccc:webui, cccc:docker.
  • Automatic repair [partial] Automatic reclaim of stale locks, MCP setup preflight repair and bounded delivery retries; no general environment auto-repair. Sources: cccc:faq, cccc:runtimes, cccc:deliverycode.

Sources: cccc:arch, cccc:cliref, cccc:deliverycode, cccc:docker, cccc:faq, cccc:features, cccc:negsearch, cccc:operations, cccc:runtimes, cccc:webui

Agent cross-checked partial

No time/turn/token/spend limits or provider-failure policies gate agent work; costs stay provider-side and untracked. Bounded delivery retries, max_runs automation bounds, transport timeouts and failure surfacing with Retry exist, but nothing enforces a stop on spend or sized budgets.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Advisory and bounded-retry only; no enforced budgets of any kind.
8 atomic answers
  • Time limits [unsupported] Limits, time_limits: bounded inspection found no time limits on agent work; automation intervals/cron schedule reminders, not deadlines. Sources: cccc:negsearch, cccc:features, cccc:cliref.
  • Turn limits [unsupported] Limits, turn_limits: no turn limits were located in docs, CLI or daemon sources. Sources: cccc:negsearch, cccc:features, cccc:cliref.
  • Token limits [unsupported] Limits, token_limits: no token/context caps were located; model-label is declarative and unchecked. Sources: cccc:negsearch, cccc:features, cccc:cliref.
  • Spend limits [unsupported] Limits, spend_limits: no spend tracking or limits exist; inference spend stays on user runtime accounts. Sources: cccc:negsearch, cccc:features, cccc:cliref.
  • Timeouts [partial] Transport-level bounds exist (bounded command capture deadline, 30s Tailscale probe, push send timeouts); no user-facing task timeouts. Sources: cccc:arch, cccc:features.
  • Retries [supported] Bounded delivery retries with ambiguous settlement, Retry actions on failed deliveries, failed-job retry for space jobs. Sources: cccc:deliverycode, cccc:faq, cccc:cliref.
  • Provider failures [partial] Delivery failures surface with reasons and terminal evidence; provider-outage behavior beyond retry/Retry is unstated. Sources: cccc:faq, cccc:features.
  • Enforcement [unsupported] Limits, enforcement: nothing converts limits into enforced stops; Mail advisories warn, type requirements never block, uncertain handoffs need explicit confirmation. Sources: cccc:negsearch, cccc:features, cccc:cliref.

Sources: cccc:arch, cccc:cliref, cccc:deliverycode, cccc:faq, cccc:features, cccc:negsearch

Agent cross-checked partial

Daemon/terminal/ledger logs with tail/search/export, delivery failure reasons with diagnostics, task/attention statistics on the board and inbox summaries, lifecycle state badges and Waiting-for-you approval counts all run from ledger truth with reconnect-safe cursors. No distributed tracing, cost/time aggregates or measured performance figures exist.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Status truth is strong; analytics and measured performance are absent.
13 atomic answers
  • Logs [supported] ccccd.log, terminal scrollback with opt-in persistence, ledger tail/search, IM logs, diagnostics bundles via doctor. Sources: cccc:operations, cccc:terminalhistory, cccc:cliref, cccc:supportdoc.
  • Traces [partial] Per-recipient runtime.delivery facts and event streams trace handoffs; no distributed tracing exists. Sources: cccc:features, cccc:arch.
  • Failure reasons [supported] Delivery failure/open-reason surfacing, Retry UI, doctor/installation diagnostics and symptom-indexed troubleshooting. Sources: cccc:faq, cccc:features, cccc:cliref.
  • Usage export [partial] Ledger search and Copy Groups export history/tasks/settings; no usage-statistics report export exists. Sources: cccc:cliref, cccc:features.
  • Task stats [supported] Board status counts, attention facets, per-task change ages, inbox-summary waiting-Mail tallies. Sources: cccc:webui, cccc:tasklistcode, cccc:cliref.
  • Agent stats [partial] Per-agent status/activity/live-update indicators; no aggregated per-agent statistics. Sources: cccc:webui.
  • Project stats [partial] Group list with statuses/counts; no project-level dashboards or aggregates. Sources: cccc:webui, cccc:cliref.
  • Time stats [partial] Event timestamps, last-run/next-run times, change ages; no time aggregates. Sources: cccc:arch, cccc:webui.
  • Failure status [supported] Running/Idle/Paused/Offline/Stopped plus per-delivery claimed/accepted/failed/ambiguous states stay visible. Sources: cccc:webui, cccc:features, cccc:cliref.
  • Approval status [supported] Waiting-for-you counts per Group and cross-Group, request states (open/answered/withdrawn/unknown) and answer tracking. Sources: cccc:features, cccc:webui.
  • Reconnect consistency [supported] Cursor-based reads, retained views, ledger-authority restore and unknown/stale marking keep state consistent across reconnects. Sources: cccc:webui, cccc:arch.
  • Performance method [unknown] Statistics, performance_method: the catalog measures none and no vendor speed figures appear in checked sources.
  • Responsiveness [unknown] Statistics, responsiveness: no latency figures are published and no installed-product fixture was run.

Sources: cccc:arch, cccc:cliref, cccc:faq, cccc:features, cccc:operations, cccc:supportdoc, cccc:tasklistcode, cccc:terminalhistory, cccc:webui

Agent cross-checked unsupported

CCCC tracks no model, API or compute spend anywhere: no per-task/session/child/epic costs, no harness aggregation, no billed-vs-estimated reconciliation, no token accounting, no budgets/alerts/exports and no drill-down. Cost visibility is limited to incidental provider-side figures inside runtime terminals; inference spend stays entirely on the user own runtime accounts.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • No cost dimension of any kind; provider-side spend is invisible to CCCC.
14 atomic answers

Sources: cccc:cliref, cccc:features, cccc:negsearch

Agent cross-checked partial

No compute-aware scheduling exists: no concurrency limits, queues, CPU/RAM awareness, backpressure, check reuse/dedup, bounded verification or fairness policies. Cancellation is the one supported control (cancel-reply, stop/restart, pause delivery); recovery reuses the ledger authority rather than scheduled capacity.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Coordination without compute scheduling; cancellation only.
12 atomic answers

Sources: cccc:arch, cccc:cliref, cccc:deliverycode, cccc:features, cccc:imbridge, cccc:negsearch, cccc:operations

Human collaboration and control

Agent cross-checked partial

Group state is shared to every holder of access (remote browsers, IM chats, read-only exhibits) with message discussion, reply/quote/forward comments and ledger attribution, but live human presence and simultaneous multi-human co-prompting do not exist: Connect links instances for message exchange rather than shared steering, and ordering/conflict handling for co-prompts is absent.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Single-user-oriented sharing; no live co-steering.
11 atomic answers
  • Visibility [supported] Shared Groups visible over remote access, IM bridges and read-only exhibit mode; Connect relays messages across instances. Sources: cccc:webui, cccc:imbridge, cccc:connect, cccc:cliref.
  • Discussion [supported] Group chat with threads via reply/quote/forward, review tables and outcome discussion; Waiting for you collects open items. Sources: cccc:webui, cccc:features.
  • Comments [supported] Reply/quote/forward plus Quick reply, Pin and Copy link per message; IM threads carry the same. Sources: cccc:webui, cccc:imbridge.
  • Presence [partial] Agent status dots/rings, activity indicators and terminal liveness show agent presence; no human presence indicators exist. Sources: cccc:webui.
  • Coprompting [unsupported] Collaboration, coprompting: bounded inspection found no simultaneous multi-human steering; a second human uses the same token/session or a separate linked instance. Sources: cccc:negsearch, cccc:webui, cccc:connect.
  • Ordering [unsupported] Collaboration, ordering: no co-prompt input ordering exists; message order follows ledger append. Sources: cccc:negsearch, cccc:webui, cccc:connect.
  • Conflicts [unsupported] Collaboration, conflicts: no co-prompt conflict handling exists; edit conflicts guard files/tasks only. Sources: cccc:negsearch, cccc:webui, cccc:connect.
  • Attribution [supported] Ledger sender attribution on every event; user vs agent addressing explicit in headers and receipts. Sources: cccc:arch, cccc:features.
  • Permissions [partial] Token-gated access with read-only exhibit and RBAC inside a Group; no per-human permission levels exist. Sources: cccc:webui, cccc:arch.
  • Plan restrictions [partial] No plan tiers restrict collaboration; remote scope needs an Admin token and reachable route, which is a security gate, not a plan. Sources: cccc:webui, cccc:cliref.
  • Owner online [partial] The originating owner need not stay online: daemon-owned work, recorded answers and IM/remote access continue; page drafts stay with their browser. Sources: cccc:operations, cccc:features, cccc:releasenotes.

Sources: cccc:arch, cccc:cliref, cccc:connect, cccc:features, cccc:imbridge, cccc:negsearch, cccc:operations, cccc:releasenotes, cccc:webui

Agent cross-checked partial

Per-group user/foreman/peer roles with a daemon-enforced permission matrix plus per-task assignees; account device membership and Connect member IDs; token-gated access with revocation (cut device, unlink, rotate). No organizations, no SSO/provisioning, no plan-scoped roles.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Group-local roles only; no org/SSO/provisioning.
9 atomic answers
  • Organization roles [unsupported] Roles, organization_roles: bounded inspection found no organization entity or org-level roles; accounts link devices, not orgs. Sources: cccc:negsearch, cccc:arch, cccc:account.
  • Project roles [supported] Per-group user/foreman/peer roles with documented capabilities (foreman manages any actor, peers only self). Sources: cccc:arch, cccc:cliref.
  • Task roles [supported] Assignee, owner and outcome fields per task plus foreman/peer task-op gating. Sources: cccc:webui, cccc:contextcode.
  • Membership [partial] Account device membership, Connect member invitations and IM subscribe authorization; no team roster management UI. Sources: cccc:connect, cccc:account, cccc:imbridge.
  • Sso [unsupported] Roles, sso: bounded search of docs, CLI and pinned sources found no single sign-on; sign-in is GitHub/Google/email-link plus local tokens. Sources: cccc:negsearch, cccc:arch, cccc:account.
  • Provisioning [unsupported] Roles, provisioning: no user provisioning/deprovisioning flow exists beyond device cut/unlink and token rotation. Sources: cccc:negsearch, cccc:arch, cccc:account.
  • Unauthorized access [partial] Loopback-only local principal, Admin-token gates for non-local, exhibit read-only; agent-runtime auth inherits providers. Sources: cccc:webui, cccc:arch.
  • Revocation [supported] Cut device, unlink account, withdraw Connect grants, remove subscriptions, rotate tokens, stop delivery. Sources: cccc:account, cccc:connect, cccc:features, cccc:imbridge.
  • Plan scope [unsupported] Roles, plan_scope: no plans or tiers exist, so no plan-scoped controls exist either. Sources: cccc:negsearch, cccc:arch, cccc:account.

Sources: cccc:account, cccc:arch, cccc:cliref, cccc:connect, cccc:contextcode, cccc:features, cccc:imbridge, cccc:negsearch, cccc:webui

Agent cross-checked partial

User decisions gate progress through in-place question answers (recorded, requester-verified, scoped to the open request) and tracked outcomes; capability allowlists govern tool visibility while runtime tool approvals stay inherited or deliberately bypassed with warnings. No network/secret approval flows exist; temporary access (tunnels, shares) is cut explicitly; exhibit mode and conservative safety are the safer defaults.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Decision gating is message-level; process-level approvals stay runtime-side.
14 atomic answers
  • Command [partial] Runtime command approvals are inherited or bypassed per runtime defaults with review-before-sensitive-work warnings; CCCC adds no command-approval gate of its own. Sources: cccc:runtimes, cccc:readme.
  • Tool [partial] Capability allowlist (indexed/mounted/enabled/pinned/blocked) governs tool visibility per group/global; approvals of individual tool calls stay runtime-side. Sources: cccc:allowlist.
  • Network [unsupported] Approvals, network: no network-access approval flow was located. Sources: cccc:negsearch, cccc:runtimes, cccc:allowlist.
  • Secret [unsupported] Approvals, secret: no secret-access approval flow was located; secrets are user-managed via actor secrets/env. Sources: cccc:negsearch, cccc:runtimes, cccc:allowlist.
  • Delivery [supported] Question-to-user requests with options/recommendation and in-place answers, plus tracked outcomes, gate delivery of decisions. Sources: cccc:features, cccc:webui.
  • Approver identity [supported] The user answers; the daemon accepts an answer only from the provably same requester while the request is open. Sources: cccc:features.
  • Lifetime [supported] Requests stay open until answered/withdrawn; paused/stopped groups record answers without delivering; Group rules note scoped lifetimes. Sources: cccc:features.
  • Allow [supported] Option choice, free-text answers and Other-with-note all record an approval decision in the ledger. Sources: cccc:webui, cccc:features.
  • Deny [partial] Decline paths exist (decline launch/trust, Other answers, stop/disable) but no explicit deny primitive is documented. Sources: cccc:readme, cccc:webui.
  • Revoke [supported] Cut devices, unlink accounts, withdraw Connect grants, stop groups, disable actors, uninstall capabilities. Sources: cccc:account, cccc:connect, cccc:cliref.
  • Tunnels [supported] Cut disables the device and deletes its tunnel/DNS; quick tunnel URLs are temporary; forwarding-header protections documented. Sources: cccc:account, cccc:webui.
  • Defaults [partial] Many managed runtimes start with approvals bypassed and connected sessions keep app prompts; safer behavior needs explicit review/setup. Sources: cccc:runtimes, cccc:readme, cccc:localsessions.
  • Safer modes [supported] Conservative external-capability safety mode, read-only exhibit mode, approval-preserving native sessions and token-gated remote access. Sources: cccc:allowlist, cccc:cliref, cccc:localsessions.
  • Enforcement [partial] RBAC and allowlist enforcement are daemon-kernel-enforced; agent process actions themselves are not product-enforced. Sources: cccc:arch, cccc:allowlist.

Sources: cccc:account, cccc:allowlist, cccc:arch, cccc:cliref, cccc:connect, cccc:features, cccc:localsessions, cccc:negsearch, cccc:readme, cccc:runtimes, cccc:webui

Agent cross-checked partial

Every action, approval, edit, discussion and decision lands attributed in the append-only ledger, persists across users/sessions/restarts, and exports through Copy Groups and ledger search. The ledger is append-only with verification/compaction (not a signed audit log); pins/tasks are mutable through guarded edits.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Durable and attributed, but not a signed audit trail.
11 atomic answers
  • Actions [supported] Actor/group lifecycle, messages, automation and delivery events append to the ledger with sender attribution. Sources: cccc:arch.
  • Approvals [supported] In-place answers and tracked outcomes record approvals as ledger events with the chosen option and notes. Sources: cccc:features.
  • Edits [supported] Task/backlog/file/guidance edits persist with version guards; reload paths keep them visible. Sources: cccc:webui, cccc:contextcode.
  • Discussion [supported] Full message history with threads, quotes and review tables persists per Group. Sources: cccc:webui, cccc:arch.
  • Decisions [supported] Decisions (chosen options, outcomes, written-back topic entries) persist in ledger and tasks. Sources: cccc:features, cccc:webui.
  • Cross user persistence [supported] Daemon-shared state: remote browsers, IM chats and linked instances read the same ledger/tasks. Sources: cccc:arch, cccc:connect, cccc:imbridge.
  • Cross session persistence [supported] Restarts, reconnects, new sessions and group copies preserve history; retained views reattach. Sources: cccc:operations, cccc:features.
  • Export [supported] Copy Groups export plus ledger search/tail and CCCC_HOME backup export history for review or migration. Sources: cccc:features, cccc:cliref, cccc:operations.
  • Mutability [partial] Ledger is append-only (reads fail closed on damage); tasks/pins/files mutate only through guarded, version-checked writes. Sources: cccc:arch, cccc:webui.
  • Retention [supported] Compaction retains history with large blobs separated; push payloads keep a day; account-side handled requests delete at 180 days. Sources: cccc:faq, cccc:features, cccc:account.
  • Integrity [partial] Maintenance validates and hashes ledger records in a streaming pass; no signed tamper-evident audit model is claimed. Sources: cccc:arch.

Sources: cccc:account, cccc:arch, cccc:cliref, cccc:connect, cccc:contextcode, cccc:faq, cccc:features, cccc:imbridge, cccc:operations, cccc:webui

Agent cross-checked partial

Reviewers work from Waiting for you with counts, read review tables and before/after evidence in chat, navigate diffs in Changes, reply/quote/forward with context, and delegate fixes via tracked tasks; drafts, filters and reading places survive context switches and phone layouts adapt. No formal request-changes state, no exact-revision approvals, no keyboard-shortcut system and no effort estimates exist.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Strong review reading; informal review actions.
13 atomic answers
  • Pending reviews [supported] Waiting-for-you filter with counts per Group and cross-Group totals, including stopped/archived groups. Sources: cccc:features, cccc:webui.
  • Change understanding [supported] Changes view with unified/side-by-side diffs, review tables in messages, before/after screenshot attachments, Agent State reports. Sources: cccc:webui, cccc:site.
  • Evidence navigation [supported] Resource panel tabs, message links, Show-in-chat, file/line anchors, task and backlog links keep evidence one click away. Sources: cccc:webui.
  • Comments [supported] Reply/quote/forward, quick replies, Copy link and per-message More actions on desktop and touch layouts. Sources: cccc:webui.
  • Request changes [partial] Change requests go as messages or tracked tasks with outcomes; no formal request-changes state or reviewer workflow exists. Sources: cccc:features, cccc:workflows.
  • Shipping guidance [partial] Workflows doc and next-action surfacing (Waiting for you, Run now, retry) guide shipping; no delivery queue or release checklist exists. Sources: cccc:workflows, cccc:webui.
  • Effort [unknown] Review, effort: no reviewer-effort estimates or sizing signals appear in the checked docs.
  • Missed evidence [partial] Unknown/stale Waiting-for-you counts are marked rather than zeroed; no missed-coverage guarantee beyond that marking. Sources: cccc:features, cccc:webui.
  • Keyboard [partial] Send shortcut in tooltip, Ctrl/Cmd+Enter and Ctrl/Cmd+S, arrow-key navigation in terminal UI and settings; no documented shortcut system. Sources: cccc:webui, cccc:cliref.
  • Narrow screen [supported] Responsive phone layouts: stacked columns, single-row composer, full-screen resource surface, touch menus, adaptive terminal paging. Sources: cccc:webui.
  • Context switching [supported] Drafts, filters, reading places, views and terminal pages survive switching groups/views and reloads (per browser). Sources: cccc:webui.
  • Roles [partial] Foreman/peer/reviewer patterns visible (Builder+Reviewer pair); no formal reviewer role or permission exists. Sources: cccc:workflows, cccc:arch.
  • Retained context [supported] Places kept 30 minutes, unsent drafts guarded with warnings, retained terminals/attachments keep review context. Sources: cccc:webui, cccc:releasenotes.

Sources: cccc:arch, cccc:cliref, cccc:features, cccc:releasenotes, cccc:site, cccc:webui, cccc:workflows

Agent cross-checked partial

A second authorized person continues the same work from another device over remote access (same Group, history, decisions, artifacts, terminal context) or via Connect/IM from their own instance (message-level continuity). Owner disconnect never blocks: the daemon persists, answers record, and native sessions keep their apps. No per-user ownership transfer or harness-transfer ceremony exists beyond switching runtimes.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Takeover is shared-access continuity, not a handover flow.
12 atomic answers
  • Ongoing takeover [supported] Same Group reachable with full state from another browser/IM client under shared access; Connect continues message-level work across instances. Sources: cccc:webui, cccc:connect, cccc:imbridge.
  • Same task [supported] Task IDs, backlog links and tracked outcomes are identical for whoever opens them. Sources: cccc:webui, cccc:contextcode.
  • Session history [supported] Ledger, terminal retention and Agent State give the newcomer full session history. Sources: cccc:arch, cccc:terminalhistory, cccc:webui.
  • Decisions [supported] Recorded answers, outcomes and written-back topics persist decisions across people. Sources: cccc:features, cccc:webui.
  • Artifacts [supported] Files, Changes, Presentation, pins and attachments are shared; Copy Groups ports them wholesale. Sources: cccc:webui, cccc:features.
  • Permissions [partial] Access is token-scoped (Admin token / account / exhibit); no per-user permission transfer or delegation exists. Sources: cccc:webui, cccc:arch.
  • Runtime context [supported] Terminals, activity and delivery state are shared over remote access; Connect explicitly excludes terminal/workspace access. Sources: cccc:webui, cccc:connect.
  • Owner disconnect [supported] Daemon-owned Groups persist; paused/stopped groups record answers, native apps stay open, reconnect restores. Sources: cccc:operations, cccc:localsessions, cccc:features.
  • Ownership [partial] Foreman/assignee fields reassign work; no human-ownership transfer flow is documented. Sources: cccc:arch, cccc:webui.
  • Attribution [supported] Ledger attribution distinguishes each sender across the handover. Sources: cccc:arch.
  • Context loss [partial] Durable state transfers fully; transient terminal modes, page drafts and unread-bubble state do not. Sources: cccc:runtimes, cccc:releasenotes.
  • Harness transfer [supported] Switch an agent runtime mid-stream with documented resume/acceptance steps per runtime. Sources: cccc:localsessions, cccc:runtimes, cccc:cliref.

Sources: cccc:arch, cccc:cliref, cccc:connect, cccc:contextcode, cccc:features, cccc:imbridge, cccc:localsessions, cccc:operations, cccc:releasenotes, cccc:runtimes, cccc:terminalhistory, cccc:webui

Verification and delivery

Agent cross-checked partial

Diffs (read-only Changes view), documents (Files editor), screenshots/recordings attachments, HTML/Markdown previews, review tables and agent-reported test outputs persist linked to tasks and revisions; Presentation slots and pins form the cross-task gallery; completed child findings persist as outcomes and Agent State. No cross-task artifact search or prompt-leakage statement exists.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • No gallery search; test evidence is message-grade; prompt exposure unstated.
13 atomic answers
  • Diffs [supported] Changes view lists working-tree/staged/conflicts/untracked with unified/side-by-side diffs; read-only by design. Sources: cccc:webui.
  • Documents [supported] Workspace editor with save/conflict/reload semantics, 1 MiB text limit, CSV/Markdown/Mermaid rendering, downloads. Sources: cccc:webui.
  • Screenshots [supported] Image attachments with shared graphics viewer (fit/actual/zoom/pan), before/after review screenshots, Presentation images. Sources: cccc:webui, cccc:site.
  • Recordings [partial] Voice recordings become transcripts/documents via Secretary; terminal transcripts persist boundedly; no screen recordings. Sources: cccc:voicesec, cccc:terminalhistory.
  • Previews [supported] Static isolated HTML previews, Markdown rendering, CSV tables, PDF/video native viewers, embedded browser views. Sources: cccc:webui.
  • Test outputs [partial] Agent-reported validation evidence (e.g. pnpm test tallies) arrives as messages/outcomes; no product test-output artifact type. Sources: cccc:site, cccc:features.
  • Reviewer outputs [supported] Review tables, before/after evidence and outcomes persist in messages and tasks. Sources: cccc:site, cccc:features.
  • Persistence [supported] Ledger/blobs/context/tasks survive restarts; retained terminals/views expire by policy; copies carry history. Sources: cccc:arch, cccc:webui.
  • Child findings [supported] Peer/foreman findings return as replies, outcomes and Agent State reports, retained in the ledger. Sources: cccc:features, cccc:webui, cccc:workflows.
  • Prompt leakage [unknown] Retained artifacts, prompt_leakage: no statement on prompt/system-prompt exposure in artifacts was located. Checked the CCCC site, docs guides, CLI/architecture references, release notes and the pinned source at v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8); no installed-product fixture was run.

Sources: cccc:arch, cccc:contextcode, cccc:features, cccc:site, cccc:terminalhistory, cccc:voicesec, cccc:webui, cccc:workflows

Agent cross-checked unsupported

CCCC enforces no verification or spec gates: no test/lint/type/CI/review/spec checks, no required checks, no failure blocking and no configured or enforced policy. Tracked outcomes record validation evidence as text and reviewers iterate in chat, but a done task without an outcome only gets a suggestion and type requirements never block.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Evidence recorded, never gated.
11 atomic answers

Sources: cccc:features, cccc:negsearch, cccc:webui

Agent cross-checked partial

Git stays terminal- and agent-side: CCCC surfaces read-only diffs and conflict displays, documents branch/worktree conventions (including Claude background worktrees) and conflict inspection, but never stages, discards, commits, pushes, rebases or opens pull requests, and owns no PR state.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Read-only Git visibility; all mutation is runtime-side.
9 atomic answers
  • Branches [partial] Branch work runs through runtime CLIs with handoff guidance (name directory and branch); product tracks no branches. Sources: cccc:runtimes.
  • Worktrees [partial] Worktree conventions documented with creation/cleanup commands; CCCC creates/manages none and never guarantees runtime cleanup. Sources: cccc:runtimes, cccc:faq.
  • Commits [unsupported] Git workflow, commits: CCCC never commits; Changes is read-only and agents commit via their own tools. Sources: cccc:negsearch, cccc:webui, cccc:runtimes.
  • Pull requests [unsupported] Git workflow, pull_requests: no product PR creation or management exists; agents discuss/ask for reviews in chat. Sources: cccc:negsearch, cccc:webui, cccc:runtimes.
  • Comments [unsupported] Git workflow, comments: no PR review-comment integration exists; message reply/quote is the comment surface. Sources: cccc:negsearch, cccc:webui, cccc:runtimes.
  • Ci response [unsupported] Git workflow, ci_response: no CI integration or response handling exists. Sources: cccc:negsearch, cccc:webui, cccc:runtimes.
  • Rebase [unsupported] Git workflow, rebase: no rebase support exists. Sources: cccc:negsearch, cccc:webui, cccc:runtimes.
  • Conflicts [partial] Conflict entries display with current-file inspection; resolution stays in terminal/agents. Sources: cccc:webui.
  • Product state [partial] Read-only Git state view (Changes) with saved-content semantics; no product-owned PR/merge state. Sources: cccc:webui.

Sources: cccc:faq, cccc:negsearch, cccc:runtimes, cccc:webui

Agent cross-checked unsupported

CCCC owns no merge or deployment authority: no approve/merge/release/deploy actions, no exact-revision checks and no authority enforcement exist. Delivery authority stays with the user in their terminal, provider and hosting; the product coordinates and records instead.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Coordination only; authority stays outside the product.
6 atomic answers
  • Approve [unsupported] Merge authority, approve: no approval-of-delivery action exists (question answers approve decisions, not code). Sources: cccc:negsearch, cccc:cliref.
  • Merge [unsupported] Merge authority, merge: no merge action exists. Sources: cccc:negsearch, cccc:cliref.
  • Release [unsupported] Merge authority, release: no release action exists. Sources: cccc:negsearch, cccc:cliref.
  • Deploy [unsupported] Merge authority, deploy: no deploy action exists. Sources: cccc:negsearch, cccc:cliref.
  • Exact revision [unsupported] Merge authority, exact_revision: no exact-revision checks exist. Sources: cccc:negsearch, cccc:cliref.
  • Authority enforcement [unsupported] Merge authority, authority_enforcement: no delivery-authority enforcement exists. Sources: cccc:negsearch, cccc:cliref.

Sources: cccc:cliref, cccc:negsearch

Agent cross-checked partial

Delivery status is fully visible (runtime.delivery facts, lifecycle states, Waiting for you); outcomes, replies and attachments persist as retained evidence. But no commit/PR/build/deployment links, rollback/revert or stale-approval invalidation exist — recovery is backup restore or group-copy re-import, and concurrent saves conflict rather than invalidate.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Status and evidence without delivery mechanics.
9 atomic answers
  • Delivery status [supported] Per-recipient claimed/accepted/failed/ambiguous facts, Group lifecycle states and Waiting-for-you tracking. Sources: cccc:features, cccc:webui.
  • Retained evidence [supported] Outcomes, replies, attachments, Agent State reports and ledger history persist past delivery. Sources: cccc:features, cccc:webui.
  • Rollback [unsupported] Completion, rollback: no rollback exists; restore via CCCC_HOME backup or Copy Groups re-import. Sources: cccc:negsearch, cccc:features.
  • Revert [unsupported] Completion, revert: no revert exists. Sources: cccc:negsearch, cccc:features.
  • Stale approval invalidation [partial] Concurrent saves conflict instead of silently applying; no approval-invalidation-on-edit semantics exist. Sources: cccc:webui, cccc:contextcode.

Sources: cccc:contextcode, cccc:features, cccc:negsearch, cccc:webui

Agent cross-checked partial

High-volume shipping runs through Waiting for you, the board with attention filters, summaries in Agent State/stand-ups, review findings as tables, Presentation/pin artifacts and next-action surfacing — but with no unified review queue, risk/size filters, exact-revision approvals, dependency merge queues or check dedup. Request-changes and stale handling stay informal.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Review coordination without release mechanics.
12 atomic answers
  • Review queue [partial] Waiting-for-you filter plus board columns approximate a queue; no unified cross-group review queue exists. Sources: cccc:features, cccc:webui.
  • Summaries [partial] Agent State reports and stand-up summaries digest work; no per-change generated summaries exist. Sources: cccc:webui, cccc:features.
  • Grouping [partial] Board columns, attention filters and sender filters group work; no risk/size or release grouping exists. Sources: cccc:webui, cccc:tasklistcode.
  • Risk size filters [unsupported] Batch review, risk_size_filters: no risk/size filters were located. Sources: cccc:negsearch, cccc:features, cccc:webui.
  • Findings [supported] Review tables, outcomes and before/after evidence persist as retained findings. Sources: cccc:site, cccc:features.
  • Artifacts [supported] Presentation slots, pins, attachments and Files keep review artifacts navigable. Sources: cccc:webui.
  • Request changes [partial] Change requests travel as messages/tracked tasks; no formal request-changes flow with states exists. Sources: cccc:features, cccc:workflows.
  • Exact revision approval [unsupported] Batch review, exact_revision_approval: no exact-revision approval exists. Sources: cccc:negsearch, cccc:features, cccc:webui.
  • Dependency queues [unsupported] Batch review, dependency_queues: no dependency-aware merge/release queues exist. Sources: cccc:negsearch, cccc:features, cccc:webui.
  • Next actions [partial] Waiting for you, retry/reload prompts and workflow guidance surface next actions; no shipping checklist exists. Sources: cccc:features, cccc:workflows.
  • Stale approval invalidation [partial] Version-conflict guards prevent silent overwrites; no approval-staleness model exists. Sources: cccc:webui, cccc:contextcode.
  • Check deduplication [unsupported] Batch review, check_deduplication: no duplicate-check reuse was located. Sources: cccc:negsearch, cccc:features, cccc:webui.

Sources: cccc:contextcode, cccc:features, cccc:negsearch, cccc:site, cccc:tasklistcode, cccc:webui, cccc:workflows

Ownership, privacy and economics

Agent cross-checked partial

Apache-2.0 across the repository: root LICENSE grant covers daemon, Web UI, CLI, runtimes and docs; Cargo workspace and Python package metadata declare Apache-2.0. Source is fully visible at the pinned v0.4.55 commit; the hosted account/Connect service and the separate SDK repo are outside the licensed-repo parity picture.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Hosted account/relay service is closed with no parity statement.
6 atomic answers
  • Client license [supported] Web UI, CLI and daemon sources under root Apache-2.0 LICENSE; web bundle ships from the same licensed tree. Sources: cccc:license, cccc:pyproject.
  • Server license [supported] Daemon/core/runtime crates under the same Apache-2.0 grant (workspace Apache-2.0, member crates inherit). Sources: cccc:license, cccc:pyproject.
  • Hosted extensions [partial] Account/Connect hosted service and the separate cccc-sdk repo are outside this license picture; no separate hosted terms were located. Sources: cccc:account, cccc:readme.
  • Source visibility [supported] Public ChesterRa/cccc repository with full history, 111 forks, 20 open issues; sources, docs and screenshots readable. Sources: cccc:repohome.
  • Source revision [supported] Pinned release v0.4.55 commit b4e861f928236ed8441ccf9c13800ecfd44f1fb8 (2026-11-12); release tags for every version. Sources: cccc:releases.
  • Hosted parity [partial] Local behavior is source-proven; the closed account/relay service has no published parity statement with the repo. Sources: cccc:account.

Sources: cccc:account, cccc:license, cccc:pyproject, cccc:readme, cccc:releases, cccc:repohome

Agent cross-checked partial

Fully self-hosted on owned Linux/macOS/Windows or Docker with no required vendor services; optional Reach/account relay and user-chosen tunnels/VPNs only extend access. Copy Groups exports (zip) and imports durable state, CCCC_HOME backup/restore ports everything, formats are zip/JSONL/YAML/Markdown; account deletion cuts devices and removes the record while uninstalls intentionally keep data.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Workspace files and live state do not port; copies exclude secrets.
8 atomic answers
  • Self hosting [supported] Headless/systemd/container/Docker self-hosting with no vendor service required; local use needs no account. Sources: cccc:operations, cccc:docker, cccc:account.
  • Vendor dependencies [partial] Local operation needs none; remote/Connect optionally use the account service, pinned cloudflared helper and provider CLIs — all user-chosen and removable. Sources: cccc:webui, cccc:cliref, cccc:runtimes.
  • Export [supported] Copy Groups export (ledger/history/agents/context/automation/settings) plus whole CCCC_HOME backup. Sources: cccc:features, cccc:operations.
  • Import [supported] Copy Groups import with collision-safe copies and workspace remapping; no external-tracker import exists. Sources: cccc:features.
  • Formats [supported] Zip packages, JSONL ledger, YAML group/config, Markdown backlog, JSON CLI output. Sources: cccc:features, cccc:arch, cccc:cliref.
  • Cancellation [supported] Account deletion cuts every device and deletes the record; uninstall keeps CCCC_HOME data by design with documented removal steps. Sources: cccc:account, cccc:faq.
  • Account independence [supported] Everything local works without an account; unlinking only ends Connect/Reach authority. Sources: cccc:account, cccc:connect.
  • History portability [partial] History/tasks/context port via copies and backups; pins, credentials, live runtime state and workspace files do not port. Sources: cccc:features.

Sources: cccc:account, cccc:arch, cccc:cliref, cccc:connect, cccc:docker, cccc:faq, cccc:features, cccc:operations, cccc:runtimes, cccc:webui

Agent cross-checked partial

Code, prompts, credentials, logs and artifacts live on the user machine under CCCC_HOME (owner-only permissions) and are never uploaded by the product; Connect/Reach relay only messages/files between the user machines, and the account service stores just identities, device/host records and connection metadata with 180-day handled-request deletion. No telemetry client or statement, training-use, residency or subprocessor statements were found; provider separation holds via BYO runtime logins (CCCC even disables some provider telemetry flags).

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Local-first is structurally evidenced; business/privacy attestations are absent.
15 atomic answers
  • Code data [supported] Workspaces stay on the CCCC host; Reach/Connect upload neither repository nor ledger — only messages/replies/small files relay. Sources: cccc:arch, cccc:connect, cccc:account.
  • Prompts [partial] Prompts persist in the local ledger and go to the user configured providers; CCCC adds no prompt store of its own. Sources: cccc:arch, cccc:runtimes.
  • Credentials [supported] Actor secrets in CCCC_HOME/state/secrets with key-metadata-only reads, IM tokens env-preferred, provider credentials in runtime logins, all excluded from copies. Sources: cccc:features, cccc:cliref, cccc:imbridge.
  • Logs [supported] Daemon/terminal/ledger logs local; account service keeps sign-in/device/hostname/last-seen records only. Sources: cccc:operations, cccc:account, cccc:terminalhistory.
  • Artifacts [supported] Blobs/attachments under CCCC_HOME; Connect carries small files only; media streams directly without cloud upload/transcode. Sources: cccc:arch, cccc:connect, cccc:webui.
  • Retention [partial] History retained with compaction; push payloads kept a day; account handled requests deleted 180 days after last update; per-Group retention policies unstated. Sources: cccc:faq, cccc:features, cccc:account.
  • Deletion [supported] Task/archive/delete, pin removal, device cut, account deletion (removes record, cuts devices), uninstall keeps data by explicit design. Sources: cccc:webui, cccc:account, cccc:faq.
  • Training [unknown] Data handling, training: no training-use statement in checked sources. Business/hosted-service fact. Checked the CCCC site, docs guides, CLI/architecture references, release notes and the pinned source at v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8); no installed-product fixture was run.
  • Residency [unknown] Data handling, residency: no residency/location statement in checked sources. Business/hosted-service fact. Checked the CCCC site, docs guides, CLI/architecture references, release notes and the pinned source at v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8); no installed-product fixture was run.
  • Subprocessors [unknown] Data handling, subprocessors: no subprocessor list in checked sources. Business/hosted-service fact. Checked the CCCC site, docs guides, CLI/architecture references, release notes and the pinned source at v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8); no installed-product fixture was run.
  • Telemetry disclosure [unsupported] Data handling, telemetry_disclosure: bounded code and docs search located no product telemetry client and no telemetry statement to disclose. Sources: cccc:negsearch, cccc:account.
  • Telemetry defaults [unsupported] Data handling, telemetry_defaults: no telemetry exists to default; no usage-sharing defaults were located. Sources: cccc:negsearch, cccc:account.
  • Telemetry controls [unsupported] Data handling, telemetry_controls: no telemetry controls exist; bounded search found no opt-out because there is no telemetry to disable. Sources: cccc:negsearch, cccc:account.
  • Provider separation [supported] Orchestration data stays local while inference/voice go to the user providers; CCCC needs no provider key and disables GROK/PI provider telemetry flags in managed launches. Sources: cccc:runtimes, cccc:localsessions.

Sources: cccc:account, cccc:arch, cccc:cliref, cccc:connect, cccc:faq, cccc:features, cccc:imbridge, cccc:localsessions, cccc:negsearch, cccc:operations, cccc:runtimes, cccc:terminalhistory, cccc:webui

Agent cross-checked partial

CCCC has no paid plan and no prices: free Apache-2.0 download (install script, pip wheel, Docker, source) with no currency, intervals, seats, overages, taxes or credits anywhere in the checked sources. Agent spend is the user own existing subscriptions or API accounts, handled provider-side.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Priced dimensions are absent because no paid plan exists; no purchase or billing test was run.
12 atomic answers
  • Currency [unknown] Price, currency: No prices, plans, seats, trials, credits or billing appear in the checked site, docs, account pages or CLI reference; the product is free open-source with provider-side spend. Business/hosted-service fact.
  • Interval [unknown] Price, interval: No prices, plans, seats, trials, credits or billing appear in the checked site, docs, account pages or CLI reference; the product is free open-source with provider-side spend. Business/hosted-service fact.
  • Seats [unknown] Price, seats: No prices, plans, seats, trials, credits or billing appear in the checked site, docs, account pages or CLI reference; the product is free open-source with provider-side spend. Business/hosted-service fact.
  • Seat minimum [unknown] Price, seat_minimum: No prices, plans, seats, trials, credits or billing appear in the checked site, docs, account pages or CLI reference; the product is free open-source with provider-side spend. Business/hosted-service fact.
  • Workspace fees [unknown] Price, workspace_fees: No prices, plans, seats, trials, credits or billing appear in the checked site, docs, account pages or CLI reference; the product is free open-source with provider-side spend. Business/hosted-service fact.
  • Included usage [unknown] Price, included_usage: No prices, plans, seats, trials, credits or billing appear in the checked site, docs, account pages or CLI reference; the product is free open-source with provider-side spend. Business/hosted-service fact.
  • Credits [unsupported] Price, credits: no credits are sold or mentioned; spend is provider-side. Sources: cccc:negsearch, cccc:readme.
  • Trial [unknown] Price, trial: no trial is stated; the product itself is free. No prices, plans, seats, trials, credits or billing appear in the checked site, docs, account pages or CLI reference; the product is free open-source with provider-side spend. Business fact.
  • Overages [unknown] Price, overages: No prices, plans, seats, trials, credits or billing appear in the checked site, docs, account pages or CLI reference; the product is free open-source with provider-side spend. Business/hosted-service fact.
  • Taxes [unknown] Price, taxes: No prices, plans, seats, trials, credits or billing appear in the checked site, docs, account pages or CLI reference; the product is free open-source with provider-side spend. Business/hosted-service fact.
  • Model cost [supported] Agent cost is the user own existing subscriptions or API accounts, handled provider-side; CCCC sells no tokens. Sources: cccc:readme, cccc:localsessions.
  • Compute cost [unknown] Price, compute_cost: execution is user machines with no product metering. No prices, plans, seats, trials, credits or billing appear in the checked site, docs, account pages or CLI reference; the product is free open-source with provider-side spend. Business fact.

Sources: cccc:localsessions, cccc:negsearch, cccc:readme

Agent cross-checked partial

No scenario can be priced in-product because the product itself costs $0 and all variable spend is provider-side and unstated: one, two and five developers run the same free download with their own runtime accounts, concurrency/token/compute assumptions unstated. Fixed cost is $0; unknown cost is whatever the chosen providers charge.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Only the $0 product cost is statable; workload costs are provider-side.
11 atomic answers
  • One person [unknown] Scenario cost, one_person: provider spend unstated; product cost $0. Business fact. Checked the CCCC site, docs guides, CLI/architecture references, release notes and the pinned source at v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8); no installed-product fixture was run.
  • Two people [unknown] Scenario cost, two_people: two developers collaborate over Connect/remote on free installs; provider spend unstated. Business fact. Checked the CCCC site, docs guides, CLI/architecture references, release notes and the pinned source at v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8); no installed-product fixture was run.
  • Five people [unknown] Scenario cost, five_people: same free installs plus provider accounts; no team pricing exists. Business fact. Checked the CCCC site, docs guides, CLI/architecture references, release notes and the pinned source at v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8); no installed-product fixture was run.
  • Task assumptions [partial] Single helper through multi-agent team patterns documented; concurrency/token/compute assumptions unstated. Sources: cccc:workflows.
  • Concurrency [unknown] Scenario cost, concurrency: no concurrency quotas or metered parallelism. Checked the CCCC site, docs guides, CLI/architecture references, release notes and the pinned source at v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8); no installed-product fixture was run.
  • Tokens [unknown] Scenario cost, tokens: no token accounting. Checked the CCCC site, docs guides, CLI/architecture references, release notes and the pinned source at v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8); no installed-product fixture was run.
  • Compute hours [unknown] Scenario cost, compute_hours: execution is user hardware, unmetered. Checked the CCCC site, docs guides, CLI/architecture references, release notes and the pinned source at v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8); no installed-product fixture was run.
  • Fixed cost [supported] Product fixed cost is $0: free download, installers, Docker and source with no license fee. Sources: cccc:readme, cccc:license.
  • Variable cost [unknown] Scenario cost, variable_cost: only provider-side spend varies, unstated by product sources. Business fact.
  • Included cost [unknown] Scenario cost, included_cost: no included-usage schedule exists. Business fact.
  • Unknown cost [supported] Unknown cost is provider-side (runtime subscriptions/API usage) plus user hardware; the product meters nothing. Sources: cccc:readme.

Sources: cccc:license, cccc:readme, cccc:workflows

Agent cross-checked partial

Stable-channel product (0.4.55, Production/Stable classifier, near-daily releases) with public installers and no access gates; support runs through GitHub issues, Discord and Telegram with diagnostics tooling, and security reports get 3-business-day acknowledgment/7-day triage. No status page exists; no shutdown/deprecation is announced; export runs through Copy Groups and CCCC_HOME backup.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Support/status facts are gaps; deprecation absence is not a finding.
8 atomic answers
  • Release stage [supported] Stable releases (0.4.55 latest, stable channel default) with RC channel; pyproject Development Status 5 Production/Stable. Sources: cccc:releases, cccc:pyproject, cccc:cliref.
  • Access restrictions [supported] Public GitHub releases, installers, pip, Docker and source with no gates; remote exposure needs an Admin token as a security policy, not a tier. Sources: cccc:readme, cccc:releases, cccc:webui.
  • Support [supported] GitHub issues with report template, cccc doctor diagnostics, SUPPORT.md resources, Discord and Telegram communities. Sources: cccc:supportdoc, cccc:readme.
  • Response commitments [partial] Security reports: acknowledgment within 3 business days, triage within 7; general support has no response commitments. Sources: cccc:security.
  • Release activity [supported] v0.4.55 on 2026-11-12 with near-daily cadence (v0.4.50-54 in the prior week); per-version release notes and changelog. Sources: cccc:releases, cccc:releasenotes.
  • Status history [unknown] Availability, status_history: no status page or history was located. Business/hosted-service fact. Checked the CCCC site, docs guides, CLI/architecture references, release notes and the pinned source at v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8); no installed-product fixture was run.
  • Deprecation [unknown] Availability, deprecation: no deprecation or shutdown notice exists; absence is not a finding. Checked the CCCC site, docs guides, CLI/architecture references, release notes and the pinned source at v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8); no installed-product fixture was run.
  • Export options [supported] Copy Groups export and CCCC_HOME backup/restore port groups, history and settings. Sources: cccc:features, cccc:operations.

Sources: cccc:cliref, cccc:features, cccc:operations, cccc:pyproject, cccc:readme, cccc:releasenotes, cccc:releases, cccc:security, cccc:supportdoc, cccc:webui

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

Agent cross-checked partial

The free Apache-2.0 download/installer/Docker/source is the ongoing free tier with no paid plan, trial, credits, card or gates: phone access, BYO subscriptions, Connect collaboration and review all work free. Self-hosting costs are the user own hardware plus provider accounts; no usage caps beyond incidental product limits exist.

Scope
Surfaces: CCCC Web UI (desktop/mobile browser, PWA, exhibit), cccc CLI and interactive terminal interface, IM bridge bots (Telegram/Slack/Discord/Mattermost/Feishu/DingTalk/WeCom/Weixin), MCP server and agent tool surface · Version: Repository v0.4.55 (b4e861f928236ed8441ccf9c13800ecfd44f1fb8) 2026-11-12; first-party source pass 2026-11-13. · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
2026-11-13
  • Free means the whole product; provider spend stays provider-side.
10 atomic answers

Sources: cccc:account, cccc:cliref, cccc:connect, cccc:license, cccc:negsearch, cccc:readme, cccc:runtimes, cccc:site, cccc:webui, cccc:workflows

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

Sources

cccc:negsearch

Bounded no-implementation search (pinned release)

Bounded search at the pinned release found no implementation or statement for: product telemetry clients or telemetry/consent UI (telemetry/analytics/posthog/sentry hits are provider flags CCCC disables, not product telemetry); SSO/SAML/OIDC/SCIM; editor/IDE extensions (vscode/vsix); local-model runtimes (ollama/lmstudio/llama.cpp); product PR/merge/release/deploy mechanics (gh pr/pull request hits are chat examples); spend/token/turn/time limits or cost tracking (budget/max_tokens/rate_limit hits are unrelated); concurrency quotas or CPU/RAM scheduling (concurrency/cpu_limit/memory_limit hits are dispatch locks); third-party MCP consumption by CCCC itself; OS/process/network sandboxing for agents; webhooks (only provider-side routine/task events); audit export; issue/label/epic entities beyond tasks; workspace export/import beyond Copy Groups; pricing, plans, seats, trials, credits, billing or status pages. Search terms: telemetry, analytics, sentry, sso, saml, oidc, scim, vscode, vsix, ollama, local model, pull request, spend_limit, token_limit, budget, max_tokens, concurrency, cpu_limit, memory_limit, webhook, sandbox, container, microvm, audit, kanban, export, pricing, billing, status page.

Kind
source-inspected
Locator
Grep across crates/*/src, web/src, docs/**, resources/ at v0.4.55 plus bounded site/docs/CLI search
Source date
2026-11-12
Retrieved
2026-11-13
Commit
b4e861f928236ed8441ccf9c13800ecfd44f1fb8
Path
.
cccc:readme

CCCC README

Install via shell installer, PowerShell, or pip wheel (native executable in platform wheel); platforms Linux x86-64 glibc 2.28+, Apple Silicon macOS 11+, Windows x86-64. cccc starts daemon+Web UI (+status panel); headless mode; Admin Access Token before non-local exposure; managed Remote Access via pinned cloudflared.

Kind
documented
Locator
What CCCC does; Quick start install/launch; runtimes table; reach/ccccc from anywhere; CLI cheat sheet; installation and upgrades
Source date
2026-11-12
Retrieved
2026-11-13
cccc:webui

Web UI Guide

Mobile-first React control plane: Messages/Terminals views, @mentions, reply/forward/pin, task board with Planned/Active/Done + backlog, AGENTS.md/Agent State/Skills panels, file browser with Git Changes (read-only diffs), Web Push notifications, automation rules, IM bridge config, LAN/tunnel/Tailscale remote access, Admin token security model.

Kind
documented
Locator
Accessing; interface overview; message/terminal views; files; search; tasks; settings; notifications; automation; mobile; remote access; security
Source date
2026-11-12
Retrieved
2026-11-13
cccc:cliref

CLI Reference

Full cccc CLI: daemon lifecycle, attach/groups/group/use, actor add/start/stop/restart/new-session/remove/secrets, send/tracked-send/reply/deliver/cancel-reply/inbox/inbox-summary/tail/ledger search, im, space, setup, update, web, mcp; CCCC_HOME/WEB_HOST/WEB_PORT env vars.

Kind
documented
Locator
Global/daemon/group/agent/message/IM/space/setup/update/web/MCP commands; environment variables
Source date
2026-11-12
Retrieved
2026-11-13
cccc:features

Features

Send/Send+Reply/Mail contracts, consuming inbox reads, runtime.delivery facts, in-place question answers, 100 pins per group, push notification semantics, automation triggers/actions, per-actor secrets, Copy Groups export/import.

Kind
documented
Locator
Messaging contracts; mail inbox; delivery; questions to user; pins; notifications; IM bridge; automation; actor secrets; Copy Groups
Source date
2026-11-12
Retrieved
2026-11-13
cccc:faq

FAQ

Not a DAG workflow orchestrator; requirements Linux x86-64 glibc 2.28+/Apple Silicon macOS 11+/Windows x86-64 + agent CLI; 16 named CLIs + custom; read receipts via inbox reads; phone via tunnel/IM/Tailscale; no worktree cleanup by product.

Kind
documented
Locator
Positioning; install; system requirements; agents; messaging; remote access; performance; troubleshooting
Source date
2026-11-12
Retrieved
2026-11-13
cccc:connect

CCCC Connect

Connect links selected Groups across instances (same account, member invite, or direct no-account pairing); carries messages/replies/small files only, not terminals/workspace; each instance keeps its own state.

Kind
documented
Locator
Same-account, different-member, direct connections; delivery and permissions
Source date
2026-11-12
Retrieved
2026-11-13
cccc:imbridge

IM Bridge Setup

Telegram/Slack/Discord/Mattermost/Feishu-DingTalk/WeCom/Weixin bridges: token setup, /send /status /pause /resume, subscribe authorization; Weixin direct-bot-chats only.

Kind
documented
Locator
Supported platforms; configuration; commands
Source date
2026-11-12
Retrieved
2026-11-13
cccc:releasenotes

CCCC v0.4.55 Release Notes

v0.4.55 adds project backlog Markdown file with Tasks|Backlog switch, PATH-change resume, notes removal, blocked-task fix (#201), plus upgrade caveats (in-page drafts/unsent edits live only in open page).

Kind
documented
Locator
Backlog; resume; group rules; coordination notes removed; fixes; upgrade notes
Source date
2026-11-12
Retrieved
2026-11-13
cccc:manifestweb

Web app manifest

PWA manifest present: name CCCC, display standalone, icons; the Web UI is an installable standalone-display web app, not a native mobile/desktop client.

Kind
source-inspected
Locator
name, short_name, display standalone, theme, icons
Source date
2026-11-12
Retrieved
2026-11-13
Commit
b4e861f928236ed8441ccf9c13800ecfd44f1fb8
Path
web/public/manifest.webmanifest
cccc:runtimes

Supported Runtimes

Named runtimes: claude, codex, grok, opencode, kilo, copilot, cursor, devin, kiro, antigravity, droid, auggie, hermes, kimi, cline, amp, pi, deepseek, web_model, chatgpt_dots, grok_web_model, custom. Many start with approval prompts bypassed; managed Claude default bg worktree isolation; CCCC does not create/manage worktrees.

Kind
documented
Locator
First-class runtimes; autonomy defaults; setup commands; delivery and recovery; Git worktrees; verification
Source date
2026-11-12
Retrieved
2026-11-13
cccc:localsessions

Connect existing native sessions

User-run Codex/Claude/Pi/OpenCode V2 sessions join Groups via enable + connect; CCCC imports no history, needs no provider key; experimental, tested Linux/WSL, macOS/native Windows need acceptance testing; Antigravity cannot connect this way.

Kind
documented
Locator
Enable once; connect to Group; resume; delivery across reconnects; disconnect
Source date
2026-11-12
Retrieved
2026-11-13
cccc:workflows

Workflow Examples

Documented patterns: solo agent, builder+reviewer pair, multi-agent team, phone monitoring via tunnel/IM, overnight tasks with automation; reviewer agent pattern for validation.

Kind
documented
Locator
Solo, pair, multi-agent, remote monitoring, overnight tasks
Source date
2026-11-12
Retrieved
2026-11-13
cccc:webmodel

ChatGPT Web Model Runtime

Browser-delivered ChatGPT agent with remote MCP connector: sign-in + shared connector + bound conversation; bounded repository inspection and scoped editing; unverified delivery/unsent-draft boundaries listed.

Kind
documented
Locator
Setup; pairing; local image reading; local command execution; bounded repo inspection; current boundaries
Source date
2026-11-12
Retrieved
2026-11-13
cccc:skillcode

Slash skill dispatch

Agents invoke skill: capabilities via slash dispatch with fixed send mode; skills are installed capability packs, not free-form plugins.

Kind
source-inspected
Locator
skill:-prefixed capability IDs; task_text/command forwarding
Source date
2026-11-12
Retrieved
2026-11-13
Commit
b4e861f928236ed8441ccf9c13800ecfd44f1fb8
Path
crates/cccc-daemon/src/ops/messaging/slash_skill.rs
cccc:capsimportcode

Capability import

Capabilities install from explicit local path, URL or GitHub target with recorded provenance; remote search results stay unverified until imported from a trusted origin.

Kind
source-inspected
Locator
local path/URL/GitHub install; provenance records; unverified old search results excluded
Source date
2026-11-12
Retrieved
2026-11-13
Commit
b4e861f928236ed8441ccf9c13800ecfd44f1fb8
Path
crates/cccc-daemon/src/ops/capabilities/import.rs
cccc:account

Usage

Local CCCC works without an account; remote access publishes a public hostname. Stores sign-in identities, device names/hostnames, Group connections, private requests/replies; handled requests deleted 180 days after last update; account deletion removes the record. Preview remote access supports Linux and macOS; capacity/availability not guaranteed.

Kind
documented
Locator
Usage page: storage, retention, deletion, remote access preview
Source date
2026-11-13
Retrieved
2026-11-13
cccc:voicesec

Voice Secretary

Chet global assistant (text + experimental Codex/Grok voice using their logins, no extra API key) and Voice Secretary dictation/documents/live voice with local or cloud ASR options.

Kind
documented
Locator
Live voice providers; workspace modes; transcript/document actions; ASR options
Source date
2026-11-12
Retrieved
2026-11-13
cccc:groupspace

Notebook Binding + NotebookLM

Group Space binds NotebookLM work/memory notebooks via Google credential; ingestion/query/jobs are explicit agent/CLI operations; automatic two-way sync retired; disconnect keeps core workflows running.

Kind
documented
Locator
Provider activation; work/memory notebook binding; explicit ingestion
Source date
2026-11-12
Retrieved
2026-11-13
cccc:gettingstarted

Getting Started

Documented path from fresh install to first task: install, cccc launch, create Group, add agent, send message.

Kind
documented
Locator
Install, launch, create first Group
Source date
2026-11-12
Retrieved
2026-11-13
cccc:webquick

Web UI Quick Start

Web flow: open local workspace in browser, create Group from sidebar, add installed agent, start it, send/communicate.

Kind
documented
Locator
Open CCCC; create Group; add agent; start and communicate
Source date
2026-11-12
Retrieved
2026-11-13
cccc:docker

Docker Deployment

Docker deployment documented: build image from source, run container, verify; image includes Claude Code, Codex CLI and Factory CLI.

Kind
documented
Locator
Build image; run container; key environment variables
Source date
2026-11-12
Retrieved
2026-11-13
cccc:operations

Operations Runbook

Daemon recovery ladder (actor restart, group stop/start, daemon stop/start), health baseline (doctor, daemon status, groups), CCCC_HOME backup/restore, upgrade playbook, Mail advisory semantics.

Kind
documented
Locator
Topology; health checks; triage; recovery; secure remote access; upgrade; backup/restore; guardrails
Source date
2026-11-12
Retrieved
2026-11-13
cccc:arch

Architecture

Single Rust daemon owns groups/ledger/tasks/context/lifecycle; ledger.jsonl append-only under CCCC_HOME/groups/<id>/; foreman coordinates + works, peers manage only self; MCP capability groups; React+TS+Vite+Tailwind+xterm Web, Rust+Axum host.

Kind
documented
Locator
Working Group; Actor; Ledger; directory layout; roles and permissions; MCP server; tech stack
Source date
2026-11-12
Retrieved
2026-11-13
cccc:allowlist

Capability Allowlist

MCP capability governance: packaged default + user overlay, indexed/mounted/enabled/pinned/blocked levels, foreman-or-user group scope vs user-only global scope, external capability safety mode; explicitly not a sandbox for agent processes.

Kind
documented
Locator
Merge model; policy levels; discovery; daemon ops; web API; safety mode
Source date
2026-11-12
Retrieved
2026-11-13
cccc:bestpractices

Best Practices

AGENTS.md/CLAUDE.md watched files with change nudges, per-group protocol reference customization, Builder + Reviewer pair pattern, code review agents recommended.

Kind
documented
Locator
AGENTS.md instructions; protocol reference; agent combinations; code review agents
Source date
2026-11-12
Retrieved
2026-11-13
cccc:pyproject

cccc-pair package metadata

Distribution name cccc-pair 0.4.55, Apache-2.0, author ChesterRa, Development Status 5 Production/Stable, console environment, Linux/macOS/Windows classifiers, repo/issue URLs.

Kind
source-inspected
Locator
name/version/description/authors/license/classifiers/urls
Source date
2026-11-12
Retrieved
2026-11-13
Commit
b4e861f928236ed8441ccf9c13800ecfd44f1fb8
Path
pyproject.toml
cccc:tasklistcode

Task list operation

Daemon task store supports planned/active/done/archived statuses, blocked/waiting_user/handoff/unassigned attention filters, assignee/query filtering and optimistic tasks_version concurrency.

Kind
source-inspected
Locator
STATUSES planned/active/done/archived; ATTENTION_FILTERS blocked/waiting_user/handoff/unassigned; pagination; tasks_version
Source date
2026-11-12
Retrieved
2026-11-13
Commit
b4e861f928236ed8441ccf9c13800ecfd44f1fb8
Path
crates/cccc-daemon/src/ops/task_list.rs
cccc:contextcode

Context batch operations

Task mutations run as validated batches with compare-and-swap revisions and explicit task_conflict errors; role-gated so agent task operations follow the foreman/peer permission policy.

Kind
source-inspected
Locator
task operations with optimistic concurrency; task_conflict errors; foreman-gated task ops
Source date
2026-11-12
Retrieved
2026-11-13
Commit
b4e861f928236ed8441ccf9c13800ecfd44f1fb8
Path
crates/cccc-daemon/src/ops/context.rs
cccc:positioning

Positioning

CCCC is the coordination layer, not a replacement for agents; complements native agent teams, parallel task runners and IM gateways rather than replacing them.

Kind
documented
Locator
What CCCC deliberately is and is not
Source date
2026-11-12
Retrieved
2026-11-13
cccc:negindex

Pinned-tree negative search for repository indexing

Bounded inspection of the pinned tree (crates/*/src, web/src, docs/**) finds no repository-indexing service or index-backed retrieval implementation; retrieval is tool- and attachment-scoped.

Kind
source-inspected
Locator
crates/*/src, web/src, docs/** at pin b4e861f
Source date
Not stated
Retrieved
2026-11-13
Commit
b4e861f928236ed8441ccf9c13800ecfd44f1fb8
Path
crates/*/src, web/src, docs/**
cccc:site

CCCC — Coordinate your coding agents like a group chat

Local-first open-source group-chat orchestrator for Claude Code/Codex/etc: shared Group with ledger, Send/Send+Reply/Mail, foreman+peers, Web/terminal/CLI/MCP/IM sharing daemon state, Chet assistant, Connect across instances, phone remote ops.

Kind
documented
Locator
Home: hero, 01 The Group, 02 How it works, 03 Your agents, 04 Voice, 05 Connect, Get started, install/runtime/remote sections
Source date
2026-11-13
Retrieved
2026-11-13
cccc:deliverycode

Actor delivery worker

Deliveries carry bounded retry limits; daemon-settled claims without outcome become ambiguous and are not auto-retried; failed provider turns release the next delivery after their retry limit.

Kind
source-inspected
Locator
retry limits; claimed/accepted/failed/ambiguous delivery settlement
Source date
2026-11-12
Retrieved
2026-11-13
Commit
b4e861f928236ed8441ccf9c13800ecfd44f1fb8
Path
crates/cccc-daemon/src/ops/actor_delivery.rs
cccc:automationcode

Automation rules

Automation supports interval, cron and one-time triggers with optional max_runs; paused/stopped groups run none, idle groups suppress the built-in stand-up, resume restarts clocks.

Kind
source-inspected
Locator
interval/cron/one-time triggers; max_runs; paused/stopped/idle semantics
Source date
2026-11-12
Retrieved
2026-11-13
Commit
b4e861f928236ed8441ccf9c13800ecfd44f1fb8
Path
crates/cccc-core/src/automation.rs
cccc:terminalhistory

Terminal output retention

Native terminal output uses bounded memory with opt-in bounded per-agent transcript persistence; restart/shutdown boundaries documented.

Kind
documented
Locator
Bounded memory; cursor/restart boundaries; retention settings; shutdown behavior
Source date
2026-11-12
Retrieved
2026-11-13
cccc:supportdoc

Support

Support via GitHub issues with version/OS/command/repro template, cccc doctor diagnostics, Discord and Telegram community channels.

Kind
documented
Locator
Bug reports; feature requests; diagnostics
Source date
2026-11-12
Retrieved
2026-11-13
cccc:repohome

ChesterRa/cccc

Canonical repo ChesterRa/cccc: 1309 stars observed 2026-11-13, Apache-2.0, homepage https://cccc.sh/, Rust, topics include claude-code, codex-cli, multi-agent, local-first.

Kind
documented
Locator
Repository header: description, stars, license, homepage, topics
Source date
2026-11-13
Retrieved
2026-11-13
cccc:releases

CCCC 0.4.55

Latest stable release v0.4.55 published 2026-11-12, with near-daily prior releases (v0.4.50–v0.4.54 within the preceding week).

Kind
documented
Locator
Release v0.4.55 page: version, date, notes
Source date
2026-11-12
Retrieved
2026-11-13
cccc:license

Apache License 2.0

Root LICENSE is the Apache License, Version 2.0 grant covering the repository contents including daemon, Web UI, CLI and docs.

Kind
source-inspected
Locator
License grant, sections 1-9; Appendix
Source date
2026-11-12
Retrieved
2026-11-13
Commit
b4e861f928236ed8441ccf9c13800ecfd44f1fb8
Path
LICENSE
cccc:security

Security Policy

Security fixes prioritized for latest RC + stable; private advisories or maintainer email; acknowledgment within 3 business days, triage within 7.

Kind
documented
Locator
Supported versions; reporting; response expectations
Source date
2026-11-12
Retrieved
2026-11-13

Comparisons with CCCC

Compare CCCC with any other product on adecomparison.com.