v8.6.3

Released: 2026-08-13

English

Highlights

• CCB Mobile now recognizes ordinary files linked from the current Agent's
  .ccb/workspaces/<agent>/... tree and presents them as authenticated download
  attachments. Generated reports such as PDF files can therefore be opened
  directly from the conversation instead of showing the raw-source warning.

Security and upgrade notes

• This is a narrow workspace-artifact exception, not general .ccb access.
  Links into another Agent's workspace, any hidden workspace path, or any other
  private .ccb runtime area remain unavailable.
• Downloads still require the Mobile file_download scope and retain the
  gateway's existing regular-file and size checks.
• No project configuration, pairing, or stored-state migration is required.
  Update the CCB host to activate the gateway fix; the existing Mobile client
  already understands authenticated artifact links.

npm install -g @seemseam/ccb@8.6.3

Existing release-package installations can use ccb update. Android users can
install ccb-mobile-v8.6.3.apk from this Release.

Known limitations

• Hidden files and directories below the Agent workspace are intentionally not
  downloadable, even when an Agent links them.
• Android is the validated Mobile release target. iOS/iPadOS remain
  source-supported. Native Windows x64 remains beta and ships unsigned
  launchers.

中文

版本亮点

• CCB Mobile 现在会识别当前 Agent 在
  .ccb/workspaces/<agent>/... 中引用的普通文件，并将其呈现为经过认证的下载
  附件。因此 PDF 等生成报告可直接从对话打开，不再显示 raw-source 提示。

安全与升级说明

• 这是范围严格受限的 workspace 产物例外，并非开放整个 .ccb。指向其他 Agent
  workspace、任意 workspace 隐藏路径或 .ccb 内其他私有运行时区域的链接仍不可用。
• 下载仍要求 Mobile file_download scope，并继续执行 gateway 既有的普通文件和
  大小限制校验。
• 无需迁移项目配置、配对或存储状态。更新 CCB 主机即可启用 gateway 修复；现有
  Mobile 客户端已经支持经过认证的 artifact 链接。

npm install -g @seemseam/ccb@8.6.3

通过 Release 包安装的用户可运行 ccb update。Android 用户可从本 Release 安装
ccb-mobile-v8.6.3.apk。

已知限制

• 即使 Agent 主动引用，Agent workspace 下的隐藏文件和目录也刻意保持不可下载。
• Android 是经过验证的 Mobile 发布目标；iOS/iPadOS 仍为源码支持。原生 Windows
  x64 仍处于 beta，且启动器尚未签名。

v8.6.2

Released: 2026-08-13

English

Highlights

• CCB now requires an external, exact-value approval before a project-local
  .ccb/ccb.config can execute a tool-window command or a custom Provider
  command template. Interactive startup can request the approval, and
  ccb config approve-commands provides an explicit non-startup workflow.
  This closes Issue #299 without treating project content as trusted code.
• Managed Codex recovery preserves conversation continuity when the current
  session record is corrupt. CCB identifies the latest valid recoverable
  session instead of silently clearing context or binding to malformed state.
• Cursor jobs can run through the visible Provider Pane with transcript anchors,
  stable-idle checks, busy deferral, and post-dispatch terminal evidence.
• CCB Mobile adds multi-session host terminals and negotiates Provider-control
  capabilities through Relay. Older hosts receive update guidance rather than
  controls that the host cannot safely honor.

Fixes and reliability

• Mobile exposes Pi native session history and hardens native Windows project
  registration, readiness waits, endpoint markers, and TCP descriptor
  validation.
• Native Windows process liveness and command-line inspection are more robust;
  ccb kill tears down the persisted Herdr namespace, and background launcher
  paths avoid unwanted console windows and venv redirection failures.
• OMP managed homes inherit the intended Provider configuration while retaining
  CCB's managed-home isolation boundaries.
• The release incorporates the Herdr teardown, Windows process, Mobile Windows
  registry, and Pi history contributions from PRs #298, #302, #301, and #300.

Security and upgrade notes

npm install -g @seemseam/ccb@8.6.2

Existing release-package installations can use ccb update. Android users can
install ccb-mobile-v8.6.2.apk from this Release.

Projects that do not configure tool_windows.<name>.command or
agents.<name>.provider_command_template require no migration. Projects that
intentionally configure either field must approve its exact current value once,
through the interactive prompt or ccb config approve-commands. Changing an
approved value requires a new approval. Script mode does not bypass this gate.

Known limitations

• Command approvals are intentionally exact and stored outside project-owned
  configuration. Moving a project, changing a protected command, or losing the
  external receipt requires approval again.
• Relay Provider controls require a host that advertises the corresponding
  capability. Older hosts continue to connect, but controls remain unavailable
  until the host is updated.
• Visible-pane Cursor completion depends on observable Pane and transcript
  evidence; ambiguous or actively working states defer or fail closed.
• Android is the validated Mobile release target. iOS/iPadOS remain
  source-supported. Native Windows x64 remains beta, requires the documented
  external prerequisites, and ships unsigned launchers.

中文

版本亮点

• CCB 现在要求项目本地 .ccb/ccb.config 中的 tool-window 命令或自定义
  Provider command template 在执行前取得项目外部、精确值匹配的批准。交互式启动
  可请求批准，也可通过 ccb config approve-commands 明确完成非启动流程。
  该安全边界修复了 Issue #299，不再把项目内容默认视为可信代码。
• 托管 Codex 当前 session 记录损坏时，CCB 会选择最近的有效可恢复 session，
  保持对话连续性，不再静默清空上下文或绑定到格式错误的状态。
• Cursor 任务可通过可见 Provider Pane 执行，并使用 transcript anchor、稳定空闲
  检查、busy 延迟和派发后的终态证据判断任务生命周期。
• CCB Mobile 新增主机多 session 终端，并通过 Relay 协商 Provider 控制能力；旧版
  主机会收到升级指引，不会显示其无法安全执行的控制项。

