CCCC v0.4.5 Release Notes

v0.4.5 consolidates more of the everyday workflow into the Web UI, simplifies remote access handling, and hardens runtime startup and shutdown behavior across Windows and POSIX environments.

Highlights

1) Web Pet replaced the old desktop pet surface

The old standalone desktop pet implementation was removed and its useful behavior was moved into the Web UI.

Key improvements:

• the pet now lives directly inside the Web interface instead of requiring a separate desktop/Tauri surface
• reminder bubbles and panel actions are more interactive, including direct jump targets such as opening chat or the relevant task
• the pet panel now shows task progress and smarter hints instead of only generic reminders
• agent tabs can surface the last terminal output after an agent stops, which makes “what just happened?” easier to answer without reopening logs

2) Web access and reachability are clearer

v0.4.5 continues the Web-access cleanup started in the previous line and makes the remote-access story more coherent in practice.

Highlights:

• the Web Access panel is better aligned with real operator goals such as local-only access, LAN/private access, and externally exposed access
• supervised Web restart/apply flows are clearer from the main cccc session
• the Web health endpoint is now publicly reachable, which makes health checks and external probing simpler
• surrounding UI wording and styling were refined so the current access posture is easier to understand at a glance

3) Runtime lifecycle behavior was hardened on Windows and POSIX

This release includes several fixes in the startup and shutdown path that materially improve day-to-day reliability.

Important changes:

• Windows Codex MCP setup is more robust and now prefers a stable absolute cccc entrypoint instead of trusting weaker path assumptions
• stale or misleading Codex MCP entries are less likely to be treated as “already installed”
• supervised Web child shutdown handling was tightened so Ctrl+C and restart flows behave more predictably
• POSIX background Python startup now preserves the active virtualenv interpreter path instead of resolving it to the system Python and silently losing the environment

4) The runtime support surface is less fragile

Beyond startup mechanics, v0.4.5 reduces a few sharp edges in the runtime control plane.

This includes:

• fail-fast MCP startup checks are scoped more carefully so they do not over-block unrelated lifecycle flows
• IM bridge child-process startup paths now follow the same safer background-process rules as the daemon/Web stack
• cross-platform process handling was refactored and validated more thoroughly in tests