Skip to content

v8.6.2

Choose a tag to compare

View all tags
@SeemSeam SeemSeam released this 12 Aug 23:22
· 282 commits to main since this release
v8.6.2
64b80c4

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，需要文档列出的外部依赖，且启动器尚未签名。
Assets 12
Loading