修复与稳定性

• Mobile 增加 Pi 原生 session 历史，并加固原生 Windows 下的项目注册、readiness
  等待、endpoint marker 和 TCP descriptor 校验。
• 原生 Windows 的进程存活与命令行检查更加可靠；ccb kill 会销毁持久化 Herdr
  namespace，后台 launcher 路径也避免弹出多余控制台窗口和 venv 重定向失败。
• OMP 托管 home 会继承预期的 Provider 配置，同时保持 CCB 的托管 home 隔离边界。
• 本版本合入 Herdr 清理、Windows 进程、Mobile Windows registry 与 Pi 历史相关的
  PR #298、#302、#301 和 #300。

安全与升级说明

npm install -g @seemseam/ccb@8.6.2

通过 Release 包安装的用户可运行 ccb update。Android 用户可从本 Release 安装
ccb-mobile-v8.6.2.apk。

未配置 tool_windows.<name>.command 或
agents.<name>.provider_command_template 的项目无需迁移。有意配置任一字段的
项目，需要通过交互式提示或 ccb config approve-commands 对当前精确值批准一次；
批准后的值发生变化时必须重新批准。脚本模式不会绕过此安全门禁。

已知限制

• 命令批准刻意采用精确匹配，且 receipt 存储在项目配置之外。移动项目、修改受
  保护命令或丢失外部 receipt 后，需要重新批准。
• Relay Provider 控制要求主机声明相应 capability。旧版主机仍可连接，但升级主机
  前这些控制项保持不可用。
• Cursor 可见 Pane 的完成判断依赖可观察的 Pane 与 transcript 证据；状态含糊或
  正在工作时会延迟派发或保持 fail-closed。
• Android 是经过验证的 Mobile 发布目标；iOS/iPadOS 仍为源码支持。原生 Windows
  x64 仍处于 beta，需要文档列出的外部依赖，且启动器尚未签名。

v8.6.1

Released: 2026-08-12

English

Highlights

• CCB Mobile now shows the selected Agent's Provider, active/configured/pending
  model and thinking state, native Codex/Claude session usage, and optional
  account quota. Supported model and thinking changes are validated on the
  host and saved as an explicit restart-required configuration change.
• The Mobile home screen can open a terminal directly for a project window or
  Agent. Terminal shortcuts can be enabled, disabled, reordered, and restored
  to defaults from the App settings.
• Managed Agents receive the built-in ccb-compact Skill. ccb compact
  checks authoritative outstanding work before sending a verified
  Provider-native compaction command and reports unsupported Providers without
  injecting ordinary prompt text.
• Config UI now loads the complete available Role catalog instead of a
  hard-coded subset, including roles such as agentroles.mother when present
  in the configured catalog source.

Fixes and reliability

• Provider-setting mutations are fenced by device scope, project namespace,
  Provider identity, runtime/config revisions, target-bound idempotency, and
  server-side model capability validation. Credentials and raw Provider
  responses remain host-only.
• Mobile conversation history now retains explicit native-session boundaries.
  Wide terminal snapshots are clipped to the negotiated pane width, and a
  combined text-plus-key input frame is delivered to the Pane in the original
  order instead of being rejected as an unsupported control sequence.
• Cross-platform runtime tests and installer checks were stabilized, and the
  WeChat community QR image and README cache key were refreshed.

Upgrade notes

npm install -g @seemseam/ccb@8.6.1

Existing release-package installations can use ccb update. Android users can
install ccb-mobile-v8.6.1.apk from this Release. No configuration or
conversation migration is required.

Known limitations

• Codex and Claude model/thinking changes require the affected managed Agent to
  restart; this release does not advertise live Provider switching.
• Account quota is available only when CCB has an authoritative managed Codex
  or Claude credential. Missing quota remains explicitly unavailable.
• ccb compact fails closed for Providers without a verified native command;
  a successful result confirms command dispatch, while the Provider performs
  compaction asynchronously in its pane.
• Android is the validated Mobile release target. iOS/iPadOS remain
  source-supported. Native Windows x64 support remains beta, requires the
  documented external prerequisites, and ships unsigned launchers.

中文

版本亮点

• CCB Mobile 现在会显示所选 Agent 的 Provider、当前/已配置/待生效的模型与
  thinking 状态、Codex/Claude 原生 session 用量，以及可选的账号额度。受支持的
  模型和 thinking 修改会在主机端校验，并明确保存为“需要重启后生效”的配置变更。
• Mobile 首页现在可以直接打开某个项目 window 或 Agent 的终端；终端快捷键可在
  App 设置中启用、关闭、排序并恢复默认值。
• 托管 Agent 新增内置 ccb-compact Skill。ccb compact 会先检查权威的未完成
  工作，再发送经过确认的 Provider 原生压缩命令；对于未验证的 Provider 会返回
  unsupported，不会把普通提示词误发进 Pane。
• Config UI 不再使用写死的少量 Role，而是加载当前可用的完整 Role catalog；当
  配置的角色源中存在 agentroles.mother 等角色时，也会一并显示。

修复与稳定性

• Provider 设置修改同时受设备 scope、项目 namespace、Provider 身份、runtime/
  config revision、与目标绑定的幂等指纹和服务端模型能力校验保护。凭据和原始
  Provider 响应仍只保留在主机端。
• Mobile 对话历史现在会保留明确的原生 session 边界；宽终端快照会先按协商后的
  Pane 宽度裁剪；同一输入 frame 内的“文本 + 按键”会按原顺序发送到 Pane，不再被
  误判为不支持的控制序列。
• 稳定了跨平台 runtime 测试和安装器检查，并刷新微信群二维码与 README 缓存键。

升级说明

npm install -g @seemseam/ccb@8.6.1

通过 GitHub Release 包安装的用户可运行 ccb update。Android 用户可从本 Release
安装 ccb-mobile-v8.6.1.apk。无需迁移配置或对话历史。

已知限制

