Skip to content

C2C 2.4.0 — Explicit effort and clearer revision checks

Choose a tag to compare

@ZiadHassanein ZiadHassanein released this 09 Oct 11:35

C2C 2.4.0 gives planners clearer effort settings and reviewers a focused view of plan changes while keeping the complete evidence available.

  • Select and record compatible worker effort explicitly. Requested effort stays separate from effective effort, which remains unknown when the provider does not report it.
  • Include bounded revision diffs alongside the full current plan, findings, decisions and security review. Oversized diffs fall back safely without dropping authoritative context.
  • Apply consistent outcome, dependency, acceptance and severity guidance to software, content and mixed projects.
  • Reduce unnecessary status polling where the host supports longer waits, and preserve reviewed plans when adding navigation or later amendments.
  • Register the frozen 2.3.0 evaluation baseline without inventing measured outcomes or token-saving percentages.

The three-file handoff, usage limits, existing runtime pins and managed update/rollback behavior remain supported. Start a new chat after updating to use the new instructions for a new plan.

Validated with 525 passing local tests and nine platform skips, documentation checks, independent source review and fictional instruction walkthroughs. All 15 native CI jobs passed on the exact release candidate across Linux, macOS and Windows with Node 18, 22 and 24 (CI results). These checks are not a live provider trial or a measured planning-quality/token-savings comparison.