v8.5.0
CCB v8.5.0
Released: 2026-07-29
English
Pi and OMP completion
- Pi
0.82.1now completes only after its finalagent_settledevent. - OMP
17.1.6now completes only afteragent_end.isTerminal=true; a
successful terminalyieldremains a valid structured result. - CCB waits for the one-shot process to exit and its output to close before
terminalizing either Provider, preventing late retry or advisor events from
being truncated. - Missing native terminal evidence, missing final outcomes, malformed or
truncated JSONL, Provider errors, and nonzero exits fail closed instead of
returning a false success. Older event shapes are not guessed.
npm runtime and Config UI
- npm postinstall now creates or repairs CCB's managed Python environment and
installs the required runtime dependencies. An incomplete system Python is
no longer treated as a usable release runtime. - Source installs now recognize linked Git worktrees whose
.gitmarker is a
file, so development checkouts are not mistaken for packaged releases. - The sidebar settings entry recovers the release-managed interpreter and
reliably launches Config UI when inherited runtime paths are stale.
Mobile activity
- Mobile ask state, Provider activity, selected-Agent views, and completion
notifications now stay synchronized with exact server-side state across
reconnects. - Expected automatic reconnect transitions no longer display misleading
snackbar errors.
Managed Provider assets
- Managed Provider assets are projected one way into private homes with
explicit ownership, avoiding writable aliases back to user-global state. - Packaged Qoder
askandccb-clearcontrols are now included in the same
managed projection contract.
Upgrade notes
- Existing project configuration requires no migration.
- npm-managed installations can run
npm install -g @seemseam/ccb@8.5.0. - Android users can install the signed CCB Mobile v8.5.0 APK from this release.
中文
Pi 与 OMP 完成检测
- Pi
0.82.1现在只在最终agent_settled事件出现后完成。 - OMP
17.1.6现在只在agent_end.isTerminal=true后完成;成功的终态
yield仍是有效的结构化结果。 - CCB 会等待一次性进程退出并关闭输出后再让两个 Provider 进入终态,避免
截断随后到达的 retry 或 advisor 事件。 - 缺少原生终止证据、缺少最终结果、JSONL 损坏或截断、Provider 错误和
非零退出都会安全拒绝,不再返回假成功;旧事件格式不会被猜测兼容。
npm 运行时与 Config UI
- npm postinstall 现在会创建或修复 CCB 的托管 Python 环境,并安装正式版
所需运行依赖;不完整的系统 Python 不再被视为可用的正式版运行时。 - 源码安装现在能识别
.git标记为文件的 linked Git worktree,不会把开发
checkout 误判成正式 release 包。 - sidebar 设置入口会恢复正式版受管解释器,在继承到失效运行路径时仍能
可靠打开 Config UI。
Mobile 活动同步
- Mobile 的 ask 状态、Provider 活动、当前 Agent 视图和完成通知会在重连
前后与服务端精确状态保持同步。 - 预期的自动重连过程不再显示误导性的 snackbar 错误。
托管 Provider 资源
- 托管 Provider 资源使用明确所有权单向投影到私有 home,不会产生指回用户
全局状态的可写别名。 - 内置 Qoder
ask与ccb-clear控制能力也纳入同一托管投影契约。
升级说明
- 现有项目配置无需迁移。
- npm 安装可执行:
npm install -g @seemseam/ccb@8.5.0。 - Android 用户可从本 Release 安装签名后的 CCB Mobile v8.5.0 APK。