• Codex 和 Claude 的模型/thinking 修改需要重启受影响的托管 Agent；本版本不宣称
  支持实时切换 Provider。
• 只有 CCB 持有权威的托管 Codex 或 Claude 凭据时，账号额度才可用；缺失额度会
  明确显示为 unavailable，不会估算。
• 对于没有经过验证的原生命令的 Provider，ccb compact 会保持 fail-closed；
  成功结果表示命令已发送，实际压缩仍由 Provider 在 Pane 中异步完成。
• Android 是本次经过验证的 Mobile 发布目标；iOS/iPadOS 仍为源码支持。原生
  Windows x64 仍处于 beta，需要文档列出的外部依赖，且启动器尚未签名。

v8.6.0 — Native Windows distribution and Pi session recovery

Released: 2026-08-12

English

Highlights

CCB 8.6.0 publishes the normal stable Linux, macOS, npm, Sidebar, and Android
artifacts and adds a native Windows x64 ZIP to the same GitHub Release. The CCB
version is stable; the Windows support tier remains beta while real
WezTerm/Herdr and provider qualification continues.

• Native Windows PE launchers are included for ccb, ask, autonew, and
  ctx-transfer.
• install.ps1 verifies the Windows archive checksum and creates an
  install-local managed Python environment.
• Windows runtime and release code stays isolated under
  lib/platforms/windows/ and platforms/windows/; Unix installers and npm
  package metadata remain platform-specific and unchanged.
• Pi now restores the exact validated native JSONL session after a CCB restart.
  Fresh context and explicit Pi session controls retain their existing
  behavior.
• Project-scoped tmux sockets are rebound after backend-cache reuse, repairing
  the Linux, macOS, and WSL lifecycle regression introduced during the Windows
  integration.
• Terminal backend exports now initialize lazily, preventing the Windows Herdr
  integration from creating a circular import when mobile or ccbd services load.
• Non-interactive Windows installation now honors -Yes and
  CCB_INSTALL_ASSUME_YES=1 when Herdr is absent, while preserving the warning
  that normal CCB startup still requires Herdr.

Upgrade

npm install -g @seemseam/ccb@8.6.0

Existing release-package installations can use ccb update. No configuration
or conversation migration is required.

For Windows testing, download ccb-windows-x86_64.zip and its .sha256
sidecar from this Release, verify the digest, extract the archive, and run:

.\install.ps1 install -Yes
ccb --print-version

Windows beta boundary

• Requires native Windows x64, Python 3.10+, WezTerm, Git Bash, and Herdr
  0.8.0 or newer.
• The ZIP is not fully self-contained and the PE launchers are unsigned.
• ccb update is diagnostic-only on the Windows beta path.
• Native Windows build, archive install, launcher smoke, and checksum gates
  passed on Windows Server 2022. Full real GUI and provider workflow
  qualification is still pending, so this release does not claim stable
  Windows support.

中文

主要更新

CCB 8.6.0 会正常发布稳定版 Linux、macOS、npm、Sidebar 与 Android 产物，
并在同一个 GitHub Release 中新增原生 Windows x64 ZIP。CCB 版本是正式稳定版；
在真实 WezTerm/Herdr 与 Provider 验收完成前，Windows 支持等级仍保持 beta。

• 新增 ccb、ask、autonew、ctx-transfer 的 Windows 原生 PE 启动器。
• install.ps1 会校验 Windows 压缩包哈希，并创建安装目录内的托管 Python 环境。
• Windows 运行时代码和发布代码分别隔离在 lib/platforms/windows/ 与
  platforms/windows/；Unix 安装器和 npm 包平台声明不混入 Windows 实现。
• CCB 重启后，Pi 现在会恢复经过校验的准确原生 JSONL 会话；新上下文和显式
  Pi 会话参数仍保持原有语义。
• 后端缓存复用后会重新绑定项目专属 tmux socket，修复 Windows 集成期间引入的
  Linux、macOS 与 WSL 生命周期回归。
• Terminal backend 导出改为按需初始化，避免 mobile 或 ccbd 服务加载时被
  Windows Herdr 集成触发循环导入。
• Windows 非交互安装在缺少 Herdr 时会正确识别 -Yes 与
  CCB_INSTALL_ASSUME_YES=1，同时继续明确提示：正常启动 CCB 仍然需要 Herdr。

升级

npm install -g @seemseam/ccb@8.6.0

通过 GitHub release 包安装的用户可运行 ccb update。本次升级不需要迁移配置或
对话历史。

Windows 测试用户请从本 Release 下载 ccb-windows-x86_64.zip 和对应的
.sha256 文件，校验哈希并解压，然后运行：

.\install.ps1 install -Yes
ccb --print-version

Windows beta 边界

• 需要原生 Windows x64、Python 3.10+、WezTerm、Git Bash 与 Herdr 0.8.0
  或更高版本。
• ZIP 并非完全自包含，PE 启动器也尚未签名。
• Windows beta 路径中的 ccb update 目前只提供诊断。
• Windows Server 2022 上的原生构建、压缩包安装、启动器 smoke 与哈希校验已通过；
  真实 GUI 和 Provider 工作流仍待完整验收，因此本版本不宣称 Windows 已达到
  稳定支持等级。

v8.6.0-beta.3 — Native Windows x64 beta

Released: 2026-08-11

English

What changed since beta.2

Beta.2 passed its native Python and Rust tests and successfully built the PE
launchers and Windows ZIP. Installation then stopped because the missing-Herdr
confirmation attempted to read interactive input even though the workflow had
supplied -Yes and CCB_INSTALL_ASSUME_YES=1.

Beta.3 makes those explicit non-interactive acknowledgements bypass the prompt
while retaining the warning that normal CCB startup requires Herdr. The release
workflow only exercises the safe --print-version and --help surfaces when
Herdr is absent. The interactive prompt is also hardened against null input.

No GitHub Release was created for beta.1 or beta.2, and neither tag was moved.

