CCCC v0.4.35-rc1 Release Notes

v0.4.35-rc1 is the first release candidate for CCCC 0.4.35. It focuses on managed DeepSeek headless execution, optional membership and Reach, reliable cross-platform daemon ownership, and a broad delivery and Web interaction hardening pass.

This is a prerelease. The hosted standalone installer and normal PyPI channel remain pinned to stable v0.4.34; RC users must select this version explicitly.

Highlights

Managed DeepSeek Harness runtime

DeepSeek Harness is now a first-class deepseek headless runtime. CCCC installs the exact tested ACP package composition below CCCC_HOME, keeps provider credentials as external inputs, isolates sessions per actor, and projects ACP turns into the same durable headless events used by other runtimes.

Delivery and recovery are designed around one durable outcome. Pending work can survive daemon restarts, committed turns are deduplicated, timed-out work is cancelled before retry, and failed writes do not silently advance inbox state.

Membership and Reach preview

Linux and macOS users can bind a machine to a membership account and explicitly publish its Web surface through a managed Cloudflare tunnel:

cccc login
cccc reach install
cccc reach on
cccc reach status
cccc reach off
cccc logout

Reach requires an Admin Access Token and keeps local CCCC usable without an account. Its pinned cloudflared helper lives under CCCC_HOME; CCCC does not upload the local ledger or repository. Windows process supervision is present, but the pinned Windows helper artifact is not included in this candidate, so Reach remains unavailable on Windows.

Windows daemon and updater reliability

The combined Rust launcher now treats the detached Windows daemon as an owned resource. It waits for an incompatible or legacy daemon to hand off, records the PID it actually created, stops only that owner during normal or failed Web startup, and leaves a competing replacement daemon untouched. Graceful shutdown is attempted first; an exact-PID process-tree termination is retained as the bounded fallback.

Windows standalone updates also use native process exit codes for expected stopped-state diagnostics, retain a verified replacement when only restart fails, and wait for executable and daemon-lock release before reporting success.

Runtime, delivery, and Web hardening

• Runtime restoration is serialized with actor and Group lifecycle mutations.
• Headless delivery completion advances only over a contiguous committed prefix.
• Legacy large event histories migrate through bounded indexes.
• Windows project selection can browse available drive roots.
• Task Board and virtual chat scrolling use focused components and stale-request guards, improving send-follow and history-anchor stability.

Install the release candidate

Python compatibility and native wheels are published to TestPyPI:

python -m pip install -U --pre \
  --index-url https://test.pypi.org/simple/ \
  --extra-index-url https://pypi.org/simple/ \
  'cccc-pair==0.4.35rc1'

The standalone Rust candidate is selected explicitly from GitHub Releases:

curl -fsSL https://chesterra.github.io/cccc/install.sh | \
  CCCC_VERSION=0.4.35-rc1 sh

$env:CCCC_VERSION = "0.4.35-rc1"
powershell.exe -NoProfile -ExecutionPolicy Bypass -Command "[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12; Invoke-RestMethod 'https://chesterra.github.io/cccc/install.ps1' | Invoke-Expression"
Remove-Item Env:CCCC_VERSION

Verify the installed identity and lifecycle:

cccc --version
cccc status
cccc daemon status
cccc daemon stop

Compatibility and known limits

• Python 3.11 through 3.14 remain supported.
• Linux x86-64, Intel macOS, Apple Silicon macOS, and Windows x86-64 receive native candidates; the portable wheel remains Python-only.
• Existing CCCC_HOME Groups, ledgers, settings, and runtime state remain shared between Python and Rust. Back up operational data before prerelease testing.
• Reach is a Linux/macOS preview and is unavailable on Windows in this candidate.
• DeepSeek requires a valid provider credential and uses an upstream developer preview package set; live-provider behavior cannot be proven by offline CI.
• The standalone Rust distribution has no Python fallback or implementation switching. Use the pip distribution when that fallback is required.

Any code or artifact correction after this candidate will be published as v0.4.35-rc2; the v0.4.35-rc1 tag and artifacts will not be replaced.