CCCC v0.4.21 Release Notes

v0.4.21 is a focused runtime operations release. It adds OpenCode as a first-class PTY runtime, makes Codex custom OpenAI-compatible endpoints easier to use in Docker deployments, and gives Web operators an explicit way to start a fresh Claude or Codex session when resume state is no longer wanted.

The release keeps the runtime model conservative: new session control clears CCCC's local resume metadata and starts the actor with the same settings, but it does not delete provider-side conversation history or introduce a provider session manager.

OpenCode Runtime Support

OpenCode is now available as a first-class PTY runtime across the main actor surfaces.

Users can select OpenCode from the Web actor configuration flow, runtime profile views, CLI actor commands, setup diagnostics, and runtime detection. OpenCode actors use the normal CCCC actor lifecycle and PTY terminal surface.

CCCC also wires MCP for OpenCode at actor launch time through OpenCode's runtime configuration environment, instead of editing a global OpenCode config file. This keeps each actor's CCCC group and actor identity scoped to the runtime process that is being launched.

The Web runtime selector and runtime avatar surfaces were updated alongside the new runtime. The selector is searchable so the full runtime list remains discoverable as more supported runtimes are added, and OpenCode has its own logo treatment in the Web UI.

Codex Docker Endpoint Configuration

Docker deployments can now use OPENAI_BASE_URL as the CCCC compatibility entry for Codex custom endpoints.

When launching Codex actors, CCCC maps OPENAI_BASE_URL into Codex CLI's openai_base_url runtime config. This applies to the normal Codex PTY path and the Codex app-server backed path, so Docker Compose users can rotate or switch OpenAI-compatible endpoints with the same environment variable they already expect to configure.

The Docker .env example and Docker getting-started guide now call out this mapping explicitly.

Fresh Session Control for Claude and Codex

The Web actor detail panel now includes a New Session action for Claude and Codex actors.

This is intended for the common operator case where a saved resume session fails, points at stale provider state, or is simply not the session the user wants to continue. The action asks for confirmation, stops the current runtime if it is running, clears CCCC's saved session metadata for that actor, and starts the actor again with the same runtime settings.

The control is intentionally limited to Web operator use and to runtimes that already have resume support. It is not advertised through the agent-facing MCP actor surface.

Validation

The release was validated with targeted coverage for:

• OpenCode runtime detection, default commands, CLI setup reporting, and MCP runtime config injection;
• Codex OPENAI_BASE_URL to openai_base_url mapping across PTY and app-server launch paths;
• Claude/Codex New Session behavior for stopped actors, running actors, and unsupported runtimes;
• Web typecheck and build coverage for the new actor control path.

Why Upgrade

Upgrade to v0.4.21 if you want to run OpenCode as a normal CCCC actor, deploy Codex with a custom OpenAI-compatible endpoint in Docker, or need a simple Web control for starting a fresh Claude or Codex actor session without editing actor settings or deleting provider history.