Included

• ccb-windows-x86_64.zip and its .sha256 sidecar.
• Native PE launchers for ccb, ask, autonew, and ctx-transfer.
• A checksum-validating PowerShell archive installer with an install-local
  Python environment.
• Windows-owned runtime and release code under lib/platforms/windows/ and
  platforms/windows/.

Install for testing

Get-FileHash .\ccb-windows-x86_64.zip -Algorithm SHA256
Get-Content .\ccb-windows-x86_64.zip.sha256
Expand-Archive .\ccb-windows-x86_64.zip -DestinationPath .\ccb-windows-beta
cd .\ccb-windows-beta\ccb-windows-x86_64
.\install.ps1 install -Yes
ccb --print-version

Prerequisites and limits

• Native Windows x64, Python 3.10+, WezTerm, Git Bash, and Herdr 0.8.0+.
• -Yes permits installation without Herdr but does not make normal CCB
  startup usable without Herdr.
• The ZIP is not fully self-contained, and the binaries are unsigned.
• This prerelease does not publish or replace npm, Linux, macOS, Sidebar, or
  Android artifacts.

中文

相比 beta.2 的修复

beta.2 已通过原生 Python 与 Rust 测试，也成功生成 PE 启动器和 Windows ZIP；但在
安装阶段，即使工作流已经传入 -Yes 与 CCB_INSTALL_ASSUME_YES=1，缺少 Herdr
时仍尝试读取交互输入，导致安装中止。

beta.3 会把上述参数视为对“继续安装”风险的明确确认，因此不再弹出交互提示；同时
仍会提示正常启动 CCB 必须安装 Herdr。发布工作流在缺少 Herdr 时只测试安全的
--print-version 与 --help。交互提示本身也增加了空输入保护。

beta.1 与 beta.2 都没有创建 GitHub Release，且旧标签均未移动。

包含内容

• ccb-windows-x86_64.zip 与对应的 .sha256 文件。
• ccb、ask、autonew、ctx-transfer 的原生 PE 启动器。
• 校验压缩包哈希、并创建安装目录内 Python 环境的 PowerShell 安装器。
• 位于 lib/platforms/windows/ 与 platforms/windows/ 的 Windows 专属代码。

测试安装

Get-FileHash .\ccb-windows-x86_64.zip -Algorithm SHA256
Get-Content .\ccb-windows-x86_64.zip.sha256
Expand-Archive .\ccb-windows-x86_64.zip -DestinationPath .\ccb-windows-beta
cd .\ccb-windows-beta\ccb-windows-x86_64
.\install.ps1 install -Yes
ccb --print-version

前置条件与限制

• 原生 Windows x64、Python 3.10+、WezTerm、Git Bash 与 Herdr 0.8.0+。
• -Yes 只允许在缺少 Herdr 时完成安装，不代表正常 CCB 启动可以脱离 Herdr。
• ZIP 并非完全自包含，二进制也尚未签名。
• 本预发布不会发布或替换 npm、Linux、macOS、Sidebar 或 Android 产物。

v8.5.7

Released: 2026-08-08

English

Highlights

• CCB now guarantees the built-in ccb-clear and ccb-diagnose Skills for
  every supported managed Agent, even when optional Skill inheritance is
  disabled. Run $ccb_diagnose <agentname> to diagnose exactly one mounted
  Agent without clearing its conversation or restarting the whole project.
• ccb-diagnose combines daemon/runtime authority, active job lineage, queue,
  inbox, trace, Provider logs, and mandatory bounded Pane inspection. It
  distinguishes healthy progress, waiting input, stale prompts, Provider
  errors, dead or blank panes, and layout failures before selecting a repair.
• Recovery remains bounded to supported CCB control-plane actions and is
  verified against runtime, lineage, queue, and Pane evidence. The Skill can
  prepare a redacted incident draft, but it must show the exact draft and
  obtain fresh user authorization before creating a GitHub issue.

Fixes and reliability

• PR #288 adds self-healing for expired mailbox deliveries without replaying
  business work, forwards Provider no-terminal timeout settings into ccbd,
  and projects Kiro settings through its isolated KIRO_HOME without copying
  Agent sessions. Its stale pre-activation Claude assistant bookkeeping is
  removed so old busy-turn records cannot contaminate a newly queued request.
• The sidebar now shows communication short ids, queue depth, and the active
  job suffix so stalled or backed-up Agents are easier to identify.
• codex-reconnect now resolves its primary readiness probe from the active
  Codex Provider configuration or inherited route. Custom Provider network and
  selected-model capacity failures therefore use the same exact-pane,
  exact-thread, two-probe recovery gates as the default route.

Upgrade notes

• No configuration or conversation migration is required. Install with
  npm install -g @seemseam/ccb@8.5.7, restart CCB, and invoke
  $ccb_diagnose <agentname> from a supported managed Agent when diagnosis is
  needed.
• ccb-diagnose is an inherited Agent Skill rather than a standalone shell
  command. Continue to use ccb clear <agentname> for explicit context clears.

Known limitations

• Diagnosis does not automatically duplicate or resubmit business work, mutate
  tmux panes directly, restart every Agent, or submit issue content without
  approval. Repairs that could repeat external effects remain blocked pending
  separate user confirmation.
• Deterministic projection and recovery-path tests can validate the Skill
  contract, but this release does not manufacture real Provider outages,
  capacity exhaustion, login prompts, or every possible terminal layout.

Validation

• All seven packaged ccb-diagnose copies passed Skill validation and have an
  identical workflow digest. The focused Provider projection, installer,
  storage, runtime, mailbox, reconnect, and PR #288 suite passed 510 tests and
  4 subtests before the Claude activation-fence regression was corrected; the
  complete Claude queued-prompt file then passed 12 tests.
