CCCC v0.4.18 Release Notes

v0.4.18 is a runtime expansion and Voice Secretary reliability release.

The previous release reduced ambiguity for Codex PTY actors by separating terminal access from structured runtime state. This release continues that direction in two ways: it adds Hermes as a formally supported runtime, and it tightens the daily Web and Voice Secretary paths that depend on accurate daemon state.

The main theme is making runtime behavior explicit without adding more user-managed setup burden.

Hermes as a Supported Runtime

Hermes is now wired through CCCC as a first-class runtime.

CCCC can detect the Hermes CLI, report launch readiness, prepare the CCCC MCP server through Hermes' own MCP setup flow, and run a Hermes MCP test with probe actor identity. The new daemon IPC operations are documented as:

• runtime_hermes_status
• runtime_hermes_prepare
• runtime_hermes_mcp_test

Hermes follows the same practical integration model as Claude and Codex: CCCC uses the selected user Hermes home/profile instead of creating a separate managed profile. If a user explicitly sets HERMES_HOME, CCCC respects that as a normal runtime environment override. MCP setup keeps ${CCCC_HOME}, ${CCCC_GROUP_ID}, and ${CCCC_ACTOR_ID} placeholders in the saved Hermes config so each actor process resolves its own CCCC identity at launch time.

The Web UI also recognizes Hermes in runtime selectors and runtime display. Hermes receives its own logo asset, while ChatGPT Web Model now reuses the Codex logo so OpenAI-backed runtimes are visually consistent.

Runtime Logo Rendering

Runtime logos now render as branded assets on a stable light logo plate.

This fixes the dark-mode failure mode where a transparent black SVG could sit directly on a dark avatar background and become unreadable. The change is intentionally generic: PNG and SVG runtime logos both keep their original brand colors, and the UI provides the contrast surface instead of rewriting the asset colors for each theme.

Voice Secretary Reliability

Voice Secretary recording and transcript delivery are more robust.

The daemon now owns a TTL-based recording lease so multiple browser tabs, browsers, or devices cannot silently start competing Voice Secretary recording streams for the same CCCC home. A crashed or disconnected client no longer leaves the system permanently blocked because the lease expires.

Final ASR output is now represented explicitly, and transcript chunking handles CJK text more naturally. Voice input notification cursors were also tightened so new input is delivered to the assistant without relying on stale cursor state or emitting unnecessary duplicate nudges.

For document-centered workflows, the Web UI can request compact Voice Secretary state views and load document content explicitly. This reduces over-fetching, makes workspace document loading clearer, and keeps the activity stream focused on useful user-facing progress instead of transient process noise.

Runtime Session and Codex Stability

Codex app-server and PTY session handling received another hardening pass.

CCCC now has clearer app-server thread start/resume behavior for Codex, stronger handling for bootstrap-control failures, and safer restart semantics around saved provider session metadata. Closing an observer-side connection no longer stops a Codex PTY actor by accident, and restart paths are less likely to leave PTY state, app-server state, and stored runtime session metadata disagreeing with one another.

Actor restart flows also support explicit fresh-session behavior where appropriate, so users can intentionally clear saved provider session state instead of being forced back into an old provider conversation.

Web State Synchronization

The Web chat surface is less prone to stale or conflicting request state.

SSE handling now has a shared connection registry, reducing duplicate stream ownership and making reconnect behavior easier to reason about. Chat request paths include stronger freshness guards, and failed sends restore composer state instead of losing the user's draft. Formal ledger event updates also avoid triggering unnecessary slash-command refresh work.

Together, these changes make Web state feel less jumpy during active group work, especially when runtime events, assistant updates, and message delivery are happening at the same time.

IM and WeCom Polish

IM delivery preserves sender and mention context more consistently.

The bridge now carries inbound sender identity and mention-user metadata through more of the routing path, including outbound replies where the platform adapter can use that context. WeCom behavior was also hardened around its existing media and streaming paths.

Platform and Test Coverage

v0.4.18 includes a macOS projected-browser compatibility fix and expands coverage around the newly tightened runtime paths.

New and expanded tests cover Hermes runtime setup, MCP install behavior, Codex app threads, Voice Secretary final ASR and document loading, Web SSE/request freshness behavior, IM sender identity, runtime command defaults, and the macOS projected-browser path.

Why Upgrade

Upgrade to v0.4.18 if you want to:

• run Hermes actors as a supported CCCC runtime;
• configure Hermes MCP through CCCC without maintaining a separate managed profile;
• make Voice Secretary recording safer across multiple browser sessions;
• reduce stale Voice Secretary input notifications and noisy document activity;
• make Codex restart/session behavior less ambiguous;
• preserve Web composer drafts after failed sends;
• improve runtime logo readability in dark mode; and
• pick up broader tests around runtime setup, session state, IM routing, and Web synchronization.

In short, v0.4.18 broadens CCCC's supported runtime surface while continuing to reduce the amount of hidden state users have to reason about during real group work.