v8.6.9

Released: 2026-08-17

English

CCB now supports the official DeepSeek Harness under the separate Developer
Preview provider key dsh. The existing deepseek key continues to launch
the Deep Code CLI and is not replaced.
Managed AGY 1.1.13 sessions now select their private file token store before
authentication starts, eliminating the unavailable-keyring delay reported
in Issue #318.

DSH uses its structured loopback HTTP/WebSocket carrier for prompts, native
events, approvals, cancellation, clear, compact, and exact-session restore.
Its current POSIX pane is only a lifecycle/log carrier and cannot supply
prompt, reply, quiet-time, or successful-completion authority.
DSH completion requires the exact durable source.rpcId, a committed
non-empty assistant reply from the same turn, and native
turn/end(completed). Restore is observer-only and never reposts a prompt.
DSH credentials, API routes, settings, skills, memory, sessions, and caches
remain inside an agent-private DSH_HOME; only allowlisted user state is
copied in one direction.
CCB refreshes AGY's provider-recognized keyring-unavailable marker only
inside the managed AGY HOME. Legacy links fail closed, user environment
overrides cannot redirect the final HOME, and other providers receive no
AGY-specific storage setting.
Windows changes that had modified shared Linux/macOS runtime behavior were
rolled back. A trusted-base, native-only Windows PR gate now rejects changes
to shared clients, global release metadata, Mobile, npm, generic tests, and
new reverse imports into Windows implementation modules.

No project, conversation, pairing, or configuration migration is required.
DeepSeek Harness is optional. Install @deepseek-ai/dsh with Node
^22.19 || >=24, configure user-owned DeepSeek credentials, and select
provider dsh explicitly.
Existing AGY agents need only restart to receive the private file-storage
selection.

DSH 0.1.0-rc.6 is Developer Preview software. CCB validated its official
loopback carrier, exact native failure handling, restart, clear, and compact
paths; authenticated answer success still requires user-owned credentials
and remains a separate qualification claim.
Native Windows x64 and Herdr remain beta. Real Windows GUI/provider and
macOS qualification remain required CI or platform-owner gates.

CCB 以独立 Developer Preview provider key dsh 接入官方 DeepSeek
Harness。现有 deepseek key 仍然启动 Deep Code CLI，不会被替换。
受管 AGY 1.1.13 现在会在认证开始前选择自己的私有文件 token 存储，消除
Issue #318 报告的不可用 keyring 等待。

DSH 的 prompt、native event、approval、cancel、clear、compact 和精确
session 恢复都通过结构化 loopback HTTP/WebSocket carrier 完成。当前 POSIX
pane 仅承担生命周期与日志承载，不能作为 prompt、reply、静默时间或成功完成
的权威。
DSH 只有同时取得精确持久化 source.rpcId、同一 turn 内已提交的非空
assistant reply，以及 native turn/end(completed) 才会完成；恢复只观察
历史，绝不重复提交 prompt。
DSH 的凭据、API route、settings、skills、memory、session 与 cache 均保留在
Agent 私有 DSH_HOME 中；用户状态只按 allowlist 单向复制。
CCB 只在 AGY 的受管 HOME 内刷新 provider 自身识别的 keyring-unavailable
marker。旧链接无法解除时会 fail closed，用户环境不能改回最终 HOME，其他
provider 也不会收到 AGY 专用存储设置。
已撤销会修改 Linux/macOS 共享运行时行为的 Windows 改动。新的原生 Windows
专用门禁从可信 base 执行，会拒绝共享客户端、全局发布元数据、Mobile、npm、
通用测试，以及新增的 Windows 实现反向 import。

无需迁移项目、对话、配对或配置。
DeepSeek Harness 是可选 provider。请使用 Node ^22.19 || >=24 安装
@deepseek-ai/dsh，配置用户自有 DeepSeek 凭据，并显式选择 provider
dsh。
现有 AGY Agent 只需重启，即可使用新的私有文件存储选择。

DSH 0.1.0-rc.6 仍是 Developer Preview。CCB 已验证官方 loopback carrier、
精确 native 失败处理、重启、clear 与 compact；认证成功回答仍依赖用户自有
凭据，属于需要单独验证的能力声明。
原生 Windows x64 与 Herdr 仍处于 beta；真实 Windows GUI/provider 和 macOS
验证仍需通过对应 CI 或平台维护者门禁。