• The final full source run passed 6203 tests and 4 subtests with 2 expected
  skips. Its remaining 4 Agent Roles smoke scenarios could not rediscover the
  external catalog after repeated isolated-home downloads; all 4 passed in a
  clean rerun pinned to the already downloaded local catalog. The 4 runtime
  accelerator lifecycle tests also passed with an existing local build.
• bash -n install.sh, the bilingual release-note validator, and repository
  whitespace checks passed. Local cargo and PowerShell were unavailable;
  Linux/macOS Rust builds, Windows static coverage, signed Android assembly,
  release assets, and npm publication remain gated by the tag workflows.

中文

版本亮点

• 即使关闭可选 Skill 继承，CCB 也会为所有受支持的托管 Agent 保证内置
  ccb-clear 和 ccb-diagnose。运行 $ccb_diagnose <agentname> 可诊断一个
  已挂载 Agent，无需清除其对话，也不会重启整个项目。
• ccb-diagnose 会联合 daemon/runtime 权威状态、当前 job lineage、队列、inbox、
  trace、Provider 日志和强制的有界 Pane 检查，在选择修复动作前区分正常推进、等待
  输入、提示符停滞、Provider 错误、Pane 死亡或空白以及布局异常。
• 恢复动作只使用 CCB 支持的有界控制面操作，并根据 runtime、lineage、队列和 Pane
  证据复验。Skill 可以生成脱敏 incident 草稿，但创建 GitHub issue 前必须展示完整
  草稿，并重新取得用户明确授权。

修复与稳定性

• PR #288 增加过期 mailbox 投递的自恢复，不会重放业务任务；Provider 无终态超时
  配置现在可传入 ccbd；Kiro 通过隔离的 KIRO_HOME 继承设置，同时不会复制
  Agent session。该 PR 中过时的 Claude 激活前 assistant 记账逻辑已移除，旧 busy
  turn 记录不会污染新排队请求。
• Sidebar 现在显示通信短 id、队列深度和当前 job 后缀，更容易定位停滞或积压的
  Agent。
• codex-reconnect 会从当前 Codex Provider 配置或继承路由解析主要就绪探测地址。
  因此自定义 Provider 的网络故障或选定模型容量错误，也会使用与默认路由相同的
  精确 Pane、精确 thread 和双探测恢复门控。

升级说明

• 无需迁移配置或对话。使用 npm install -g @seemseam/ccb@8.5.7 安装并重启
  CCB；需要诊断时，在受支持的托管 Agent 中运行
  $ccb_diagnose <agentname>。
• ccb-diagnose 是继承到 Agent 内的 Skill，不是独立 shell 命令。需要明确清除
  上下文时，继续使用 ccb clear <agentname>。

已知限制

• 诊断不会自动复制或重新提交业务任务，不会直接修改 tmux Pane，不会重启全部
  Agent，也不会未经授权提交 issue 内容。可能重复外部副作用的修复仍会被阻止，
  直到用户另行确认。
• 确定性的 projection 与恢复路径测试可以验证 Skill 契约，但本版不会人为制造真实
  Provider 中断、容量耗尽、登录提示或所有可能的终端布局。

验证说明

• 7 份打包的 ccb-diagnose 均通过 Skill 校验，并具有相同的 workflow digest。
  Provider projection、安装器、storage、runtime、mailbox、reconnect 与 PR #288
  重点套件在修复 Claude 激活隔离回归前通过 510 个测试和 4 个 subtest；随后完整
  Claude 排队 prompt 文件的 12 个测试全部通过。
• 最终完整源码运行通过 6203 个测试和 4 个 subtest，另有 2 个预期 skip。剩余
  4 个 Agent Roles smoke 场景在多次独立 HOME 下载后无法重新发现外部 catalog；
  固定到已下载的本地 catalog 后，4 项隔离重跑全部通过。4 个 runtime accelerator
  生命周期测试也使用已有本地构建全部通过。
• bash -n install.sh、双语 Release Notes 校验和仓库空白检查均通过。本机没有
  cargo 和 PowerShell；Linux/macOS Rust 构建、Windows 静态覆盖、签名 Android
  构建、Release 资产与 npm 发布仍由 tag 工作流门控。

v8.5.6

Released: 2026-08-06

English

Highlights

• CCB now resolves Provider authority per dimension. An API key, token, URL,
  route, account selection, or Provider profile explicitly present in
  .ccb/ccb.config wins for that dimension; dimensions without explicit CCB
  authority inherit the current external Provider environment or login state.
• A stopped Provider generation is rebuilt from a fresh external snapshot and
  private managed projection. The flow is one-way: managed refresh, logout,
  cleanup, and restart do not write to the user's shell, Provider home, IDE,
  OS keyring, or remote login.
• CCB keeps one stable conversation identity across authority generations.
  Same-authority launches use native resume. Codex, Claude, and Gemini use
  native fork/import only when the installed CLI capability and private-path
  checks prove it safe; otherwise the new generation is recorded as a linked
  continuation and the old transcript remains discoverable.

Fixes and reliability

• The withdrawn v8.5.5 *-global/legacy-route migration shape can be restored
  only when the old session id and path prove ownership. Legacy sessions with
  missing authority metadata are adopted in place instead of being treated as
  an automatic clear. Workspaces, queues, session records, and history are
  retained across authority changes.
• CCB now bundles and automatically arms codex-reconnect for managed Codex
  panes after a concrete thread binding. Exact-thread network and selected-model
  capacity failures pass the existing pane, cursor, and two-probe gates before
  one literal continue is submitted. Standalone Codex remains opt-in through
  $reconnect on.
• The Relay invitation default remains 1 GiB per 24-hour window, and the
  community QR asset/cache key is refreshed.

Upgrade notes

• v8.5.5 was withdrawn from GitHub on 2026-08-05. Do not install it for managed
  sessions; use v8.5.6 or v8.5.4 instead.
• No configuration or data migration is required. Do not run ccb clear to
  apply an account or API change. After changing inherited shell environment
  values, restart the CCB/backend process so it reads the new environment;
  then restart affected managed Agents as needed. Provider files and supported
  keyring state are re-read one-way, and session continuity is retained.
