CCCC v0.4.19 Release Notes
v0.4.19 is a focused runtime reliability patch for Windows actors, Codex app-server backed PTY sessions, and provider resume recovery.
The release does not introduce a new runtime model. It tightens the existing one: failed provider resumes should recover cleanly, fresh sessions should produce durable metadata where the provider supports it, and Windows process/PTY behavior should match the daemon's restart expectations more closely.
Runtime Resume Recovery
Failed PTY resumes are now treated as recoverable launch failures instead of terminal startup failures.
When a saved provider session cannot be resumed, CCCC marks that metadata as failed and starts a fresh actor. Claude and Gemini fallback launches continue to use explicit provider session IDs, so the newly started session can be recorded durably. Codex PTY keeps its existing status-capture based session discovery path.
Codex app-server backed PTY actors also recover more cleanly after stale thread metadata. If a saved thread cannot be resumed, the remote TUI starts against the app-server normally and records the fresh thread id from app-server notifications once it appears. This prevents later relaunches from repeatedly chasing the stale thread.
Windows Actor Reliability
Windows actor restart paths now handle more of the real process environment.
CCCC resolves Windows command shims before launching Codex app-server processes, terminates real app-server process trees more reliably during restart/stop, and answers the terminal capability queries used by Gemini and related PTY runtimes without duplicating replies when a real terminal writer is attached.
MCP runtime context recovery can now read parent and ancestor process environments on Windows, matching the existing POSIX recovery behavior more closely. This helps MCP commands recover CCCC_HOME, group, and actor identity when the immediate process environment is incomplete.
Codex Remote TUI Stability
Codex remote TUI startup now resumes known app-server threads when possible and falls back to a plain remote TUI when the saved thread is stale.
The shutdown path is also more bounded: websocket close operations no longer risk blocking indefinitely, observer websocket disconnects no longer imply actor stop, and remote TUI exit handling preserves provider resume metadata unless the app-server thread itself is known to be invalid.
Validation
The release expands coverage around the affected restart paths, including:
- Windows PTY terminal-query handling;
- Windows MCP runtime context recovery;
- Codex app-server thread resume and stale-thread fallback;
- Codex remote TUI shutdown semantics; and
- PTY resume failure recovery for Claude, Gemini, and Codex.
Why Upgrade
Upgrade to v0.4.19 if you run actors on Windows, rely on Codex app-server backed PTY sessions, or have seen actor relaunches get stuck after stale Claude, Gemini, or Codex resume metadata.
In short, v0.4.19 keeps the runtime session model simple while making failed resumes and Windows restarts recover more predictably.