CCCC v0.4.26 Release Notes

v0.4.26 is a reliability release for Web terminals, group sending, local memory, and daemon cleanup.

The main theme is making long-running CCCC groups feel less fragile. Terminal sessions reconnect with less missing output, read-only viewers are kept out of the terminal control path, stopped groups can be woken by sending instead of being blocked by stale browser state, and the ledger index is less likely to trip over SQLite writer contention during busy reads and writes.

More Reliable Web Terminals

Web terminal attach and reconnect now use the raw PTY byte stream as the source of truth.

When a browser connects to a running PTY actor, CCCC can replay the retained terminal backlog and seed the client from an absolute byte cursor. Reconnects resume from the byte gap instead of re-rendering a lossy text snapshot. This improves terminal continuity after tab refreshes, network hiccups, and WebSocket reconnects.

Terminal access control is also clearer:

• viewer connections can watch output without becoming terminal writers;
• control connections are explicit;
• control takeover is represented separately from normal viewing;
• read-only exhibit mode always attaches terminals as viewers and cannot steal control from an active operator.

The Web terminal also no longer recreates the live xterm instance when the user changes theme or terminal scrollback settings. Those settings are applied in place, which avoids a class of failures where the terminal looked connected but input or resize events were still bound to a disposed instance.

Better Terminal Diagnostics and Text Rendering

Terminal tails and diagnostics now render more accurately for wide CJK/fullwidth characters and alternate-screen terminal apps such as editors or full-screen TUIs.

This does not try to replace xterm for live terminal rendering. It improves the text snapshot paths used by diagnostics, terminal history, stopped terminal output, and debugging views so that copied or inspected output is easier to understand.

Group Sends Wake More Reliably

The Web composer no longer blocks a send just because the current runtime projection says no actor is running.

That browser-side state can be stale during group wake-up or actor refresh races. CCCC now lets the server-side send path decide whether a stopped group can wake, while still blocking explicit paused groups. This makes "send to wake" flows more predictable and avoids false disabled-send states after runtime transitions.

The chat view also avoids forcing the scroll position to the bottom while the user is browsing detached history, reducing jumps during active conversations.

First-Class Local Memory Operations

CCCC now exposes local memory operations through the daemon:

• memory_search;
• memory_get;
• memory_write;
• memory_profile_get;
• memory_health.

These operations sit on top of the existing local ReMe-backed memory store, so they do not introduce a second memory system. They give runtimes and integrations a stable daemon API for searching, reading, writing, and checking local group memory.

Runtime and Ledger Stability

Headless Codex and Claude session shutdown now waits briefly for worker threads to exit after the runtime process is stopped. This reduces stale stdout, stderr, websocket, and turn-loop threads after stop/restart flows.

Ledger index catch-up is now serialized with the append indexing path. This avoids transient SQLite writer-lock failures during busy ledger tail/search requests while another path is updating the same index.

Windows ConPTY installs avoid the newly regressed pywinpty 3.0.4 release while keeping the previously verified 3.0.3 path available. That keeps Windows PTY smoke tests and actor startup stable without forcing users back to the older 2.x line.

Smaller Web and Permission Fixes

This release also includes several focused fixes:

• reply uploads now reject invalid default recipients with a clear validation error;
• foreman actors can remove peer actors through the expected management path;
• task reference chips have stronger contrast in dark mode;
• composer image previews and stopped terminal output paths remain covered by focused regression tests.

Validation

The release was validated with targeted backend and frontend coverage for terminal attach modes, terminal replay cursors, read-only terminal viewing, runtime thread cleanup, local memory operations, ledger index locking, group send lifecycle projection, reply upload validation, terminal transcript rendering, and Web terminal reconnection behavior.

Why Upgrade

Upgrade to v0.4.26 if you use the Web terminal heavily, run public or read-only exhibit sessions, rely on group sends to wake stopped actors, use local memory tooling, or have seen intermittent ledger tail/search failures during active work.