• Install the npm package with
  npm install -g @seemseam/ccb@8.5.6. Android users can install the signed
  CCB Mobile v8.5.6 APK from the v8.5.6 release.

Known limitations

• Native fork/import is capability-gated by the installed Provider CLI. When a
  CLI cannot import or fork, CCB preserves a linked continuation and does not
  claim that remote context was imported.
• Deterministic reconnect, isolated source-runtime, and synthetic capacity
  tests pass. Organic real network-disconnect and service-capacity events remain
  an open qualification item and were not manufactured for release testing.

Validation

• The focused Provider authority, restore, launch, and reconnect integration
  suite passed 189 tests. The final full source suite passed 6188 tests and 4
  subtests, with 2 skipped.
• An inspectable external source-runtime project re-read changed inherited
  Codex authority, advanced the authority generation without changing its
  stable CCB conversation id, and created a native fork whose user-message
  sequence matched the retained old transcript. A same-authority restart then
  resumed the same Codex thread. No session was archived; reconnect reached
  armed, normal shutdown changed it to off, and no project process residue
  remained.

中文

版本亮点

• CCB 现在按维度解析 Provider 权威状态。在 .ccb/ccb.config 中显式配置的
  API key、token、URL、route、账号选择或 Provider profile 优先用于对应维度；
  没有显式 CCB 权威的维度，才从当前外部 Provider 环境或登录状态继承。
• 停止后的 Provider generation 会根据新的外部快照和 CCB 私有 projection
  重新构建。整个流程是单向的：托管 Provider 的 refresh、logout、cleanup 和
  restart 不会写入用户 shell、Provider home、IDE、OS keyring 或远程登录。
• CCB 在不同 authority generation 之间保持一个稳定的 conversation identity。
  同一权威使用原生 resume；只有在已安装 CLI 能力和私有路径检查证明安全时，
  Codex、Claude、Gemini 才使用原生 fork/import；否则记录 linked continuation，
  并继续让旧 transcript 可发现。

修复与稳定性

• 只有在旧 session id 和路径证明属于该 Agent 时，才恢复已撤回 v8.5.5 的
  *-global/legacy-route 迁移形状。缺少 authority metadata 的旧会话会原位采用，
  不会被误判为自动 clear。authority 变化期间会保留 workspace、队列、session
  record 和历史。
• CCB 现在会在托管 Codex 形成明确 thread binding 后自动安装并 arm
  codex-reconnect。精确 thread/pane 的网络错误或选定模型容量错误必须先通过
  pane、cursor 和两次探测检查，随后最多提交一次字面量 continue。独立 Codex
  仍需通过 $reconnect on 主动启用。
• Relay 邀请默认配额继续为每 24 小时 1 GiB，社区二维码资源及缓存 key 已刷新。

升级说明

• v8.5.5 已于 2026-08-05 从 GitHub 撤回。托管会话不要安装该版本，请使用
  v8.5.6 或 v8.5.4。
• 无需迁移配置或数据。账号或 API 变化后不要执行 ccb clear。如果改变了继承的
  shell 环境变量，应重启 CCB/backend 进程，让新进程读取新的环境；随后按需重启
  受影响的托管 Agent。Provider 文件和支持的 keyring 状态会单向重新读取，会话
  连续性保持不变。
• npm 安装命令为 npm install -g @seemseam/ccb@8.5.6。Android 用户可从
  v8.5.6 Release 安装签名后的 CCB Mobile v8.5.6 APK。

已知限制

• 原生 fork/import 由所安装的 Provider CLI 能力决定。如果 CLI 不支持导入或分叉，
  CCB 会保留 linked continuation，不会声称远程上下文已导入。
• 确定性 reconnect、隔离 source-runtime 和合成容量错误测试均已通过；真实网络
  中断及真实服务容量事件仍是开放的 qualification 项，本次没有人为制造真实压力。

验证说明

• Provider authority、restore、launch 和 reconnect 集成重点测试共 189 个通过。
  最终完整源码测试为 6188 个测试和 4 个 subtest 通过，2 个跳过。
• 在可检查的外部 source-runtime 项目中，Codex 重新读取了已变化的继承权威，
  authority generation 正常递增，同时稳定 CCB conversation id 保持不变；新建的
  原生 fork 与保留的旧 transcript 具有完全相同的用户消息序列。随后在同一权威下
  restart 继续使用同一个 Codex thread。整个过程没有归档任何 session；reconnect
  达到 armed，正常关闭后变为 off，且未留下该项目的运行进程。

CCB v8.5.4

Released: 2026-08-03

English

Safer ask routing

• --chain is now documented consistently across all inherited Provider ask
  skills as a dependency mechanism, not a general reply option. Use it only
  when an active parent task cannot finish without the exact child result.
• Independent asks, communication tests, batch sends, and notifications no
  longer imply a chain merely because a reply may be useful. Tasks that do not
  need a successful result can continue to use --silence.
• Control-plane reply_delivery acknowledgement work is excluded from active
  parent detection. An overlapping ordinary ask is no longer rejected as
  nested work or attached to a false callback edge.

Bounded Agent history cleanup

• Config UI can scan and clean managed Provider transcript history for one
  exact Agent or all Agents, with 7, 30, or 90 days of retention.
• Cleanup protects active session bindings, all history inside the selected
  retention window, and the newest transcript for each Agent/Provider binding.
  Deletion remains restricted to the managed transcript allowlist and is
  serialized with project lifecycle changes.
• The current control panel keeps configuration, activation review, and Agent
  history cleanup. The read-only communication-flow observer is temporarily
  removed from the shipped DOM, animation code, trace drawer, and event
  handlers.

Mobile LAN recovery

• Android now reads only coarse connected/Wi-Fi/Ethernet/cellular/VPN
  booleans. It does not request location or read SSID, BSSID, addresses,
  device identifiers, credentials, or pairing secrets.
