CCCC v0.4.3 Release Notes

v0.4.3 is a major refinement release over v0.4.2. It tightens the core collaboration model, reduces prompt and control-plane drift, hardens Windows and runtime integration, and makes long-running group operation more predictable across Web, MCP, IM, and Group Space workflows.

Highlights

1) Prompt, help, and role guidance were re-layered

The guidance stack was simplified so stable startup rules, live runtime guidance, and actor-specific notes no longer compete with each other.

Key changes:

the startup prompt is slimmer and more focused on durable operating rules
live runtime guidance now belongs to cccc_help, so optional capability-specific instructions appear only when actually relevant
actor role notes are now canonically stored in the group help document @actor blocks instead of leaking into working-state fields
agent working stance and role guidance are now more clearly separated, which reduces confusion between long-term role intent and current execution context

2) Context and task authority semantics were hardened

Several core collaboration boundaries were tightened so the system behaves more predictably under real multi-actor usage.

This includes:

task.restore now follows a clear archived-only precondition and matches the same authority model as the other task-mutating operations
peers can no longer mutate arbitrary unassigned tasks; task control is limited to the actor actually responsible for the work
actor-owned agent_state semantics are now aligned across docs, daemon behavior, MCP tooling, and Web expectations
system-driven task-to-working-state synchronization remains in place where it materially reduces manual upkeep cost

3) Group Space and memory workflows became more coherent

v0.4.3 significantly improves the operational behavior of notebook-backed workflows.

Key improvements:

work-lane and memory-lane status now track the current binding more accurately instead of leaking stale sync residue after unbind/rebind cycles
NotebookLM-related runtime guidance is injected only when the relevant capability is actually active
the login, bind, use, unbind, and disconnect flow is cleaner from both the daemon and Web state-model perspective
memory and daily-memory coordination stays intentionally connected, but the surrounding guidance and runtime status are now clearer

4) Runtime support and Windows robustness were strengthened

This release continues the push toward a more disciplined and supportable runtime surface.

Highlights:

Windows MCP reliability was hardened, including runtime-context resolution and stdio/encoding robustness
the officially supported runtime surface was narrowed and clarified to the runtimes CCCC can set up and operate reliably
standalone Web startup now follows the same local-first binding model as the main CLI entrypoint
release verification was tightened to better match the project's claimed Linux, macOS, and Windows support surface

5) Operator-facing surfaces saw broad stabilization

A large amount of polish landed across the everyday control surfaces used by operators and agent teams.

Notable areas:

user-scoped actor profiles now work end to end across daemon, Web, and MCP paths
IM integration continued to improve, especially around DingTalk sender identity, revoke behavior, @ targeting, and streaming fallback behavior
blueprint export/import portability was fixed so round-trips keep the intended portable fields
Web settings, modal behavior, overflow handling, context presentation, and translation coverage were substantially cleaned up
global browser surfaces were trimmed so scoped users see less irrelevant machine-global data by default

Validation Summary

The 0.4.3 line was stabilized through multiple release candidates and targeted regression work across the highest-risk areas, including:

context and task authority rules
role-notes source-of-truth handling
Group Space bind/unbind status correctness
Windows MCP stability
scoped actor profiles and permission boundaries
IM bridge revoke and delivery behavior
blueprint round-trip portability

Upgrade Notes

From v0.4.2, this is still a drop-in minor upgrade for most deployments. No explicit data migration step is required.

CCCC v0.4.3 Release Notes ​

Highlights ​

1) Prompt, help, and role guidance were re-layered ​

2) Context and task authority semantics were hardened ​

3) Group Space and memory workflows became more coherent ​

4) Runtime support and Windows robustness were strengthened ​

5) Operator-facing surfaces saw broad stabilization ​

Validation Summary ​

Upgrade Notes ​