CCCC v0.4.24 Release Notes

v0.4.24 adds first-class Grok Build runtime support, introduces a safer Reset group workflow, and fixes project attachment when CLI requests cross the daemon boundary.

The main theme is making day-to-day group operations smoother. Users can now run Grok Build actors through the same CCCC runtime surfaces as other supported CLIs, reset an experimental group without manually rebuilding it from scratch, and attach project directories reliably even when the daemon is running from a different working directory.

Grok Build Runtime Support

Grok Build is now a first-class PTY runtime in CCCC.

You can select grok from the CLI and Web runtime surfaces, use it in actor configuration and runtime profiles, see the Grok runtime logo in the Web UI, and run setup diagnostics through the normal CCCC runtime/MCP paths. The default launch command is grok, matching Grok Build's interactive CLI entrypoint.

CCCC's MCP stdio server was also tightened for clients such as Grok that send plain newline-delimited JSON instead of MCP Content-Length frames during initialization. The server now mirrors the inbound stdio framing style: plain JSON clients receive plain JSON responses, while framed clients continue to receive framed responses. Protocol negotiation also accepts the current Grok MCP initialization version while preserving compatibility with existing MCP clients.

Reset Group

Groups can now be reset without manually deleting and recreating them.

Reset group creates a clean replacement group and deletes the current group. It keeps the high-effort configuration users are likely to care about, including:

• group name and project scope;
• actor definitions and runtime configuration;
• stored actor secrets;
• automation rules and automation timing/settings.

It intentionally does not copy message history, memory, context, runtime sessions, or provider state. This makes it useful after experiments, failed runs, or messy exploratory work where the group configuration is still valuable but the working history should be discarded.

The Web UI exposes Reset group next to Delete group in the group edit dialog. The controls now use consistent contextual tooltips, and the reset confirmation dialog still explains that a new group ID will be created. The CLI also provides cccc group reset --group <id> --confirm <id> for scripted or terminal-based workflows.

More Reliable Project Attachment

cccc attach . and cccc group use now resolve paths in the CLI before sending requests to the daemon.

Previously, a relative path such as . could be interpreted relative to the daemon's process directory instead of the user's project console. In some setups this made an ordinary project attach look like an attempt to attach CCCC_HOME, producing errors such as workspace scope must be a project directory, not CCCC_HOME.

v0.4.24 fixes that boundary by sending absolute resolved paths from the CLI. The Web attach route also rejects relative paths with a clear error, so Web requests cannot silently depend on daemon cwd.

Validation

The release was validated with targeted coverage for:

• Grok runtime metadata, command defaults, setup commands, and Web runtime/logo surfaces;
• MCP stdio initialization for both plain JSON and Content-Length framed clients;
• Reset group behavior across daemon, CLI, Web, permissions, active-group handling, actor config, private secrets, scopes, and automation settings;
• CLI daemon-boundary path resolution for attach and group use;
• Web attach route behavior for absolute and relative paths;
• Web typecheck/lint coverage for the updated Reset group UI.

Why Upgrade

Upgrade to v0.4.24 if you want to run Grok Build actors in CCCC, need a fast way to reset experimental groups without rebuilding their configuration by hand, or saw cccc attach . fail because the daemon interpreted the project path relative to the wrong directory.