• LAN pairing shows an advisory when no local-network transport is visible,
  while retaining Continue anyway for phone-hotspot and platform edge
  cases. Non-LAN routes are unchanged.
• A reconnecting LAN route keeps its stored profile and shows a persistent,
  localized explanation with Retry and authenticated Diagnostics.
  Guidance covers same-network, guest/client isolation, VPN, firewall, and
  computer DHCP address changes.
• Terminal WebSockets now use a 15-second client ping interval. Silent Wi-Fi
  half-open connections enter the existing reconnect and cursor-resume path
  without replaying input frames.

Validation and upgrade notes

• No configuration or data migration is required. Restart already-running CCB
  projects after upgrading so managed ask skills and Config UI load the new
  release.
• Focused Python routing, cleanup, Config UI, Mobile onboarding, and release
  integration regression tests passed (208 tests). Flutter 3.44.2 static analysis reported no issues,
  and the complete App suite passed 736 tests with 1 existing skip.
• The physical Android Wi-Fi, phone-hotspot, guest-isolation, VPN, and DHCP
  address-change matrix was not executed for this release. Android remains the
  release build target; iOS/iPadOS remain source-supported but were not built
  or device-tested here.
• npm-managed installations can run
  npm install -g @seemseam/ccb@8.5.4.
• Android users can install the signed CCB Mobile v8.5.4 APK from this release.

中文

更安全的 ask 路由

• 所有继承到 Provider 的 ask skill 现在统一把 --chain 定义为依赖机制，
  而不是通用的“需要回复”选项。只有当前 active parent task 必须等待这个
  child 的精确结果才能完成时，才应使用 --chain。
• 独立 ask、通讯测试、批量发送和通知不会因为“回复可能有用”就自动形成
  chain；不需要成功结果的任务仍可使用 --silence。
• 控制面的 reply_delivery 确认任务不再参与 active parent 检测。与它重叠
  的普通 ask 不会被误判为嵌套任务，也不会挂到错误的 callback edge 上。

有界的 Agent 历史清理

• Config UI 支持按一个指定 Agent 或全部 Agent 扫描、清理托管 Provider
  transcript 历史，可选择保留 7、30 或 90 天。
• 清理会保护当前 session 绑定、保留期内的全部历史，以及每个
  Agent/Provider 绑定最新的一份 transcript。删除范围严格限制在托管
  transcript allowlist 中，并与项目生命周期变更串行化。
• 当前控制面板保留配置、激活检查和 Agent 历史清理。只读的通讯流观察区
  暂时下架，其 DOM、动画代码、trace drawer 和事件处理器均不再随版本发布。

Mobile 局域网恢复

• Android 只读取 connected/Wi-Fi/Ethernet/cellular/VPN 等粗粒度布尔状态，
  不申请定位权限，也不读取 SSID、BSSID、地址、设备标识、凭据或配对秘密。
• LAN 配对时，如果没有发现本地网络传输，App 会先显示提示；同时为手机热点
  和平台边缘情况保留“仍然继续”。非 LAN 路由不受影响。
• LAN 路由重连时会保留已存 profile，并持续显示本地化原因，同时提供“重试”
  和经过认证的“诊断”。提示覆盖同一网络、访客/设备隔离、VPN、防火墙和
  电脑 DHCP 地址变化。
• Terminal WebSocket 增加 15 秒客户端 ping。Wi-Fi 静默半开连接会进入现有
  reconnect 和 cursor-resume 流程，不会重放输入帧。

验证与升级说明

• 无需迁移配置或数据。升级后请重启已经运行的 CCB 项目，使托管 ask skill
  和 Config UI 加载新版本。
• ask 路由、历史清理、Config UI、Mobile onboarding 和发布集成的重点
  Python 回归共 208 个测试通过；Flutter 3.44.2 静态分析无问题，完整 App 测试
  736 个通过，保留 1 个既有 skip。
• 本版本没有执行 Android 真机 Wi-Fi、手机热点、访客网络隔离、VPN 和 DHCP
  地址变化矩阵。Android 仍是发布构建目标；iOS/iPadOS 保持源码支持，但本轮
  未构建、未做真机测试。
• npm 安装可执行：
  npm install -g @seemseam/ccb@8.5.4。
• Android 用户可从本 Release 安装签名后的 CCB Mobile v8.5.4 APK。

CCB v8.5.3

Released: 2026-08-01

English

Relay capacity

• Newly issued Relay Host invitations now default to 200 MiB per 24-hour
  quota window instead of 100 MiB. Operators can still choose another limit
  with --max-bytes-per-day.
• Existing Relay Host credentials keep the quota recorded when they were
  issued. To change one, the Relay operator must update that Host separately or
  issue and activate a new invitation.

Callback and daemon reliability

• CCB now keeps a process-local latest-state view of the append-only callback
  edge ledger and safely rebuilds it after an external append, replacement, or
  truncation.
• Callback repair ignores terminal history, bounds the candidates that still
  need recovery, and scans each relevant target's job history at most once per
  tick. Long-lived projects no longer turn historical callback growth into
  sustained idle CPU and cached-read amplification.
• JSONL remains the only durable callback authority; no ledger migration or
  manual cleanup is required.

Claude agent environment

