CCCC v0.4.29 Release Notes
v0.4.29 is a major collaboration and runtime expansion release.
The headline change is Group Bridge: CCCC can now connect trusted working groups across machines or teams, exchange explicit cross-group messages, and optionally grant remote read or full local-access tools when the relationship is trusted enough. This release also expands the supported runtime catalog, improves the MCP tool surface agents rely on, and cleans up several Web and IM bridge workflows around cross-group work.
Group Bridge Connects Trusted Remote Groups
Group Bridge turns CCCC from a single local working group into a network of trusted groups.
Users can now create a pairing invitation from one group, approve it from another CCCC instance, and manage the resulting connection from group settings. Each trusted remote group has an explicit access level:
- Messages lets groups exchange directed messages, including attachments.
- Read lets the trusted remote group inspect local context, repository content, and git state through remote MCP tools.
- Full extends that access to edits and command execution through the same local-access model used by native actors.
The design remains local-first. A bridge does not merge group state, does not make remote actors local actors, and does not grant read/full access unless the local group explicitly allows it.
Remote MCP Access and Attachments
Agents can now discover connected remote groups and use dedicated cccc_remote_* tools when a bridge grants access.
Read access includes context snapshots, repository inspection, repository search, and git status/diff/log. Full access adds repository mutation, patch application, shell execution, and long-running command sessions. Remote calls require an explicit remote_group_id, so agents can distinguish several connected groups without guessing from display names.
Cross-group attachment delivery is also supported. Users and agents can send files to trusted remote groups through the same message flow instead of manually copying artifacts between machines.
A More Usable Cross-Group Web Experience
The Web UI now treats remote groups as first-class recipients.
Remote groups appear in the composer recipient area, can be selected alongside local actors, and expose concise identifiers that users can copy when they want to tell an agent which remote group to contact or inspect. Remote messages are visually distinguished from local messages, while avoiding noisy internal ids in the message bubble.
The Group Bridge settings page was also reorganized around what users need to decide: which groups are trusted, what each remote group may do in the current group, and what access the current group has on the remote side after refresh.
Runtime Catalog Expansion
This release adds first-class runtime support for several more agent CLIs:
- Devin CLI
- Kiro CLI
- GitHub Copilot CLI
- Antigravity CLI
- Kilo Code CLI
- Cursor CLI
Runtimes with reliable MCP setup commands are handled through the usual automatic setup path. Runtimes that do not expose a stable non-interactive MCP installer use prompt-assisted MCP setup: CCCC injects an idempotent setup prompt that tells the runtime how to install the cccc MCP server only when it is not already available.
Gemini CLI has been removed from the formal runtime catalog after its personal-service path stopped being useful for CCCC users. Unsupported CLIs can still be run through the custom runtime path.
Better MCP Guidance and Local Inspection Tools
The MCP surface has been tightened for day-to-day agent work.
Message guidance now more clearly separates new messages from replies, so agents are less likely to answer an existing message with a fresh send. Reply and send results also include a concise checkpoint reminding the actor to resume any interrupted work after handling a message.
Repository search is more capable and more precise, including glob filtering for local and remote repository inspection. Help output and capability summaries were reduced to the information agents need in the moment instead of repeating long setup guidance on every turn.
Actor notes and related help surfaces now use more consistent product language, making actor-specific guidance easier to understand and manage.
IM Bridge and Web Reliability
This release includes a broad reliability pass around IM bridge processing and Web runtime behavior.
DingTalk handling was split into smaller sender, media, message, reaction, and API components, with fixes for image delivery metadata. IM bridge subprocesses now sanitize certificate-authority environment variables before launch, and bridge lifecycle/reaction handling has more focused tests.
Web streaming and cache behavior were hardened as well: stale in-flight actor/context reads are bypassed correctly after writes, stream-close handling is more explicit, and cross-group send failures are propagated instead of being shown as successful sends.
Documentation and Runtime Surfaces
README and reference docs now present Group Bridge as a primary CCCC capability and describe the runtime catalog as stable entrypoints/surfaces rather than exposing runtime-specific launch flags.
The supported runtime count is now documented consistently across the English, Chinese, and Japanese READMEs, and the Group Bridge section explains the Messages / Read / Full access model from a user perspective.
Validation
The release includes expanded backend and frontend coverage for Group Bridge pairing, routing, remote delivery, remote MCP access, attachment transfer, reply relay behavior, runtime setup, prompt-assisted MCP setup, repository search, IM bridge lifecycle, Web cache invalidation, and composer recipient behavior.
Why Upgrade
Upgrade to v0.4.29 if you want to coordinate CCCC groups across machines or trusted teams, use remote read/full MCP access between groups, send files across Group Bridge, or run newer CLI runtimes such as Devin, Kiro, Copilot, Antigravity, Kilo Code, or Cursor with CCCC.