CCB v8.5.1

Released: 2026-07-30

English

Claude now aggregates snapshots of the same assistant message and waits for
its visible final text. A thinking-only end_turn can no longer complete
with earlier process narration such as Let me....
Terminal artifacts use only the confirmed final assistant message rather
than a buffer accumulated across tool rounds.
Missing completion hooks can be recovered only from evidence matching the
exact request, Agent, workspace, timestamp, and Claude session.
API Error: Response stalled mid-stream is reported as failed/incomplete
provider output instead of a successful completion.

New Pi asks run in the existing managed Pi pane, so prompts, tool activity,
and replies remain visible in the TUI.
CCB loads a runtime-owned Pi extension and accepts only the final
agent_settled message bound to the exact dispatch id, prompt digest, Agent,
launch session, runtime instance, and request id.
Process narration, tool rounds, retries, stale sessions, manual input, and
partial or malformed event logs cannot be returned as a successful reply.
Pi pane runs no longer have a fixed terminal timeout by default. Native
cancellation also avoids the model-facing cancel-file probe and its extra
tool call/token cost.
Persisted 8.5.0 Pi jobs remain compatible. Operators can temporarily select
the previous one-shot path with CCB_PI_EXECUTION_MODE=headless.

Local Mobile gateway health checks bypass HTTP_PROXY, HTTPS_PROXY, and
ALL_PROXY, preventing configured proxies from making a healthy loopback
gateway appear unavailable.

No configuration migration is required.
Restart already-running CCB projects after upgrading so managed Claude and Pi
runtimes load the new completion behavior.
npm-managed installations can run
npm install -g @seemseam/ccb@8.5.1.
Android users can install the signed CCB Mobile v8.5.1 APK from this release.

Claude 现在会聚合同一 assistant message 的多个快照，并等待可见的最终
文本。只有 thinking 的 end_turn 不会再用之前的 Let me... 等过程说明
提前完成。
终态 artifact 只使用已确认的最终 assistant message，不再采用跨工具轮次
累积的过程文本。
completion hook 缺失时，只有同时匹配当前请求、Agent、workspace、时间戳
和 Claude session 的证据才允许参与恢复。
API Error: Response stalled mid-stream 会作为失败或不完整的 Provider
输出处理，不再被误判为成功完成。

新的 Pi ask 会在现有托管 Pi pane 中执行，prompt、工具活动和回复都能在
TUI 中直接看到。
CCB 会加载运行时自有的 Pi extension，并且只接受与 dispatch id、prompt
摘要、Agent、启动 session、运行实例和 request id 精确绑定的最终
agent_settled 消息。
过程说明、工具轮次、重试、旧 session、人工输入以及部分写入或损坏的
event log 都不能成为成功回复。
Pi pane 默认不再使用固定终态超时。原生取消也不再要求模型检查 cancel
文件，从而避免额外的工具调用和 token 消耗。
8.5.0 已持久化的 Pi job 保持兼容；运维人员也可以临时设置
CCB_PI_EXECUTION_MODE=headless 使用之前的一次性执行路径。

本地 Mobile gateway 健康检查会绕过 HTTP_PROXY、HTTPS_PROXY 和
ALL_PROXY，避免代理配置把正常的 loopback gateway 误判为不可用。