• Non-API variables from agents.<name>.env, such as proxy settings and tool
  configuration paths, now reach managed Claude processes. CCB's API
  credential, endpoint, and managed runtime-home precedence remains unchanged
  (PR #284).

Upgrade notes

• No configuration or data migration is required.
• Restart already-running CCB projects after upgrading so the daemon and
  managed Claude processes load the new behavior.
• npm-managed installations can run
  npm install -g @seemseam/ccb@8.5.3.
• Android users can install the signed CCB Mobile v8.5.3 APK from this release.

中文

Relay 容量

• 新签发的 Relay Host 邀请默认使用每个 24 小时配额窗口 200 MiB 的上限，
  不再是 100 MiB；运营端仍可通过 --max-bytes-per-day 指定其他上限。
• 已有 Relay Host 凭据继续使用签发时记录的配额。如需修改，Relay
  运营端必须单独更新该 Host，或重新签发并激活新的邀请。

Callback 与 daemon 稳定性

• CCB 现在为只追加的 callback edge ledger 维护进程内最新状态视图；
  检测到外部追加、替换或截断后会安全重建。
• Callback 修复会忽略已终结的历史记录，限制仍需恢复的候选，并且每个
  tick 对每个相关目标最多扫描一次 job history。长生命周期项目不再因
  callback 历史增长而出现持续的空闲高 CPU 和缓存读放大。
• JSONL 仍是唯一持久化 callback 权威，无需迁移 ledger，也无需手动清理。

Claude Agent 环境变量

• agents.<name>.env 中的非 API 变量（例如代理设置和工具配置路径）现在
  会传入托管 Claude 进程。CCB 对 API 凭据、endpoint 和托管 runtime-home
  的优先级保持不变（PR #284）。

升级说明

• 无需迁移配置或数据。
• 升级后请重启已经运行的 CCB 项目，使 daemon 和托管 Claude 进程加载
  新行为。
• npm 安装可执行：
  npm install -g @seemseam/ccb@8.5.3。
• Android 用户可从本 Release 安装签名后的 CCB Mobile v8.5.3 APK。

CCB v8.5.2

Released: 2026-07-30

English

Bounded pane recovery and disk safety

• A replacement pane now remains in a 90-second probation window and must
  receive a new healthy observation before recovery succeeds. Queued work is
  held while the runtime is probing.
• Consecutive unstable recoveries back off for 30 seconds, 60 seconds,
  120 seconds, 5 minutes, 10 minutes, and 30 minutes. After six attempts CCB
  opens a recovery circuit and stops further respawns, crash captures, and
  dispatch until an explicit restart or remount.
• Each Provider runtime retains only the newest 50 pane-crash logs and matching
  reason records. Pane history is cleared before respawn, and unchanged helper
  manifests are no longer rewritten.
• A stale CCB-managed Claude --continue binding can be removed without
  changing Provider authentication. A missing managed Codex app server now
  fails closed with an actionable restart/remount diagnostic.

Quieter managed communication

• Stable reply and cancellation guidance now lives once in managed project
  memory instead of being repeated in every ask prompt.
• Normal asks no longer inject the default reply block or require the Agent to
  poll a cancellation file before every work step. Compact and silent asks add
  only their requested mode metadata, while runtime interruption remains the
  primary cancellation mechanism.

Isolated Rich terminal launches

• CCB Rich WezTerm launches now use a new process session with stdin, stdout,
  and stderr detached from the invoking shell. GUI diagnostics and job-control
  signals no longer pollute or stop the parent terminal job.
• On Linux Wayland, the workbench provisions a private XCursor overlay for the
  missing hand cursor while preserving the selected cursor theme and leaving
  user and system cursor files unchanged.

Upgrade notes

• No configuration migration is required.
• Restart already-running CCB projects after upgrading so they load the new
  recovery and managed-memory behavior.
• Existing Rich users should run ccb update rich once to regenerate the
  detached launcher and Wayland cursor compatibility overlay.
• If an Agent reaches recovery-circuit-open, repair its Provider/session
  state and then run ccb restart <agent> or remount the project.
• npm-managed installations can run
  npm install -g @seemseam/ccb@8.5.2.
• Android users can install the signed CCB Mobile v8.5.2 APK from this release.

中文

有界 pane 恢复与磁盘保护

• 替换后的 pane 现在会进入 90 秒观察期，并且必须获得一次新的健康观测后
  才能确认恢复成功；runtime 处于探测状态时，队列任务会保持等待。
• 连续不稳定恢复依次退避 30 秒、60 秒、120 秒、5 分钟、10 分钟和
  30 分钟。第六次仍不稳定时，CCB 会打开恢复熔断，并停止继续 respawn、
  捕获崩溃和派发任务，直到显式 restart 或 remount。
• 每个 Provider runtime 只保留最新 50 份 pane crash 日志及对应原因记录。
  respawn 前会清空 pane history，内容未变化的 helper manifest 也不再重复
  写盘。
• CCB 可以移除失效的 Claude --continue 绑定，同时不改动 Provider
  登录状态。托管 Codex app server 缺失时则会安全停止，并给出明确的
  restart/remount 诊断。

更简练的托管通讯

• 稳定的回复和取消规则现在只写入一次托管项目记忆，不再在每次 ask
  prompt 中重复注入。
• 普通 ask 不再附加默认回复段落，也不再要求 Agent 每一步都轮询取消文件。
  compact 和 silent ask 只添加所需的模式元数据，runtime interruption
  继续作为主要取消机制。

隔离的 Rich 终端启动

• CCB Rich WezTerm 现在使用独立进程会话启动，并断开与调用 shell 的
  stdin、stdout 和 stderr。GUI 诊断及 job-control 信号不会再污染或暂停
  父终端任务。
• 在 Linux Wayland 下，workbench 会提供私有 XCursor overlay，补齐缺失
  的 hand cursor，同时保留用户选择的 cursor theme，且不会修改用户或
  系统 cursor 文件。

升级说明

• 无需迁移现有配置。
• 升级后请重启已经运行的 CCB 项目，使其加载新的恢复和托管记忆行为。
• 已启用 Rich 的用户应执行一次 ccb update rich，重新生成隔离 launcher
  和 Wayland cursor 兼容 overlay。
• 如果 Agent 进入 recovery-circuit-open，请先修复其 Provider/session
  状态，再执行 ccb restart <agent> 或重新挂载项目。
• npm 安装可执行：
  npm install -g @seemseam/ccb@8.5.2。
• Android 用户可从本 Release 安装签名后的 CCB Mobile v8.5.2 APK。