@yu_robotics/remote-cli 1.6.264 → 1.6.265
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +41 -0
- package/dist/client/MessageHandler.d.ts +12 -2
- package/dist/client/MessageHandler.d.ts.map +1 -1
- package/dist/client/MessageHandler.js +320 -168
- package/dist/client/MessageHandler.js.map +1 -1
- package/dist/client/WebSocketClient.d.ts.map +1 -1
- package/dist/client/WebSocketClient.js +1 -0
- package/dist/client/WebSocketClient.js.map +1 -1
- package/dist/delegation/piExtension.js +1 -1
- package/dist/delegation/piExtension.js.map +1 -1
- package/dist/executor/AcpExecutor.d.ts +11 -4
- package/dist/executor/AcpExecutor.d.ts.map +1 -1
- package/dist/executor/AcpExecutor.js +64 -11
- package/dist/executor/AcpExecutor.js.map +1 -1
- package/dist/executor/AgyExecutor.d.ts +6 -0
- package/dist/executor/AgyExecutor.d.ts.map +1 -1
- package/dist/executor/AgyExecutor.js +126 -9
- package/dist/executor/AgyExecutor.js.map +1 -1
- package/dist/executor/ClaudePersistentExecutor.d.ts +5 -1
- package/dist/executor/ClaudePersistentExecutor.d.ts.map +1 -1
- package/dist/executor/ClaudePersistentExecutor.js +81 -17
- package/dist/executor/ClaudePersistentExecutor.js.map +1 -1
- package/dist/executor/CodexAppServerClient.d.ts +1 -1
- package/dist/executor/CodexAppServerClient.d.ts.map +1 -1
- package/dist/executor/CodexAppServerClient.js +8 -2
- package/dist/executor/CodexAppServerClient.js.map +1 -1
- package/dist/executor/CodexAppServerExecutor.d.ts +3 -1
- package/dist/executor/CodexAppServerExecutor.d.ts.map +1 -1
- package/dist/executor/CodexAppServerExecutor.js +67 -22
- package/dist/executor/CodexAppServerExecutor.js.map +1 -1
- package/dist/executor/DshExecutor.d.ts +2 -0
- package/dist/executor/DshExecutor.d.ts.map +1 -1
- package/dist/executor/DshExecutor.js +26 -6
- package/dist/executor/DshExecutor.js.map +1 -1
- package/dist/executor/IExecutor.d.ts +4 -0
- package/dist/executor/IExecutor.d.ts.map +1 -1
- package/dist/executor/PiExecutor.d.ts +2 -0
- package/dist/executor/PiExecutor.d.ts.map +1 -1
- package/dist/executor/PiExecutor.js +96 -23
- package/dist/executor/PiExecutor.js.map +1 -1
- package/dist/executor/acp/AcpClient.d.ts +4 -3
- package/dist/executor/acp/AcpClient.d.ts.map +1 -1
- package/dist/executor/acp/AcpClient.js +18 -2
- package/dist/executor/acp/AcpClient.js.map +1 -1
- package/dist/executor/agy/AgyAcpRuntime.d.ts +8 -1
- package/dist/executor/agy/AgyAcpRuntime.d.ts.map +1 -1
- package/dist/executor/agy/AgyAcpRuntime.js +47 -3
- package/dist/executor/agy/AgyAcpRuntime.js.map +1 -1
- package/dist/executor/agy/AgySessionSelection.d.ts +3 -0
- package/dist/executor/agy/AgySessionSelection.d.ts.map +1 -1
- package/dist/executor/agy/AgySessionSelection.js +24 -0
- package/dist/executor/agy/AgySessionSelection.js.map +1 -1
- package/dist/executor/dsh/DshAcpClient.d.ts +1 -1
- package/dist/executor/dsh/DshAcpClient.d.ts.map +1 -1
- package/dist/executor/dsh/DshAcpClient.js +2 -2
- package/dist/executor/dsh/DshAcpClient.js.map +1 -1
- package/dist/executor/pi/PiClient.d.ts +3 -1
- package/dist/executor/pi/PiClient.d.ts.map +1 -1
- package/dist/executor/pi/PiClient.js +15 -1
- package/dist/executor/pi/PiClient.js.map +1 -1
- package/dist/executor/pi/PiTypes.d.ts +3 -1
- package/dist/executor/pi/PiTypes.d.ts.map +1 -1
- package/dist/executor/pi/PiTypes.js.map +1 -1
- package/dist/executor/zcode/ZCodeClient.d.ts +2 -2
- package/dist/executor/zcode/ZCodeClient.d.ts.map +1 -1
- package/dist/executor/zcode/ZCodeClient.js +26 -7
- package/dist/executor/zcode/ZCodeClient.js.map +1 -1
- package/dist/maintenance/release-notes.json +1 -1
- package/dist/managed/tools.d.ts +6 -6
- package/dist/scheduling/ScheduleCapabilities.d.ts +59 -14
- package/dist/scheduling/ScheduleCapabilities.d.ts.map +1 -1
- package/dist/scheduling/ScheduleCapabilities.js +33 -29
- package/dist/scheduling/ScheduleCapabilities.js.map +1 -1
- package/dist/scheduling/ScheduleCardService.d.ts.map +1 -1
- package/dist/scheduling/ScheduleCardService.js +3 -1
- package/dist/scheduling/ScheduleCardService.js.map +1 -1
- package/dist/scheduling/ScheduleCleanup.d.ts +3 -2
- package/dist/scheduling/ScheduleCleanup.d.ts.map +1 -1
- package/dist/scheduling/ScheduleCleanup.js +3 -0
- package/dist/scheduling/ScheduleCleanup.js.map +1 -1
- package/dist/scheduling/ScheduleCommand.d.ts +1 -3
- package/dist/scheduling/ScheduleCommand.d.ts.map +1 -1
- package/dist/scheduling/ScheduleCommand.js +10 -62
- package/dist/scheduling/ScheduleCommand.js.map +1 -1
- package/dist/scheduling/ScheduleDeliveryClient.d.ts +2 -1
- package/dist/scheduling/ScheduleDeliveryClient.d.ts.map +1 -1
- package/dist/scheduling/ScheduleDeliveryClient.js +20 -8
- package/dist/scheduling/ScheduleDeliveryClient.js.map +1 -1
- package/dist/scheduling/ScheduleService.d.ts +44 -4
- package/dist/scheduling/ScheduleService.d.ts.map +1 -1
- package/dist/scheduling/ScheduleService.js +537 -72
- package/dist/scheduling/ScheduleService.js.map +1 -1
- package/dist/scheduling/ScheduleToolScope.d.ts +4 -1
- package/dist/scheduling/ScheduleToolScope.d.ts.map +1 -1
- package/dist/scheduling/ScheduleToolScope.js +14 -13
- package/dist/scheduling/ScheduleToolScope.js.map +1 -1
- package/dist/scheduling/agy/AgyHookRelay.d.ts +3 -0
- package/dist/scheduling/agy/AgyHookRelay.d.ts.map +1 -1
- package/dist/scheduling/agy/AgyHookRelay.js +15 -1
- package/dist/scheduling/agy/AgyHookRelay.js.map +1 -1
- package/dist/scheduling/claude/ClaudeScheduleOwnership.d.ts +2 -0
- package/dist/scheduling/claude/ClaudeScheduleOwnership.d.ts.map +1 -1
- package/dist/scheduling/claude/ClaudeScheduleOwnership.js +11 -0
- package/dist/scheduling/claude/ClaudeScheduleOwnership.js.map +1 -1
- package/dist/scheduling/claude/ClaudeSessionSchedules.d.ts +3 -2
- package/dist/scheduling/claude/ClaudeSessionSchedules.d.ts.map +1 -1
- package/dist/scheduling/claude/ClaudeSessionSchedules.js +12 -4
- package/dist/scheduling/claude/ClaudeSessionSchedules.js.map +1 -1
- package/dist/scheduling/dsh/ScheduledSessionGuard.js +1 -1
- package/dist/scheduling/dsh/ScheduledSessionGuard.js.map +1 -1
- package/dist/scheduling/host/HostScheduleRule.d.ts +6 -0
- package/dist/scheduling/host/HostScheduleRule.d.ts.map +1 -0
- package/dist/scheduling/host/HostScheduleRule.js +144 -0
- package/dist/scheduling/host/HostScheduleRule.js.map +1 -0
- package/dist/scheduling/toolContract.d.ts +3 -3
- package/dist/scheduling/toolContract.js +4 -4
- package/dist/scheduling/toolContract.js.map +1 -1
- package/dist/scheduling/types.d.ts +20 -2
- package/dist/scheduling/types.d.ts.map +1 -1
- package/dist/scheduling/types.js.map +1 -1
- package/dist/types/ScheduleCards.d.ts +2 -1
- package/dist/types/ScheduleCards.d.ts.map +1 -1
- package/dist/types/index.d.ts +2 -0
- package/dist/types/index.d.ts.map +1 -1
- package/native/prebuilds/darwin-arm64/managed_native.node +0 -0
- package/native/prebuilds/darwin-arm64/manifest.json +1 -1
- package/native/prebuilds/darwin-x64/managed_native.node +0 -0
- package/native/prebuilds/darwin-x64/manifest.json +1 -1
- package/native/prebuilds/win32-arm64/managed_native.node +0 -0
- package/native/prebuilds/win32-arm64/manifest.json +1 -1
- package/native/prebuilds/win32-x64/managed_native.node +0 -0
- package/native/prebuilds/win32-x64/manifest.json +1 -1
- package/package.json +1 -1
|
@@ -1 +1 @@
|
|
|
1
|
-
{"format":1,"firstVersion":"1.6.123","sections":[{"version":"1.6.264","text":"### 修复 AGY 提问流程\n- AGY 提问时显示等待输入,直接在原线程回复即可继续。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"AGY 提问时显示等待输入,直接在原线程回复即可继续。"}],"details":"### Fixed\n- Keep AGY ACP foreground turns open while native questions await an answer. Route replies to the same session and require the native Stop receipt before completing the turn. Release queue admission when a failed foreground leaves the host fenced."},{"version":"1.6.263","text":"### 恢复 Claude 旧会话中的定时任务管理\n- 重连原 Claude 会话后,可以让 Agent 列出并删除选定的旧任务,再在同一会话创建新任务。","changes":[{"topic":"native-schedules","title":"定时任务","text":"重连原 Claude 会话后,可以让 Agent 列出并删除选定的旧任务,再在同一会话创建新任务。"}],"details":"### Fixed\n- Restore agent-requested cleanup and new schedule creation in the original managed Claude session after a restart. Install SDK admission hooks at initialization and reject unclassified resumed input without a current foreground command. Explicit Cron disables remain effective."},{"version":"1.6.262","text":"### 改善 Claude 和 AGY 定时任务创建\n- Claude 会话缺少所需定时工具时,直接提示原因,避免等待无法执行的创建操作。\n- 旧会话启动时禁用定时工具,会明确提示查看历史列表无法解锁清理;删除任务需要核对原生删除回执。\n- 修复 AGY 思考或查询状态较久时,尚未调用创建工具就超时失败的问题;取消和未确认任务仍保留保护。","changes":[{"topic":"native-schedules","title":"定时任务","text":"Claude 会话缺少所需定时工具时,直接提示原因,避免等待无法执行的创建操作。"},{"topic":"native-schedules","title":"定时任务","text":"旧会话启动时禁用定时工具,会明确提示查看历史列表无法解锁清理;删除任务需要核对原生删除回执。"},{"topic":"native-schedules","title":"定时任务","text":"修复 AGY 思考或查询状态较久时,尚未调用创建工具就超时失败的问题;取消和未确认任务仍保留保护。"}],"details":"### Fixed\n- Refuse Claude schedule creation when native initialization reports missing Cron tools or lifecycle support, before reserving schedule ownership or returning a native creation action.\n- Report when Claude started with Cron disabled. Reviewed cleanup requires a native inventory and an exact deletion receipt for each selected task.\n- Start the AGY same-turn native receipt deadline at the exact authorized tool dispatch, so model reasoning, tool discovery and operation polling do not expire an uninvoked action. Keep bounded post-dispatch waits and existing uncertainty protections.\n- Retire pending AGY actions on foreground completion, cancellation or ownership loss; a final inventory receipt cannot authorize a successor action after its turn ends."},{"version":"1.6.261","text":"### 更正 AGY 定时能力提示\n- 明确旧会话需主动清空、ACP 子任务不支持原生定时任务;保留历史与清理保护,不自动恢复任务。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"明确旧会话需主动清空、ACP 子任务不支持原生定时任务;保留历史与清理保护,不自动恢复任务。"}],"details":"### Fixed\n- Correct AGY scheduling capability text: legacy stream-json selections require explicit clear, and managed workers use ACP without native scheduling. This does not change execution, ownership or cleanup policy.\n\n### Tests\n- Replace obsolete AGY stream-json activity and internal-queue fixtures with ACP/hook terminal, cancellation and overlap regressions; exercise the real managed-child registration guard.\n- Canonicalize receipt fixture HOME through the native realpath API, expose bounded capture diagnostics in tests, and verify alias/replaced-root refusal before any prompt. Windows CI remains required for platform acceptance."},{"version":"1.6.260","text":"### AGY 统一会话通信与更多并行任务\n- 主会话和子任务统一使用 ACP,旧会话需主动清空后再开始;不会自动迁移历史或恢复定时任务。\n- 空闲会话可直接确认模型和思考强度,支持审批与图片输入;存在定时任务或未确认状态时保留保护限制。\n- 全局同时运行名额增至 20,单个 Git 请求最多同时运行 12 个任务;累计仍限 12 个,非 Git 目录仍串行执行。\n- 异常退出后,仅在确认旧进程组已退出时修复遗留钩子;未知归属保留并提示处理,子任务清空不会误报成功。\n- 工具拒绝请求或后台任务创建记录会阻止会话复用,避免把原生成功状态误当成安全续聊依据。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"主会话和子任务统一使用 ACP,旧会话需主动清空后再开始;不会自动迁移历史或恢复定时任务。"},{"topic":"agy-session","title":"AGY 会话","text":"空闲会话可直接确认模型和思考强度,支持审批与图片输入;存在定时任务或未确认状态时保留保护限制。"},{"topic":"delegation","title":"委派任务","text":"全局同时运行名额增至 20,单个 Git 请求最多同时运行 12 个任务;累计仍限 12 个,非 Git 目录仍串行执行。"},{"topic":"agy-session","title":"AGY 会话","text":"异常退出后,仅在确认旧进程组已退出时修复遗留钩子;未知归属保留并提示处理,子任务清空不会误报成功。"},{"topic":"agy-session","title":"AGY 会话","text":"工具拒绝请求或后台任务创建记录会阻止会话复用,避免把原生成功状态误当成安全续聊依据。"}],"details":"### Changed\n- Use ACP exclusively for AGY main and worker conversation execution. Remove persistent stream-json spawning, parsing and fallback; legacy selections require explicit clear. Keep native history, exact ownership and cleanup guards.\n- Confirm AGY live model/effort controls, route manual approvals, preserve native hook terminal errors, and record worker creation receipts before prompting. Loaded or reconfigured sessions cannot acquire fresh scheduling admission; uncertain outcomes remain refused.\n- Increase global occupied worker capacity to 20 and effective Git-request parallelism to 12. Keep the cumulative 12-task quota, serial non-Git workspaces, admission rejection at full capacity, FIFO, cancellation and exact exit/artifact slot accounting.\n- Forward AGY image inputs over ACP and retain bounded native informational helpers and explicit summarize-then-reset compaction. No automatic schedule restoration or exit-time handoff is added.\n\n### Fixed\n- Restore only proven-owned stale AGY hook overlays after exact prior owner/group exit, using per-HOME kernel exclusion and durable atomic restoration metadata. Preserve user hook edits and refuse unknown legacy or ambiguous ownership with actionable diagnostics.\n- Permanently fence AGY host continuity after any requested tool denial or observed background-task creation receipt, including DONE receipts followed by successful Stop. Older continuity receipts no longer grant worker reuse.\n- Keep worker-card Clear truthful for unconfirmed AGY allocation/schedule ownership, archive ACP selections, and guide settings attempts on refused saved main selections to explicit clear. Busy AGY transitions do not bypass shared reset admission."},{"version":"1.6.259","text":"### 修复定时任务状态保留\n- 修复 Windows 重复记录 DSH 会话保护标记时的刷盘错误,保留原有凭据和续聊限制。\n- 取消未能确认完成时,保留任务原本的中断原因及取消意图,不会把进程退出误报为原生任务已删除。","changes":[{"topic":"native-schedules","title":"定时任务","text":"修复 Windows 重复记录 DSH 会话保护标记时的刷盘错误,保留原有凭据和续聊限制。"},{"topic":"native-schedules","title":"定时任务","text":"取消未能确认完成时,保留任务原本的中断原因及取消意图,不会把进程退出误报为原生任务已删除。"}],"details":"### Fixed\n- Reopen existing DSH refusal markers with write access before flushing on Windows, without truncating evidence or bypassing file/symlink validation. Repeated marking retains the permanent refusal and all durability checks.\n- Preserve the original interruption diagnostic when retained cancellation fails. Cancellation still reports its error and retains intent; confirmed process exit is never promoted to native deletion success or permission to clean up through a successor.\n\n### Tests\n- Correct late Claude CREATE fixtures to assert unresolved deletion separately from confirmed process exit, retaining the exact handle, interruption reason and no-successor-prompt assertions.\n- Await delegation terminal receipts before asserting notice counts, with a controlled final-metadata gate. Give native artifact entry and completion separate 30-second fixture phases, with regressions for false shared-budget timeouts and continued ownership after real phase timeouts. No production Git deadlines or publication gates were relaxed."},{"version":"1.6.258","text":"### 修复 AGY 新会话设置\n- 新建 ACP 会话会先确认所选模型和思考强度,再开始聊天或接收定时任务,避免因不支持的启动参数悄悄失去定时能力。\n- 设置失败会显示脱敏原因;已分配的失败会话保留历史,需主动 /clear 后再尝试新会话,不会自动恢复。\n- 已有 ACP 会话中修改模型或思考强度仍沿用旧传输切换方式,兼容性未确认;建议在允许清空时主动 /clear,将设置应用到新 ACP 会话。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"新建 ACP 会话会先确认所选模型和思考强度,再开始聊天或接收定时任务,避免因不支持的启动参数悄悄失去定时能力。"},{"topic":"agy-session","title":"AGY 会话","text":"设置失败会显示脱敏原因;已分配的失败会话保留历史,需主动 /clear 后再尝试新会话,不会自动恢复。"},{"topic":"agy-session","title":"AGY 会话","text":"已有 ACP 会话中修改模型或思考强度仍沿用旧传输切换方式,兼容性未确认;建议在允许清空时主动 /clear,将设置应用到新 ACP 会话。"}],"details":"### Fixed\n- Configure fresh AGY ACP model and thinking-level selections through session controls instead of unsupported launch flags. Persist allocation before setup; grant host admission only after native state confirms the requested settings.\n- Fence prompts during initial ACP setup and invalidate setup on competing session controls, cancellation or process retirement. Preserve ordinary ACP backend behavior and DSH callback ownership semantics.\n- Report sanitized startup stage/category diagnostics and visible pre-allocation stream-json fallback. After allocated setup failure, keep the saved selection refused, release only a confirmed-closed runtime, and support explicit archival reset without restoring saved sessions or exit handoff.\n\n### Tests\n- Cover settings confirmation, native aliases, rejected controls, setup races/timeouts, guided refusal/reset and generic ACP backends. Live ACP model/effort switching still uses the existing unverified stream-json transition; use explicit clear for fresh ACP settings."},{"version":"1.6.257","text":"### 定时任务仅在当前会话运行\n- 移除自动恢复功能;CLI、电脑或原生会话进程重启后,未完成任务显示为中断,不会自动重建或补跑。\n- 保留运行中的创建、查看、取消、精确清理及已完成结果投递;原始会话历史不会自动删除。\n- 退出和更新不再通过模型交接定时任务;历史未确认任务保留清理证据,不再挤占当前可运行任务的名额。\n- AGY ACP 保存会话重启后无法安全续聊,即使没有定时任务日志;无任务归属和过渡锁时可主动 /clear 开启新会话,旧历史和未确认凭据保留,线程删除仍受限制;未加载的 AGY 仍有任务归属记录时,切换后端也无法清空或改目录,需使用新线程。\n- 新建 DSH 任务记录准确的原会话归属,创建前启动失败不再误封续聊,不阻塞无关的新会话;旧记录缺少归属时仍保守拒绝,请勿删除未确认凭据。","changes":[{"topic":"native-schedules","title":"定时任务","text":"移除自动恢复功能;CLI、电脑或原生会话进程重启后,未完成任务显示为中断,不会自动重建或补跑。"},{"topic":"native-schedules","title":"定时任务","text":"保留运行中的创建、查看、取消、精确清理及已完成结果投递;原始会话历史不会自动删除。"},{"topic":"native-schedules","title":"定时任务","text":"退出和更新不再通过模型交接定时任务;历史未确认任务保留清理证据,不再挤占当前可运行任务的名额。"},{"topic":"agy-session","title":"AGY 会话","text":"AGY ACP 保存会话重启后无法安全续聊,即使没有定时任务日志;无任务归属和过渡锁时可主动 /clear 开启新会话,旧历史和未确认凭据保留,线程删除仍受限制;未加载的 AGY 仍有任务归属记录时,切换后端也无法清空或改目录,需使用新线程。"},{"topic":"native-schedules","title":"定时任务","text":"新建 DSH 任务记录准确的原会话归属,创建前启动失败不再误封续聊,不阻塞无关的新会话;旧记录缺少归属时仍保守拒绝,请勿删除未确认凭据。"}],"details":"### Changed\n- Remove automatic schedule restoration and the cancelled recovery experiment: HTTP admission server, durable journals, DSH controller, recovery capability flags and startup reconstruction. Native schedules run in the live original conversation; host loss or restart marks unfinished work interrupted without replay.\n- Keep shutdown and updates free of schedule handoff, model/RPC checkpointing and result draining. Idle future definitions do not indefinitely block updates; active work, native mutations and pending results retain their safety gates.\n- Preserve catalog versions 1–6, exact cancellation and cleanup, history purge selectors, outbox acknowledgements, per-thread isolation and original native histories. Legacy ownership metadata authorizes cleanup only; unsettled queued native work still blocks unsafe resume. Historical AGY/DSH cleanup without a supported management route no longer consumes live quota. Persist exact DSH session attribution before CREATE, including ambiguous failures, without fencing unrelated fresh sessions.\n- Saved AGY ACP chat remains non-resumable even without a schedule-owner journal. Explicit `/clear` may detach an owner-free selection while retaining native history and unconfirmed-retirement evidence; thread data erasure remains blocked. No automatic reset or old-session execution is authorized.\n- Compact definitively refused DSH creation attempts before the session marker so startup failures do not fence ordinary chat. Inactive AGY owner journals, including retired ones, continue to block thread-wide reset and directory changes across backends; use a new thread.\n- Preserve late CREATE deletion identities during shutdown without waiting for native work, keep original interrupted diagnostics, and load catalog state with older Routers while withholding unsupported result delivery.\n- Preserve the reviewed AGY owned-host retirement ordering and in-turn purge fixes from 1.6.256. Keep the unrelated compact-summary handoff.\n\n### Tests\n- Cover live native scheduling adapters, restart interruption without reconstruction, no exit-time scheduling RPC, legacy catalogs, cancellation/purge/outbox and ordinary chat. Remove tests exclusive to the deleted recovery and exit-handoff implementations; retain lifecycle safety regressions."},{"version":"1.6.256","text":"### 修复 AGY 定时任务清理\n- 任务在首次触发前取消后,可正常删除线程或切换目录;仍会等待原会话进程确认退出,避免误删未完成的状态。\n- 修复 AGY 在聊天过程中清理定时任务时提示忙碌的问题;只清理选中的任务,尚未确认结束的工作继续保留。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"任务在首次触发前取消后,可正常删除线程或切换目录;仍会等待原会话进程确认退出,避免误删未完成的状态。"},{"topic":"native-schedules","title":"定时任务","text":"修复 AGY 在聊天过程中清理定时任务时提示忙碌的问题;只清理选中的任务,尚未确认结束的工作继续保留。"}],"details":"### Fixed\n- Retire the exact owned AGY host before deleting or resetting a thread whose schedules were cancelled before their first possible wake. Directory changes follow the same ordering; unknown predecessors, live siblings, checkpoint transitions, and unconfirmed exits still retain their evidence.\n- Give AGY schedule purge its native management scope during a foreground turn, preserving exact list/kill receipts, request identity, siblings, and unresolved retirement obligations. History-only cleanup does not start native work.\n\n### Tests\n- Add synthetic production runtime and handler/service/provider regressions for retirement ordering, in-turn purge, stale ownership, and isolated cleanup."},{"version":"1.6.255","text":"### 修复 AGY 线程登录\n- 修复命令行已登录 AGY、线程内仍提示认证失败的问题,兼容新版登录文件并保留已有会话和线程本地凭据。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"修复命令行已登录 AGY、线程内仍提示认证失败的问题,兼容新版登录文件并保留已有会话和线程本地凭据。"}],"details":"### Fixed\n- Share AGY's `antigravity-cli/antigravity-oauth-token` login file with per-thread HOME directories, including threads initialized before login. Preserve thread-local credential replacements and private conversation data.\n\n### Tests\n- Add isolated filesystem regressions for native login discovery, later login, refreshed credentials, and local replacement preservation without launching AGY."},{"version":"1.6.254","text":"### 移除实验性常驻宿主模式\n- 移除实验性常驻宿主启动方式,保留普通启动和现有定时任务恢复能力;本次尚未新增直接停止后的恢复方案。","changes":[{"topic":"native-schedules","title":"定时任务","text":"移除实验性常驻宿主启动方式,保留普通启动和现有定时任务恢复能力;本次尚未新增直接停止后的恢复方案。"}],"details":"### Removed\n- Remove experimental retained-host mode, its launch flag, standalone host runtime, supervisor, pinned bundles, and reduced gateway profile. Ordinary startup, shared ownership safeguards, and native schedule recovery remain supported.\n- Remove retained-host configuration checks without adding a migration gate. This release does not add recovery after an abrupt stop without an exit checkpoint."},{"version":"1.6.253","text":"### 创建失败的定时任务自动收起\n- 因时区不匹配等原因、确认尚未创建的失败任务自动移出列表,启动时也会整理已有的同类记录;原请求仍显示失败,不会重复创建。\n- 结果不明的任务、待清理记录和待确认消息继续保留,不会误删正常任务。","changes":[{"topic":"native-schedules","title":"定时任务","text":"因时区不匹配等原因、确认尚未创建的失败任务自动移出列表,启动时也会整理已有的同类记录;原请求仍显示失败,不会重复创建。"},{"topic":"native-schedules","title":"定时任务","text":"结果不明的任务、待清理记录和待确认消息继续保留,不会误删正常任务。"}],"details":"### Fixed\n- Automatically remove failed fresh schedule attempts that the provider definitively refused before native admission, including native timezone mismatch. Compact existing proven refusal rows at startup while retaining owner-bound replay fences and the original failed request response.\n- Preserve ambiguous creations, recovery failures, cleanup obligations, concurrent operations, and pending results. Keep refused records if safe compaction cannot be persisted or replay-fence capacity is exhausted.\n\n### Tests\n- Cover synthetic native timezone refusal, request receipt retries, restart replay denial, startup compaction, cancellation races, retained results, and persistence/capacity failures."},{"version":"1.6.252","text":"### 定时任务失败后的会话恢复\n- 单个任务恢复失败不会误伤尚未开始恢复的同会话任务;新建任务正常交接后仍可恢复或取消,不受旧任务未确认状态影响。\n- 恢复失败的定时任务不再反复重试;等待原生管理操作结束后,可继续使用原会话聊天,保留原有历史。\n- 清理旧任务后,经运行进程核验可在原会话创建新任务,无需重启整台机器;不会重放结果不明的旧任务。\n- 保留迟到结果与待确认消息;仅有失败历史时不再持续阻塞更新和退出,仍在执行的工作继续受到保护。","changes":[{"topic":"native-schedules","title":"定时任务","text":"单个任务恢复失败不会误伤尚未开始恢复的同会话任务;新建任务正常交接后仍可恢复或取消,不受旧任务未确认状态影响。"},{"topic":"native-schedules","title":"定时任务","text":"恢复失败的定时任务不再反复重试;等待原生管理操作结束后,可继续使用原会话聊天,保留原有历史。"},{"topic":"native-schedules","title":"定时任务","text":"清理旧任务后,经运行进程核验可在原会话创建新任务,无需重启整台机器;不会重放结果不明的旧任务。"},{"topic":"native-schedules","title":"定时任务","text":"保留迟到结果与待确认消息;仅有失败历史时不再持续阻塞更新和退出,仍在执行的工作继续受到保护。"}],"details":"### Fixed\n- Quarantine failed Claude schedule restoration and consumed recovery checkpoints without retrying uncertain jobs. Join the exact failed management turn, or recycle an isolated stalled management host while preserving its original native session. Keep admitted work, late receipts and result acknowledgements protected.\n- Allow explicit new schedules in the original session after same-boot host exclusion, including legacy ownership receipts. Record native host identity and preserve dirty predecessor diagnostics separately; new admission does not certify historical task completion or authorize replay.\n- Register response recipients before schedule recovery admission checks so fenced commands receive their response. Failed-only history no longer blocks update or shutdown after live recovery work settles.\n- Preserve clean pending siblings when an earlier restoration still owns thread admission, and retry them after exact settlement subject to current admission checks.\n- Bind recovery and cleanup to the job's ownership incarnation across clean handoffs, while retaining archived predecessor uncertainty for older jobs.\n- Clear the native recovery deadline before persisting successful activation so slow checkpoint writes cannot strand an already recovered job.\n\n### Tests\n- Add public MessageHandler and synthetic native adapter coverage for recovery timeout, late terminal, bounded process recycle, ordinary chat and fresh scheduling in the same session and boot; cover durable results, repeated restart, legacy receipts, process identity and live-owner conflicts."},{"version":"1.6.251","text":"### 附件恢复与定时任务授权修复\n- 修复取消请求与写盘失败同时发生时,客户端重启可能跳过尚未报告的附件错误的问题。\n- 定时任务回合结束后,未执行的操作授权及时失效,避免后续无关回合误用旧删除授权或一直等待。","changes":[{"topic":"incoming-files","title":"文件接收","text":"修复取消请求与写盘失败同时发生时,客户端重启可能跳过尚未报告的附件错误的问题。"},{"topic":"native-schedules","title":"定时任务","text":"定时任务回合结束后,未执行的操作授权及时失效,避免后续无关回合误用旧删除授权或一直等待。"}],"details":"### Fixed\n- Preserve unreported attachment failures across cancellation, interrupted reporting and persistence errors instead of treating an unfinished report as acknowledged after restart.\n- Retire uninvoked native scheduling authorizations when their exact invocation ends, including autonomous scheduled work. Keep live-turn tool discovery independent from result deadlines and preserve ownership of already-invoked mutations and late receipts.\n\n### Tests\n- Add regressions for cancellation after attachment metadata publication with failed rollback, and for stale deletion authorization surviving a completed scheduled invocation into an unrelated foreground turn."},{"version":"1.6.250","text":"### 定时任务查询保护\n- 查询列表不再触发任务删除;核验超时或失败时保留原任务状态,避免等待中的任务意外失效。\n- 调整原生工具的等待计时,避免模型思考或查找工具超过一分钟后,原本要求的工具调用反而被拒绝。","changes":[{"topic":"native-schedules","title":"定时任务","text":"查询列表不再触发任务删除;核验超时或失败时保留原任务状态,避免等待中的任务意外失效。"},{"topic":"native-schedules","title":"定时任务","text":"调整原生工具的等待计时,避免模型思考或查找工具超过一分钟后,原本要求的工具调用反而被拒绝。"}],"details":"### Fixed\n- Keep schedule listing observational: inventory errors preserve active task state and admission, unresolved records never trigger automatic cleanup, and list receipts reject unexpected native mutations. Verified native absence remains distinct from execution completion.\n- Separate current-turn native invocation waiting from receipt deadlines so model and tool-discovery delays do not expire an uninvoked action. Preserve bounded native-result and out-of-turn management waits and retire actions on turn end, local errors, timeouts, abort, or owner loss without discarding uncertain mutation ownership.\n\n### Tests\n- Cover read-only listing through slash commands and managed tools, inventory uncertainty and absence, pending cleanup, delayed native invocation, result deadlines, foreground errors without native result frames, and late-receipt isolation with synthetic fixtures.\n- Isolate recovery catalog-lock release/reacquisition tests in the existing fork pool to prevent inherited descriptors from transiently retaining a released lock during concurrent test-worker startup."},{"version":"1.6.249","text":"### 附件失败恢复\n- 超限或接收失败的附件报错后,不再反复影响后续普通聊天,客户端重启后也会记住处理状态;明确引用失败文件时仍提示重新上传。","changes":[{"topic":"incoming-files","title":"文件接收","text":"超限或接收失败的附件报错后,不再反复影响后续普通聊天,客户端重启后也会记住处理状态;明确引用失败文件时仍提示重新上传。"}],"details":"### Fixed\n- Persist consumption of reported attachment failures so oversized or rejected files do not block later ordinary messages after a client restart. Preserve the first associated command's error and explicit-reference rejection.\n\n### Tests\n- Cover failure reporting, inbox recreation, explicit rejected references, and subsequent ordinary-message execution with isolated attachment fixtures."},{"version":"1.6.248","text":"### 定时任务升级连续性与失败保护\n- 定时任务交接失败后,其他线程可继续聊天;受影响线程仍保留保护,后续升级会重新检查是否就绪,不会重复未确认的交接。\n- 升级日志区分准备与安装,准备失败不会执行安装;已安装成功的同一版本不因收尾失败而重复安装。\n- 新增需单独配置的实验模式:新建会话的定时任务保留在独立宿主,前端更新交接不调用模型;不自动迁移旧会话,也不保证宿主崩溃后续跑。\n- 实验模式下,任务及结果已处理完毕后可正常关闭宿主;无法确认进程退出时保留任务记录与重试保护。","changes":[{"topic":"native-schedules","title":"定时任务","text":"定时任务交接失败后,其他线程可继续聊天;受影响线程仍保留保护,后续升级会重新检查是否就绪,不会重复未确认的交接。"},{"topic":"native-schedules","title":"定时任务","text":"升级日志区分准备与安装,准备失败不会执行安装;已安装成功的同一版本不因收尾失败而重复安装。"},{"topic":"native-schedules","title":"定时任务","text":"新增需单独配置的实验模式:新建会话的定时任务保留在独立宿主,前端更新交接不调用模型;不自动迁移旧会话,也不保证宿主崩溃后续跑。"},{"topic":"native-schedules","title":"定时任务","text":"实验模式下,任务及结果已处理完毕后可正常关闭宿主;无法确认进程退出时保留任务记录与重试保护。"}],"details":"### Fixed\n- Separate automatic-update preparation from installation in logs. Failed finalization releases global update admission while preserving affected schedule-thread fences; unrelated chat remains available, and retries check readiness without replaying uncertain handoff operations or starting model-mediated recovery.\n- Remember successful package installation across finalization failures so retries do not reinstall the same version. Installation and restart still require confirmed preparation.\n- Separate drained-host retirement admission from native exit proof. Explicit stop joins original executor groups, persists late callbacks and releases ownership only after confirmation; failed exits retain the same handles for retry.\n\n### Added\n- Add an opt-in retained native host with a separately updated command frontend, authenticated local epochs, durable operation receipts, scheduled result delivery and single-writer storage. Frontend replacement keeps the original host and does not invoke native schedule management. Existing monolithic sessions are not imported; the opt-in command profile and host failure/restart limitations are explicit.\n- Connect private retained-host launch records to verified immutable runtime bundles and independently named Linux/macOS service supervisors. Reusing a running owner does not restart it; uncertain or previously stopped owners require reconciliation. Windows supervision is unsupported. Actual service-manager, package-installation and live Router acceptance remain required before deployment.\n\n### Tests\n- Isolate retained-host and schedule-handler native lock tests in separate test processes, preventing unrelated child creation from transiently inheriting their locks.\n- Verify real Claude/AGY continuity in isolated Linux namespaces with deterministic loopback providers: stable native identities, once/cron execution across frontend replacement, ACK replay without execution replay, and zero inference or management calls during replacement and drained-host stop. This does not verify live services or macOS/Windows.\n- Align the legacy Claude installer-failure regression with retained thread fences and assert no recovery requests after failure or reconnect."},{"version":"1.6.247","text":"### 会话关闭修复\n- 修复线程恢复记录异常时可能阻断正常关闭的问题;仍需确认原进程退出,异常会话继续禁止执行并保留原数据。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"修复线程恢复记录异常时可能阻断正常关闭的问题;仍需确认原进程退出,异常会话继续禁止执行并保留原数据。"}],"details":"### Fixed\n- Retire existing AGY hosts during shutdown even when a thread's reset generation is corrupt or unreadable. Use stored backend summaries only for teardown; retain execution admission checks, original context data and the requirement to confirm host retirement before schedule catalog cleanup.\n\n### Tests\n- Await asynchronous AGY context reset in backend-isolation fixtures and complete discovery/shutdown test doubles. Cover corrupt-generation shutdown and unconfirmed AGY exit without weakening lifecycle guards. Join schedule recovery and durable ACK settlement before reading the catalog in restart fixtures, avoiding concurrent readers during Windows file replacement."},{"version":"1.6.246","text":"### AGY 原生定时任务与会话保护\n- 中止、切换模型或进程异常后,下一条命令会等待旧进程确认关闭,避免新旧进程同时使用同一会话。\n- 无法确认退出时保留会话并暂停新执行,可重试 /abort;清空会话和删除线程数据也会先等待退出。\n- 新的 AGY 会话可通过 /schedule 或对话工具创建原生定时任务,结果回到原线程;旧会话保留上下文,不自动迁移,也不按 AGY 版本号限制。\n- AGY 尚未到首次触发时间的安全任务可在中止当前请求或正常重启后自动续跑,保留原会话;到期、取消或状态不明的任务不会自动重放。\n- 加强 AGY 结果归属与取消后的任务检查;有安全检查点的无任务会话可直接恢复,无法确认旧提醒状态的历史会话仍保留兼容聊天方式。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"中止、切换模型或进程异常后,下一条命令会等待旧进程确认关闭,避免新旧进程同时使用同一会话。"},{"topic":"agy-session","title":"AGY 会话","text":"无法确认退出时保留会话并暂停新执行,可重试 /abort;清空会话和删除线程数据也会先等待退出。"},{"topic":"native-schedules","title":"定时任务","text":"新的 AGY 会话可通过 /schedule 或对话工具创建原生定时任务,结果回到原线程;旧会话保留上下文,不自动迁移,也不按 AGY 版本号限制。"},{"topic":"native-schedules","title":"定时任务","text":"AGY 尚未到首次触发时间的安全任务可在中止当前请求或正常重启后自动续跑,保留原会话;到期、取消或状态不明的任务不会自动重放。"},{"topic":"native-schedules","title":"定时任务","text":"加强 AGY 结果归属与取消后的任务检查;有安全检查点的无任务会话可直接恢复,无法确认旧提醒状态的历史会话仍保留兼容聊天方式。"}],"details":"### Added\n- Add a reusable original-session AGY ACP schedule host/provider and authenticated hook/transcript bridge. Join native tool-step receipts, SYSTEM sender provenance and native Stop batches; bound canonical native transcript reads and preserve user hook groups. Native AGY owns once/cron timing and inference.\n- Carry AGY identities through the existing schedule catalog, durable outbox, result ACKs and Router cards. Isolated Linux acceptance exercises the compiled adapter with real native timers and a deterministic loopback provider; external delivery is mocked. Fresh production AGY sessions now use this ACP path through the executor factory, MessageHandler commands and session-scoped MCP scheduling tools. Saved stream-json sessions remain compatible without silent migration. No AGY version restriction or client timer fallback is used.\n\n- Register AGY managed tools with standard ACP session-scoped MCP servers. Preserve user hook configuration in a private HOME overlay; retire the exact host group before catalog shutdown. Completed one-shots do not start cleanup inference from a terminal callback, and inactive-thread deletion checks retained AGY ownership. Explicit context reset after confirmed retirement discards, rather than replays, old work.\n\n### Fixed\n- Require matched native invocation start/completion evidence and stable completed output before settling an AGY batch. Recheck each new wake and management receipt against current ownership while retaining already admitted late results after cancellation; native execution counters are not treated as globally unique IDs.\n- Fence AGY successor prompts on the previous host's confirmed transport close, including abort, unexpected exit and model/effort recycling. A bounded exit timeout retains the original conversation and blocks execution until explicit retirement is confirmed; signalling a process is not completion evidence.\n- Join AGY shutdown before context reset, managed-tool reconfiguration or thread-data removal. Invalidate prompts waiting on a retired context and report stream-json abort's loss of session-only timers explicitly.\n- Add deadline-bounded original-conversation AGY continuation after foreground cancellation and orderly restart/update recovery through the shared catalog. Persist and exclusively consume clean handoff proof before loading; preserve exact task ownership and outbox identities across native definition rebinding. Exact cancellation before any possible first wake can retire an individual task, preserving sibling recovery and allowing clean chat restoration after all tasks are cancelled. Unknown queued work, dirty exits, expired one-shots and cancelled jobs are not replayed.\n- Restore checkpointed no-job AGY conversations on ACP without resetting their context. Uninstrumented saved stream-json sessions remain compatible and refuse unsafe migration before inference. Ordinary no-job abort/settings behavior is preserved."},{"version":"1.6.245","text":"### 定时任务残留清理\n- 已删除历史却仍显示清理未确认的记录,现在可以明确请求忘记选中的残留追踪;不会误报原生任务已删除,也不会恢复已删除任务。\n- 修复能够确认尚未提交原生创建的失败任务仍留下无法收尾记录的问题;正在执行或清理尚未确认的任务继续受到保护。","changes":[{"topic":"native-schedules","title":"定时任务","text":"已删除历史却仍显示清理未确认的记录,现在可以明确请求忘记选中的残留追踪;不会误报原生任务已删除,也不会恢复已删除任务。"},{"topic":"native-schedules","title":"定时任务","text":"修复能够确认尚未提交原生创建的失败任务仍留下无法收尾记录的问题;正在执行或清理尚未确认的任务继续受到保护。"}],"details":"### Fixed\n- Record verified pre-dispatch native schedule refusals so failed creation can be purged without leaving an unresolvable cleanup obligation. Preserve uncertainty after native admission or mutation.\n- Add exact-ID `forgetUnresolved: true` and `/schedule purge <managed-id,...> --forget-unresolved` for user-requested erasure of cleanup tracking whose history was already purged. Preserve durable replay fences, ownership, pending-work guards, and native-absence warnings; never invoke native tools or claim native deletion when forgetting metadata."},{"version":"1.6.244","text":"### 旧定时任务历史删除\n- 缺少旧会话归属的历史记录现在也能按请求删除,连同尚未发送的结果一起清理,不再无限等待原生任务核验。\n- 历史删除与原生任务清理分别报告;未能确认清理的原生任务保留最小追踪信息,可在列表查看并重试,不会误报全部清理完成。\n- 保留正在执行和发送中的任务保护,重启后不会恢复已删除历史;新清理追踪格式需客户端 1.6.244 或更新版本读取。","changes":[{"topic":"native-schedules","title":"定时任务","text":"缺少旧会话归属的历史记录现在也能按请求删除,连同尚未发送的结果一起清理,不再无限等待原生任务核验。"},{"topic":"native-schedules","title":"定时任务","text":"历史删除与原生任务清理分别报告;未能确认清理的原生任务保留最小追踪信息,可在列表查看并重试,不会误报全部清理完成。"},{"topic":"native-schedules","title":"定时任务","text":"保留正在执行和发送中的任务保护,重启后不会恢复已删除历史;新清理追踪格式需客户端 1.6.244 或更新版本读取。"}],"details":"### Fixed\n- Delete selected owned schedule history and queued results even when legacy native attribution is missing. History removal and unresolved native cleanup are separate results; running work, pending operations, in-flight delivery, owner generations, and sibling schedules remain protected.\n- Persist a bounded deletion-only cleanup ledger, durable request selections and permanent replay fences atomically with history removal (catalog format 5, requiring CLI 1.6.244 or newer while cleanup entries or request receipts are present). Keep no prompt/output text or execution-recovery permission. List remaining obligations and retry them through the existing purge command/tool; exact attributed Claude selectors retain prompt digests for deletion and fresh absence verification in the original bound session.\n- Keep deletion-only cleanup visible and retriable for the same authenticated user/thread across context generations without changing original provenance or live-record isolation. Avoid blocking DSH context reset where no supported cleanup route depends on retaining that session.\n- Preserve explicit native-cleanup limitations for missing session attribution, unconfirmed predecessors and unsupported backend capabilities. An empty unrelated session never proves global absence; Router upgrades alone do not change CLI cleanup behavior."},{"version":"1.6.243","text":"### 定时任务历史清理修复\n- 修复原生任务已删除后,历史清理仍缺少核验入口的问题;可核实原会话归属且确认旧执行已结束的记录,现在能够清理。\n- 保存已确认的取消与执行结束结果,避免重启客户端后再次丢失清理依据;保存后需使用 1.6.243 或更新版本读取。\n- 对缺少归属信息或无法确认旧执行已结束的任务,明确说明未完成原因;不会把当前会话的空列表当成所有旧任务已清除。","changes":[{"topic":"native-schedules","title":"定时任务","text":"修复原生任务已删除后,历史清理仍缺少核验入口的问题;可核实原会话归属且确认旧执行已结束的记录,现在能够清理。"},{"topic":"native-schedules","title":"定时任务","text":"保存已确认的取消与执行结束结果,避免重启客户端后再次丢失清理依据;保存后需使用 1.6.243 或更新版本读取。"},{"topic":"native-schedules","title":"定时任务","text":"对缺少归属信息或无法确认旧执行已结束的任务,明确说明未完成原因;不会把当前会话的空列表当成所有旧任务已清除。"}],"details":"### Fixed\n- Wire production history purge to fresh original-session Claude inventory under the existing cleanup lease. Exact saved session, working directory, thread and marker attribution plus framework-confirmed predecessor retirement permit removal after reviewed native deletion, without requiring execution-recovery model metadata or recreating tasks.\n- Persist confirmed native cancellation and execution retirement for Claude and DSH so later history purge can survive a CLI restart. This optional cleanup receipt uses catalog format 4, never grants execution admission, and requires CLI 1.6.243 or newer to read while present.\n- Report missing attribution and uncertain predecessor work separately from native presence. Empty inventory in another session does not erase legacy history; unresolved cancellation tracking and sibling schedules remain intact."},{"version":"1.6.242","text":"### 定时任务删除与历史清理\n- 请求清理后,助手可直接检查并删除选中的原生任务,不再要求你复制确认命令;仍核验任务归属和删除结果。\n- 新增 /schedule purge,可取消选中的托管任务并移除确认清理完成的历史记录;未完成的清理会逐项说明,不会仅清空列表就报成功。清理后的目录格式不支持旧版客户端读取。\n- 修复原生列表查询超时后残留授权、反复积累导致后续查询受阻的问题;超时提示会区分调用和回执阶段,删除结果未知时不误报成功。","changes":[{"topic":"native-schedules","title":"定时任务","text":"请求清理后,助手可直接检查并删除选中的原生任务,不再要求你复制确认命令;仍核验任务归属和删除结果。"},{"topic":"native-schedules","title":"定时任务","text":"新增 /schedule purge,可取消选中的托管任务并移除确认清理完成的历史记录;未完成的清理会逐项说明,不会仅清空列表就报成功。清理后的目录格式不支持旧版客户端读取。"},{"topic":"native-schedules","title":"定时任务","text":"修复原生列表查询超时后残留授权、反复积累导致后续查询受阻的问题;超时提示会区分调用和回执阶段,删除结果未知时不误报成功。"}],"details":"### Changed\n- Permit scoped agent tools to execute reviewed native schedule deletion without a separate owner-text confirmation. Preserve exact inventory, owner/session, expiry, sibling and native-action receipt checks; keep the existing text command compatible.\n- Add managed schedule purge tools and commands: cancel first, remove only verified retired history and queued output, and report pending cleanup per task. Persist bounded ID/owner replay fences in catalog format 3; older format-2 clients cannot downgrade this catalog.\n\n### Fixed\n- Release expired native CronList read authorizations to prevent capacity exhaustion after repeated missing receipts. Report the stalled timeout stage without implying that an inventory read created a task; retain uncertain mutation receipts for reconciliation."},{"version":"1.6.241","text":"### 会话恢复与任务收尾\n- 新增 /schedule cleanup review:可在原会话查看旧任务并亲自确认删除选中的原生任务,不再依赖缺失的历史托管信息;仅确认当前会话的定义已删除,不误报旧进程已停止,无法确认会话归属的任务仍会明确阻止。\n- 恢复 Claude 会话时会先检查并拦截无法确认归属的旧任务,避免仅隐藏输出却继续运行;归属可验证的任务仍可恢复,历史任务的删除仍需核实,不会批量删除其他任务。 启动时先等待保护就绪,不能承接定时任务的会话、委派进程和压缩进程会禁用原生定时执行。\n- 托管任务中断或请求取消后,即使清理失败也会拦截后续执行,已开始的结果仍可回传;修复一次性任务因原生列表省略字段而无法删除的问题。\n- 子任务成果尚未处理完时,主任务会在原会话继续收尾,不再仅因超过两轮就失败,也不会重复执行已完成的子任务或重新发送原附件。\n- 多次收尾仍无进展时会逐步放缓重试;可用 /abort 停止,清理会话或关闭客户端也会取消等待,未解决的成果仍会保留。","changes":[{"topic":"native-schedules","title":"定时任务","text":"新增 /schedule cleanup review:可在原会话查看旧任务并亲自确认删除选中的原生任务,不再依赖缺失的历史托管信息;仅确认当前会话的定义已删除,不误报旧进程已停止,无法确认会话归属的任务仍会明确阻止。"},{"topic":"native-schedules","title":"定时任务","text":"恢复 Claude 会话时会先检查并拦截无法确认归属的旧任务,避免仅隐藏输出却继续运行;归属可验证的任务仍可恢复,历史任务的删除仍需核实,不会批量删除其他任务。 启动时先等待保护就绪,不能承接定时任务的会话、委派进程和压缩进程会禁用原生定时执行。"},{"topic":"native-schedules","title":"定时任务","text":"托管任务中断或请求取消后,即使清理失败也会拦截后续执行,已开始的结果仍可回传;修复一次性任务因原生列表省略字段而无法删除的问题。"},{"topic":"delegation","title":"委派任务","text":"子任务成果尚未处理完时,主任务会在原会话继续收尾,不再仅因超过两轮就失败,也不会重复执行已完成的子任务或重新发送原附件。"},{"topic":"delegation","title":"委派任务","text":"多次收尾仍无进展时会逐步放缓重试;可用 /abort 停止,清理会话或关闭客户端也会取消等待,未解决的成果仍会保留。"}],"details":"### Fixed\n- Add explicit `/schedule cleanup review` and owner text confirmation for exact session-only Claude Cron definitions, including legacy/native-only tasks without managed recovery metadata. Bind short-lived reviews to owner, connection and native host/session, verify full structured inventory before and after deletion, reconcile lost receipts only from fresh absence, and preserve unknown predecessor status. Project-persisted definitions without session attribution remain blocked. Expose review through managed scheduling tools without a model confirmation endpoint.\n- Check live managed admission at every Claude wake, including recovered jobs. Interrupted, cancelled, faulted or retired owners cannot admit new occurrences even when native cleanup fails; preserve already-admitted completion callbacks and independent sibling jobs.\n- Accept omitted native CronList recurrence for one-shot cancellation while rejecting malformed values and preserving exact definition and ownership checks.\n- Hold scheduling-enabled Claude startup with the native `--await-initialize` barrier before restored timers can run. Disable native Cron per process for non-owning foreground hosts, restricted hosts, delegated workers and external compaction; the previous settings flag did not suppress restored execution. Preserve owned adoption, delivery and exact cancellation without changing native timers.\n- Guard resumed foreground Claude schedules before chat independently of managed-tool registration. Verify callback-hook policy, reject unowned restored wakeups before inference, and preserve exact-owned adoption and delivery. Do not infer scheduler suppression from launch settings, delete unverifiable legacy definitions, or claim already-admitted predecessor work is stopped.\n- Continue unresolved delegated artifact closeout in the original coordinator request/session instead of failing after two rounds. Preserve explicit integration decisions, durable receipt and ancestry checks, worker-launch/tool-call admission limits, and existing backend failure handling; do not replay completed workers or original attachments.\n- Pace repeated unresolved closeout with a 1–30 second capped backoff. Cancel waits on abort, conversation retirement, or shutdown, retain request/queue ownership, and recheck durable disposition before another model turn.\n\n### Tests\n- Cover reviewed cleanup authorization, stale inventories and hosts, partial/error-after-commit retries, missing/foreign ownership receipts, sibling callbacks, catalog attribution and authenticated command/tool routing. Isolated Linux native acceptance verifies exact deletion and absence after a second resume while unknown scheduled wakes make no inference requests.\n- Cover continuation beyond two rounds, capped pacing and timer cleanup, cancellation during waits, model/compaction retries, unchanged admission limits, and pending/unavailable artifact preservation with synthetic executors and real Git fixtures."},{"version":"1.6.240","text":"### 清理中断的定时任务\n- 中断的 Claude 任务在原会话和归属信息可验证时,可检查并删除原生已有定义,不再因丢失运行句柄而无法清理,也不会重建任务或补跑。\n- 取消请求会保留;旧任务缺少归属证据,或同次开机内旧进程的工作仍无法确认时,会明确报告清理未完全确认,不再误报取消成功。请使用完整托管任务 ID,不要重复创建。","changes":[{"topic":"native-schedules","title":"定时任务","text":"中断的 Claude 任务在原会话和归属信息可验证时,可检查并删除原生已有定义,不再因丢失运行句柄而无法清理,也不会重建任务或补跑。"},{"topic":"native-schedules","title":"定时任务","text":"取消请求会保留;旧任务缺少归属证据,或同次开机内旧进程的工作仍无法确认时,会明确报告清理未完全确认,不再误报取消成功。请使用完整托管任务 ID,不要重复创建。"}],"details":"### Fixed\n- Route interrupted Claude schedule cancellation through a removal-only native inventory operation when the live handle is gone. Require the original session/model, durable ownership evidence, exact native ID, full marked prompt and rule before deleting; verify absence afterward without creating or admitting work.\n- Preserve cancellation intent and report partial cleanup when a same-boot predecessor remains unconfirmed. Legacy records without ownership evidence now fail explicitly instead of returning an unchanged interrupted record as a successful cancellation. Direct unscoped native deletion remains denied.\n\n### Tests\n- Cover scoped inventory/deletion receipts, mismatched ownership, expired one-shots, stale and late replies, repeated cancellation, sibling execution, predecessor fences and cancellation tombstones using isolated synthetic protocol fixtures."},{"version":"1.6.239","text":"### 按实际能力支持 Claude\n- Claude 恢复时优先接续原生已有任务,避免重复创建;新建周期任务在确认同一电脑已重新启动后可恢复后续触发,不补跑未知结果。同次开机内强制终止 CLI、原生任务无故缺失或一次性任务结果不明时仍会暂停恢复。\n- 不再仅允许指定 Claude 版本或架构恢复定时任务;实际具备所需能力的新版本和 ARM64 会话也可进行有序恢复,已开始的工作仍须完成,结果不明确时继续阻止恢复。\n- 原会话模型切换和保留会话的取消操作改为检查实际控制能力与回执,不再因版本号或架构不同直接拒绝;未确认的操作不会误报成功。\n- Linux 托管服务停止时先通知 CLI 完成交接,结果确认结束后再断开连接,避免提前结束原生进程;旧版生成的服务单元会在明确的服务操作前迁移,自定义配置需人工检查,超时或清理失败不会误报安全恢复。","changes":[{"topic":"native-schedules","title":"定时任务","text":"Claude 恢复时优先接续原生已有任务,避免重复创建;新建周期任务在确认同一电脑已重新启动后可恢复后续触发,不补跑未知结果。同次开机内强制终止 CLI、原生任务无故缺失或一次性任务结果不明时仍会暂停恢复。"},{"topic":"native-schedules","title":"定时任务","text":"不再仅允许指定 Claude 版本或架构恢复定时任务;实际具备所需能力的新版本和 ARM64 会话也可进行有序恢复,已开始的工作仍须完成,结果不明确时继续阻止恢复。"},{"topic":"model-selection","title":"模型切换","text":"原会话模型切换和保留会话的取消操作改为检查实际控制能力与回执,不再因版本号或架构不同直接拒绝;未确认的操作不会误报成功。"},{"topic":"native-schedules","title":"定时任务","text":"Linux 托管服务停止时先通知 CLI 完成交接,结果确认结束后再断开连接,避免提前结束原生进程;旧版生成的服务单元会在明确的服务操作前迁移,自定义配置需人工检查,超时或清理失败不会误报安全恢复。"}],"details":"### Fixed\n- Require exact boolean recurrence evidence when adopting native Claude schedules. On handoff-completion retries, publish the durable clean ownership receipt only after the captured host's drained EOF exit; a successful exit before that boundary is insufficient.\n- Reconcile Claude schedules against structured native CronList receipts, adopting exact owned definitions without duplicate creation. New recurring jobs may resume future firings after verified same-machine reboot using durable session ownership and exclusive catalog/host locks. Same-boot crashes, unknown predecessors, unexplained native absence and uncertain one-shots remain blocked; cancellation tombstones and the existing orderly path are preserved.\n- Give the CLI main process the first systemd stop signal with `KillMode=mixed` and an explicit 90-second supervisor timeout. Migrate only recognized generated legacy units before explicit service operations, verify effective overrides, preserve custom units, and report failed/timed-out stops without removing the unit.\n- Keep the Router connection available until native shutdown handoff and result acknowledgement settle; disconnect afterward, preserving cleanup errors and idempotent shutdown.\n- Remove exact Claude version, OS and architecture allowlists from native model control, retained-process interruption and orderly schedule recovery. Use actual initialized process/session identity, native tools/hooks/lifecycle capabilities and correlated receipts instead; newer capable ARM64 hosts are no longer excluded solely by their build or architecture.\n- Preserve restricted/worker recovery exclusions, uncertain-outcome fences, admitted-work drain, background inventory and confirmed predecessor exit. Missing protocol evidence never authorizes automatic recreation or false success.\n\n### Tests\n- Cover newer ARM64 and simulated macOS/Windows protocol branches, absent version metadata, missing lifecycle capabilities, changed process/session identity and original-session recovery. These synthetic tests do not establish native support on every OS or Claude release."},{"version":"1.6.238","text":"### 定时任务恢复与模型切换\n- 取消意图会先保存,避免清理回执丢失后误恢复;恢复过程不会自动补跑过期的一次性任务或执行结果未知的任务;Claude 已取消或拒绝的执行不会因后续成功回执被误报成功。\n- 新建 DSH 任务及 Linux x64 上 Claude 2.1.311 的托管定时任务可在确认有序退出后自动恢复,无需打开原会话;等待中的可恢复任务不再一直阻止自动升级,安装失败也会尝试恢复。\n- Claude 已触发但尚未获准执行的任务可在升级时跳过,不会误报成功或补跑;已开始的执行仍须完成,后台工作或退出结果不明时会暂缓升级;异常崩溃后的自动重建暂不支持。\n- 升级后的安全恢复若只是在等待 Router 重连,会在连接恢复后继续;不会在安装尚未结束时提前启动任务。\n- Linux x64 的 Claude 2.1.311 可在原进程内切换模型并保留后续定时任务;其他运行中的版本或平台会明确拒绝,不再为切换模型自动停止进程。\n- 切换及自动恢复的模型回执不明确时会暂缓新任务,不保存未确认选项;清理其他任务不会提前解除等待;有定时任务时会拒绝需要重启的思考强度调整,避免意外丢失任务。","changes":[{"topic":"native-schedules","title":"定时任务","text":"取消意图会先保存,避免清理回执丢失后误恢复;恢复过程不会自动补跑过期的一次性任务或执行结果未知的任务;Claude 已取消或拒绝的执行不会因后续成功回执被误报成功。"},{"topic":"native-schedules","title":"定时任务","text":"新建 DSH 任务及 Linux x64 上 Claude 2.1.311 的托管定时任务可在确认有序退出后自动恢复,无需打开原会话;等待中的可恢复任务不再一直阻止自动升级,安装失败也会尝试恢复。"},{"topic":"native-schedules","title":"定时任务","text":"Claude 已触发但尚未获准执行的任务可在升级时跳过,不会误报成功或补跑;已开始的执行仍须完成,后台工作或退出结果不明时会暂缓升级;异常崩溃后的自动重建暂不支持。"},{"topic":"native-schedules","title":"定时任务","text":"升级后的安全恢复若只是在等待 Router 重连,会在连接恢复后继续;不会在安装尚未结束时提前启动任务。"},{"topic":"model-selection","title":"模型切换","text":"Linux x64 的 Claude 2.1.311 可在原进程内切换模型并保留后续定时任务;其他运行中的版本或平台会明确拒绝,不再为切换模型自动停止进程。"},{"topic":"model-selection","title":"模型切换","text":"切换及自动恢复的模型回执不明确时会暂缓新任务,不保存未确认选项;清理其他任务不会提前解除等待;有定时任务时会拒绝需要重启的思考强度调整,避免意外丢失任务。"}],"details":"### Tests\n- Verify Claude model switching with the real isolated Linux 2.1.311 host and a loopback fake provider, including autonomous timing and late acknowledgement. Add a regression for a resumed unowned wake whose blocked hook still produces a successful native terminal; this is not schedule recovery proof.\n\n### Added\n- Add a versioned provider-neutral schedule recovery contract for authoritative persistent reattachment or predecessor-fenced reconstruction. Persist execution intent, cancellation intent and bounded occurrence deduplication; reconcile eligible records after Router readiness without a foreground message.\n- Require original owner/backend/directory admission, serialize recovery and retain ambiguous native receipts. Expired one-shots and crash-interrupted executions are not replayed. Legacy terminal records remain terminal.\n- Add an explicit provider-neutral skip-unadmitted handoff policy. Claude 2.1.311 on Linux x64 fences UserPromptSubmit admission, skips pending occurrences without replay or successful delivery, drains admitted work/background tasks, verifies owned native deletion and joins a no-escalation EOF exit. Persist stable ownership before CREATE and verify native inventory in the original session before reconstruction.\n\n### Changed\n- Use acknowledged native `set_model` for live Claude 2.1.311 sessions on Linux x64, retaining process/session/managed-tool registration and future jobs. Support native default and card/global reset semantics; cold selection does not spawn a host. Other live builds/platforms refuse the change without a destructive fallback.\n- Fence model-control uncertainty, bind receipts to the captured host/session, and keep timed-out preferences unsaved even on late acknowledgement. Allow only explicit same-host retries after settled internal errors; retain destructive context reset as an explicit recovery option. Refuse restart-based effort changes while managed native schedules exist.\n- Enable DSH orderly recovery through native serialized deletion, queued-turn drain, session flush and confirmed owned-host exit. Resume the original session automatically after Router readiness and reconstruct only future firings from a consumed durable clean checkpoint.\n- Prepare native handoff before automatic installation; restore suspended jobs after failed installation or manual install-only updates. Waiting eligible Claude and DSH jobs no longer block updates indefinitely; uncertain drain/exit/restoration retains admission and never silently force-stops work.\n\n### Fixed\n- Require a completed Claude scheduled lifecycle as well as a successful result before reporting occurrence success; cancelled, discarded or refused terminals cannot be overwritten by late success receipts.\n- Do not reconstruct a one-shot already absent at handoff, or block the next foreground turn when every cleanly suspended one-shot is skipped or expires.\n- Validate the exact model acknowledgement during Claude recovery, retain cleanup handles for post-create failures, and scope admission release to its restoration owner. Finalize terminal-only update handoffs and describe the negotiated recovery policy in creation responses.\n- Fence automatic updates while startup catalog inspection/reconciliation is unresolved, including malformed catalogs. Persist cancellation intent before native deletion so a failed receipt cannot authorize later recreation.\n- Distinguish clean native quiescence from deletion evidence when cancelling or expiring persistent schedules. Resume clean update restoration on Router reconnect only after installation finalization; reject update admission on destroyed handlers.\n\n### Limitations\n- Dirty-crash reconstruction remains unsupported. Claude orderly recovery is gated to Linux x64 Claude Code 2.1.311; isolated real-native acceptance uses a loopback fake API and native Cron timing, not authenticated provider traffic. No macOS/Windows native Claude recovery claim is made. DSH retains its stricter drain policy. Retained-process `/abort` and model switching remain supported."},{"version":"1.6.237","text":"### 取消当前任务并保留后续定时任务\n- Claude 启动中的请求也可取消,旧请求和输入等待不再影响下一轮;停止结果不确定时会阻止新任务,并提示重试 /abort。\n- 取消聊天时刚创建成功的定时任务会保留清理状态;无法安全清理时可通过 /schedule list 查看并重试取消,避免重复创建。\n- Linux x64 上已验证的 Claude 2.1.311 可在 /abort 后保留会话和后续定时任务;已触发的任务仍可能被一起打断,其他版本或平台继续使用停止进程的方式。\n- 清理未确认时可重试 /abort;若选择 /clear 或 /new 强制恢复,会停止进程并丢失其中的定时任务,不会悄悄重建任务。","changes":[{"topic":"session-handoff","title":"会话接续","text":"Claude 启动中的请求也可取消,旧请求和输入等待不再影响下一轮;停止结果不确定时会阻止新任务,并提示重试 /abort。"},{"topic":"native-schedules","title":"定时任务","text":"取消聊天时刚创建成功的定时任务会保留清理状态;无法安全清理时可通过 /schedule list 查看并重试取消,避免重复创建。"},{"topic":"native-schedules","title":"定时任务","text":"Linux x64 上已验证的 Claude 2.1.311 可在 /abort 后保留会话和后续定时任务;已触发的任务仍可能被一起打断,其他版本或平台继续使用停止进程的方式。"},{"topic":"session-handoff","title":"会话接续","text":"清理未确认时可重试 /abort;若选择 /clear 或 /new 强制恢复,会停止进程并丢失其中的定时任务,不会悄悄重建任务。"}],"details":"### Changed\n- On Linux x64 with Claude 2.1.311 and verified native capabilities/process identity, interrupt foreground work without restarting Claude or losing future native schedules. Join acknowledgement, input UUID results and lifecycle terminals, retire old interactive authority, and stop only background tasks with observed foreground tool lineage.\n- Reconcile interrupted native CREATE/DELETE mutations under a cancellation-owned lease on the same host. Keep unconfirmed cleanup fenced and retryable with `/abort`; `/clear` provides explicit destructive recovery that loses session-only schedules. Never recreate jobs or claim atomic cancellation of already-fired scheduled work or all external effects.\n\n### Fixed\n- Cancel Claude requests still queued during startup, fence late startup dispatch, and keep uncertain shutdowns blocked until explicit retry confirms process exit. Startup and unsupported native hosts retain the explicit process-stop fallback.\n- Retire interactive input waiters and detection timers on abort, context reset, and destruction so old callbacks cannot change a later turn's input state.\n- Give managed tool activations owner-checked retirement so an older finalizer cannot deactivate a newer turn; keep the Claude endpoint registered across a verified retained abort while preserving deliberate disposal on reset/destroy/backend changes.\n- Reconcile late accepted Claude schedule creation only under fresh owner authority on the existing idle host. Preserve the native handle and a retryable cleanup error when admission is unsafe, without recreating jobs or reviving an expired foreground scope."},{"version":"1.6.236","text":"### 定时与排队卡片更清晰\n- 定时和排队卡片突出任务内容,状态、时间和操作更易读,长任务编号改为次要信息。\n- 统一排队确认、取消和开始执行后的卡片样式,保留原有按钮操作。","changes":[{"topic":"task-cards","title":"任务卡片","text":"定时和排队卡片突出任务内容,状态、时间和操作更易读,长任务编号改为次要信息。"},{"topic":"task-cards","title":"任务卡片","text":"统一排队确认、取消和开始执行后的卡片样式,保留原有按钮操作。"}],"details":"### Changed\n- Refine scheduled-task and queue cards with task-first content, compact status and context, readable timestamps with explicit timezones, and consistent action and receipt layouts.\n- Keep full schedule identifiers in secondary details while preserving existing ownership, confirmation, pagination, and retry controls."},{"version":"1.6.235","text":"### 定时任务沿用当前聊天上下文\n- Claude 和 DSH 定时任务在原聊天会话中执行,可沿用之前的讨论、后续消息和前几次执行的上下文。\n- 取消任务停止后续触发,不结束聊天会话;已经开始的执行仍可返回结果,同时到点的任务可能返回标明来源的合并结果。\n- Claude 周期任务需使用原生会话时区;本机服务重启后仍需重新创建中断的任务。","changes":[{"topic":"native-schedules","title":"定时任务","text":"Claude 和 DSH 定时任务在原聊天会话中执行,可沿用之前的讨论、后续消息和前几次执行的上下文。"},{"topic":"native-schedules","title":"定时任务","text":"取消任务停止后续触发,不结束聊天会话;已经开始的执行仍可返回结果,同时到点的任务可能返回标明来源的合并结果。"},{"topic":"native-schedules","title":"定时任务","text":"Claude 周期任务需使用原生会话时区;本机服务重启后仍需重新创建中断的任务。"}],"details":"### Changed\n- Execute Claude and DSH managed schedules in their original foreground native conversation, preserving earlier discussion, subsequent messages, and recurring-turn history without copying transcripts.\n- Authorize Claude Cron actions in the active model turn, serialize card/slash management on that session, and use native DSH host CRUD with occurrence-aware output routing.\n- Cancel future firings without terminating the shared conversation; retain already-started results and label native combined answers. Process-restart job restoration remains unsupported.\n- Require recurring Claude timing to match the native session timezone and reject ambiguous one-shot clock-rollback times without changing session settings."},{"version":"1.6.234","text":"### 用自然语言创建并管理定时任务\n- 可用自然语言请求 Claude 或 DSH 创建、查看和取消定时任务,无需开启多代理委派;时间或时区不明确时会先澄清。\n- 自然语言操作会单独返回管理卡片,保留助手正常回复;创建较慢时可查询进度,重试同一操作不会重复创建。\n- 耗时操作失败后会补充明确结果;卡片发送失败时可通过 /schedule list 恢复查看,无需重复创建任务。","changes":[{"topic":"native-schedules","title":"定时任务","text":"可用自然语言请求 Claude 或 DSH 创建、查看和取消定时任务,无需开启多代理委派;时间或时区不明确时会先澄清。"},{"topic":"native-schedules","title":"定时任务","text":"自然语言操作会单独返回管理卡片,保留助手正常回复;创建较慢时可查询进度,重试同一操作不会重复创建。"},{"topic":"native-schedules","title":"定时任务","text":"耗时操作失败后会补充明确结果;卡片发送失败时可通过 /schedule list 恢复查看,无需重复创建任务。"}],"details":"### Added\n- Add backend-neutral managed scheduling tools for natural-language creation, listing, cancellation, and bounded operation receipts, independently of delegation settings. Retain Claude and DSH native-provider admission and reject unsupported execution backends explicitly.\n- Deliver model-requested management cards separately from foreground answers with negotiated compatibility, captured ownership, replay fencing, and cleanup of newly created jobs when their turn context retires.\n\n### Fixed\n- Surface terminal failures after pending scheduling receipts, preserve scoped tools across authorized Codex model recovery, and reclaim completed receipt capacity without dropping pending operations."},{"version":"1.6.233","text":"### 在卡片上管理定时任务\n- 创建或查看定时任务后,可直接在卡片上刷新状态、确认取消,无需手动输入任务编号。\n- 取消操作等待本机确认;超时会提示结果未知,避免把仍在运行的任务显示为已取消。\n- 旧版本仍可使用原有命令;未使用定时任务时保持原有聊天流程。","changes":[{"topic":"native-schedules","title":"定时任务","text":"创建或查看定时任务后,可直接在卡片上刷新状态、确认取消,无需手动输入任务编号。"},{"topic":"native-schedules","title":"定时任务","text":"取消操作等待本机确认;超时会提示结果未知,避免把仍在运行的任务显示为已取消。"},{"topic":"native-schedules","title":"定时任务","text":"旧版本仍可使用原有命令;未使用定时任务时保持原有聊天流程。"}],"details":"### Added\n- Add interactive native schedule management cards with on-demand status refresh and confirmed cancellation through the CLI, retaining the original task owner and thread.\n- Negotiate schedule card controls separately, preserve text commands for older peers, and keep scheduling dormant until used.\n\n### Fixed\n- Treat timed-out card operations as unknown outcomes and retain cancellation retry when native process cleanup is unconfirmed."},{"version":"1.6.232","text":"### 定时任务回到原线程\n- 可用 /schedule 创建一次性或周期任务、查看状态和取消;支持具备原生定时能力的 Claude Code 和 DSH。\n- 任务结果回到原线程,断线时保留待投递结果;需保持本机服务运行,重启后未完成任务会标为中断,不自动重建。\n- 可查看全部八个后端的支持情况;暂不支持的后端会说明具体原因,不会自动切换到其他后端执行。\n- 未使用定时任务时不会创建任务数据或启动定时服务,日常聊天和重连保持原有流程。","changes":[{"topic":"native-schedules","title":"定时任务","text":"可用 /schedule 创建一次性或周期任务、查看状态和取消;支持具备原生定时能力的 Claude Code 和 DSH。"},{"topic":"native-schedules","title":"定时任务","text":"任务结果回到原线程,断线时保留待投递结果;需保持本机服务运行,重启后未完成任务会标为中断,不自动重建。"},{"topic":"native-schedules","title":"定时任务","text":"可查看全部八个后端的支持情况;暂不支持的后端会说明具体原因,不会自动切换到其他后端执行。"},{"topic":"native-schedules","title":"定时任务","text":"未使用定时任务时不会创建任务数据或启动定时服务,日常聊天和重连保持原有流程。"}],"details":"### Added\n- Add capability-based `/schedule` commands for native one-shot and recurring Claude and DSH tasks, with an isolated native process per schedule, explicit timezone handling, native create/list/cancel receipts, and lifecycle-correlated completion.\n- Persist task ownership, interrupted state, and bounded pending results; deliver acknowledged result cards to the original thread and retry after reconnect without adding a Router scheduler or model polling.\n- Add DSH native scheduler composition and an ACP event adapter with private job storage, correlated native terminal outcomes, and explicit cleanup. Preserve backend identity through catalog recovery and result delivery.\n- Report explicit scheduling eligibility for all eight backends and return version-specific reasons when native timing or existing-transport result delivery is unavailable. Keep list/cancel available after backend switches, and reject unavailable native capabilities, restricted sandbox configurations, and incompatible Routers explicitly.\n\n### Fixed\n- Keep scheduling initialization and delivery subscriptions dormant when no catalog exists. Recover persisted results after reconnect without creating schedule state for ordinary chat users; serialize first-use and recovery initialization and guard shutdown races.\n- Preserve already completed pending results when native processes report shutdown; distinguish service shutdown from ownership invalidation so offline recurring results can be delivered after restart."},{"version":"1.6.231","text":"### 点取文件即可申请授权\n- 尚未开启文件权限时,也可点击原来的 Get file 按钮发起授权,无需寻找旧提示或另外操作按钮。\n- 授权并重新连接后,可在原回复继续取文件;待处理附件仅临时保留,重启或开始新任务后可能需要重新请求。","changes":[{"topic":"output-files","title":"文件取回","text":"尚未开启文件权限时,也可点击原来的 Get file 按钮发起授权,无需寻找旧提示或另外操作按钮。"},{"topic":"output-files","title":"文件取回","text":"授权并重新连接后,可在原回复继续取文件;待处理附件仅临时保留,重启或开始新任务后可能需要重新请求。"}],"details":"### Added\n- Let the existing inline Get file button request device file approval when approval is missing, without adding a second button. Keep automatic enrollment reminders separate from explicit user requests.\n- Carry only the explicitly selected unverified reply across first-key approval, and prepare bounded process-local attachment intent after authenticated reconnection. Keep stale contexts, unavailable proof, revoked keys, and unknown delivery outcomes held without widening file access."},{"version":"1.6.230","text":"### 附件信息更清爽\n- 附件区去掉重复标题,单页不再显示页码;文件名、大小、状态和有效期分层展示,更容易浏览。","changes":[{"topic":"output-files","title":"文件取回","text":"附件区去掉重复标题,单页不再显示页码;文件名、大小、状态和有效期分层展示,更容易浏览。"}],"details":"### Changed\n- Simplify the inline Files panel to a single heading, show page numbers only for multiple pages, and separate filenames from subdued size, status, and absolute UTC expiry details."},{"version":"1.6.229","text":"### 附件入口更显眼\n- 回复中的文件面板默认展开,显示文件总数,并移到回答下方、线程切换按钮上方,取回和查看进度更方便。\n- 修复同时确认文件授权、手动更换密钥或解绑设备时,较早的授权可能覆盖新状态的问题。\n- 修复前面的失败子任务暂时无法清理时,后面可清理的子任务一直得不到处理的问题。","changes":[{"topic":"output-files","title":"文件取回","text":"回复中的文件面板默认展开,显示文件总数,并移到回答下方、线程切换按钮上方,取回和查看进度更方便。"},{"topic":"output-files","title":"文件取回","text":"修复同时确认文件授权、手动更换密钥或解绑设备时,较早的授权可能覆盖新状态的问题。"},{"topic":"delegation","title":"委派任务","text":"修复前面的失败子任务暂时无法清理时,后面可清理的子任务一直得不到处理的问题。"}],"details":"### Changed\n- Open inline Files panels expanded by default, with a clear heading and total attachment count above completion details and thread controls. Preserve ordering through continuation cards, streaming and selection refreshes, pagination, late offers, and saved-body recovery without changing retrieval authorization or expiry.\n\n### Fixed\n- Serialize automatic file approval, manual key enrollment, and unbinding across binding managers sharing one store, preventing stale approvals from restoring revoked access or overwriting a newer manually approved key.\n- Rotate bounded failed-worker cleanup retries across candidates so persistent safety holds do not indefinitely block later eligible checkouts, while retaining all existing disposal guards."},{"version":"1.6.228","text":"### 后台结束通知不再刷屏\n- Claude Code 和 Codex 的后台任务结束后不再单独弹出通知卡片,主回复、后台执行和必要的授权与输入提示照常保留。","changes":[{"topic":"agent-activity","title":"运行进度","text":"Claude Code 和 Codex 的后台任务结束后不再单独弹出通知卡片,主回复、后台执行和必要的授权与输入提示照常保留。"}],"details":"### Changed\n- Retire standalone native background-task terminal notifications. The CLI stops forwarding Claude Code hooks and Codex completion callbacks, and the Router quietly drops legacy `task_notification` frames without cards, text fallback, reply associations, or task/recipient logging. Legacy notification options cannot restore this presentation.\n- Preserve native background execution, completion consumption and deduplication, main response/tool flow, actionable approvals and input prompts, managed worker progress and closeout, and inline file retrieval. Keep the generic card sender and legacy wire types for their remaining callers and compatibility."},{"version":"1.6.227","text":"### 文件取回留在原回复中\n- 新附件的取回按钮、传输状态和重试入口集中在原助手卡片中,多份文件可翻页查看,避免额外刷出文件卡片。\n- 未启用或尚未获批时显示灰色入口,不读取本地文件;内部导出失败不再单独弹出笼统计数提示。\n- 引导助手把交付文件放在已授权工作区的可见目录,减少因隐藏或未授权位置导致的附件准备失败。","changes":[{"topic":"output-files","title":"文件取回","text":"新附件的取回按钮、传输状态和重试入口集中在原助手卡片中,多份文件可翻页查看,避免额外刷出文件卡片。"},{"topic":"output-files","title":"文件取回","text":"未启用或尚未获批时显示灰色入口,不读取本地文件;内部导出失败不再单独弹出笼统计数提示。"},{"topic":"output-files","title":"文件取回","text":"引导助手把交付文件放在已授权工作区的可见目录,减少因隐藏或未授权位置导致的附件准备失败。"}],"details":"### Changed\n- Show new output files, manual retrieval, transfer state, and valid retries inside the original assistant execution card. Bind controls to its actual final continuation, preserve the full card body through serialized updates, and retain bounded private parent-body receipts for late offers and restart recovery. Paginate file rows without dropping selections.\n- Display negotiated, basename-only unavailable controls when file retrieval is disabled, unapproved, or unsupported, without reading or snapshotting candidate files. Existing approved offline references retain queueing and cached-copy delivery; hints never authorize bytes or prove file existence.\n- Suppress count-only preparation alerts, including legacy discovery frames. Keep bounded internal reason codes and hashed request/path correlations, and guide assistants to prepare visible deliverables in the approved workspace or an explicitly authorized export root. Preserve path guards, original device ownership, quotas, expiry, legacy published cards, and unknown-send protections."},{"version":"1.6.226","text":"### 只为交付附件显示取回按钮\n- 普通源码引用不再生成取回卡片或文件不可用提示,只有助手明确作为附件交付的文件才会显示按钮;源码文件也可作为附件交付。\n- 子任务文件仍可在临时目录清理后由主助手选为附件,已生成的取回卡片保持可用。","changes":[{"topic":"output-files","title":"文件取回","text":"普通源码引用不再生成取回卡片或文件不可用提示,只有助手明确作为附件交付的文件才会显示按钮;源码文件也可作为附件交付。"},{"topic":"output-files","title":"文件取回","text":"子任务文件仍可在临时目录清理后由主助手选为附件,已生成的取回卡片保持可用。"}],"details":"### Changed\n- Require the exact Markdown link title `attachment` for newly selected output files. Ordinary source citations no longer produce Get file cards or unavailable notices, while deliberate source-file attachments remain supported.\n- Discover public attachment intent only from trusted assistant text, including native final-only replies, rather than aggregate backend diagnostics. Teach the selection syntax on each capability-enabled coordinator request without changing saved configuration.\n- Keep ordinary worker links as private snapshots for explicit coordinator selection after workspace reclamation. Existing published receipts, transfer permissions, quotas, and expiry remain compatible."},{"version":"1.6.225","text":"### 子任务故障自动收尾\n- Linux 上无法生成产物的已结束子任务会自动清理临时工作区,避免后续对话反复报收尾错误;如需其中内容,可重新运行子任务。","changes":[{"topic":"delegation","title":"委派任务","text":"Linux 上无法生成产物的已结束子任务会自动清理临时工作区,避免后续对话反复报收尾错误;如需其中内容,可重新运行子任务。"}],"details":"### Fixed\n- Automatically dispose of verified, terminated worker checkouts when artifact capture fails, persist completion receipts, and stop repeating unavailable-artifact closeout errors. Pending deliverables and external symlink targets retain their existing protections."},{"version":"1.6.224","text":"### 文件授权更省事,取回卡片更清晰\n- 后台子任务的内部文件和导出失败提示不再刷屏,只展示主助手选定的交付文件;临时目录清理后仍可取回已保存的文件快照。\n- 旧设备升级后自动申请文件授权,在飞书确认一次即可启用;已完成授权的设备不会重复提示,无需再到终端执行启用命令。\n- 文件名、大小和有效期分层显示,取回及重试按钮更醒目,传输中、成功、失败和结果不明有清晰的状态提示。","changes":[{"topic":"output-files","title":"文件取回","text":"后台子任务的内部文件和导出失败提示不再刷屏,只展示主助手选定的交付文件;临时目录清理后仍可取回已保存的文件快照。"},{"topic":"output-files","title":"文件取回","text":"旧设备升级后自动申请文件授权,在飞书确认一次即可启用;已完成授权的设备不会重复提示,无需再到终端执行启用命令。"},{"topic":"output-files","title":"文件取回","text":"文件名、大小和有效期分层显示,取回及重试按钮更醒目,传输中、成功、失败和结果不明有清晰的状态提示。"}],"details":"### Added\n- Automatically request file-key approval for eligible initialized devices and let the existing bound owner approve from a Feishu card. Skip approved devices, retain manual enrollment, and persist an explicit CLI automatic-enrollment opt-out.\n\n### Changed\n- Keep worker file snapshots internal until explicit coordinator selection, suppress worker-only export notices, and preserve hidden publication state across reconnects and restarts.\n- Restyle output-file entries and standalone transfer cards with status-colored headers, primary actions, readable file sizes and absolute UTC expiry times, and clear delivery confirmations. Preserve callback payloads, transfer state, retry boundaries, and uncertain-send protection."},{"version":"1.6.223","text":"### 首次绑定时一并启用文件能力\n- 新设备直接运行 `remote-cli init` 即会申请文件授权,仍需在飞书确认后启动;`--with-files` 保持兼容,无需再单独执行启用命令。\n- 旧 Router 或非本机 HTTP 的纯文本初始化需明确添加 `--without-files`;文件授权仍需 HTTPS 和支持该能力的 Router,失败时不会自动降级。","changes":[{"topic":"output-files","title":"文件取回","text":"新设备直接运行 `remote-cli init` 即会申请文件授权,仍需在飞书确认后启动;`--with-files` 保持兼容,无需再单独执行启用命令。"},{"topic":"output-files","title":"文件取回","text":"旧 Router 或非本机 HTTP 的纯文本初始化需明确添加 `--without-files`;文件授权仍需 HTTPS 和支持该能力的 Router,失败时不会自动降级。"}],"details":"### Added\n- Make `remote-cli init` request device binding and file-key approval by default with one Feishu binding code. Keep `--with-files` as a compatibility alias and require explicit `--without-files` for legacy text-only initialization; conflicting flags are rejected before initialization.\n- Reuse locally persisted device identities for retries and forced initialization; require an explicit secure-enrollment response without redirect or credentialless fallback.\n\n### Fixed\n- Persist an authentication requirement before first-device key enrollment, retain failed approvals for owner retry, and reject credentialless connections during enrollment and after restart. Sync approved keys before clearing the requirement and exclude sockets whose authentication outlives their connection."},{"version":"1.6.222","text":"### 补齐 Linux ARM64 文件取回支持\n- 安装包补齐 Linux ARM64 组件,修复该架构因缺少组件而无法启用文件取回的问题;仍需完成 HTTPS 连接和设备授权。","changes":[{"topic":"output-files","title":"文件取回","text":"安装包补齐 Linux ARM64 组件,修复该架构因缺少组件而无法启用文件取回的问题;仍需完成 HTTPS 连接和设备授权。"}],"details":"### Fixed\n- Include Linux arm64 native helpers in the CLI package so output-file retrieval can create snapshots on that architecture.\n- Build and test Linux arm64 helpers on a native CI runner, retain the minimum Node.js compatibility check, and require all six platform/architecture artifacts with matching source and binary hashes before publication."},{"version":"1.6.221","text":"### 从回复中取回本地文件\n- 回复中的合规本地文件链接可生成取回按钮,点击后通过独立任务卡片查看传输状态,并接收飞书文件。\n- 文件快照最多 20 MiB、保留 24 小时;支持离线等待和可确认失败的重试,发送结果不明时避免重复发送。\n- macOS 清理遇到暂时无法确认的进程状态时,在原有期限内继续确认;仍无法确认退出时保留数据。","changes":[{"topic":"output-files","title":"文件取回","text":"回复中的合规本地文件链接可生成取回按钮,点击后通过独立任务卡片查看传输状态,并接收飞书文件。"},{"topic":"output-files","title":"文件取回","text":"文件快照最多 20 MiB、保留 24 小时;支持离线等待和可确认失败的重试,发送结果不明时避免重复发送。"},{"topic":"delegation","title":"委派任务","text":"macOS 清理遇到暂时无法确认的进程状态时,在原有期限内继续确认;仍无法确认退出时保留数据。"}],"details":"### Added\n- Capture bounded immutable output-file snapshots from explicit assistant Markdown links, with native handle-relative reads and managed worker disposal fencing.\n- Add authenticated CLI-to-Router HTTP streaming, durable original-device references and transfer receipts, separate file-entry and progress cards, and native Feishu file delivery.\n- Preserve retryable failures and uncertain external send outcomes across restarts without replaying delivered files; enforce fixed expiry, storage quotas, and transfer concurrency limits.\n\n### Fixed\n- Keep inconclusive macOS process-group permission probes pending within the existing exit-confirmation deadline; require kernel absence before cleanup and report only recognized error codes.\n- Give multi-operation delegation fixtures independent phase deadlines and drain timed-out work before teardown."},{"version":"1.6.220","text":"### 更清楚地追查消息发送和恢复问题\n- 增加卡片大小、发送结果和更新差异的诊断记录,不记录卡片正文或请求凭据。\n- 关联任务结果确认、恢复等待与连接关闭记录,帮助区分卡片发送失败和连接中断。","changes":[{"topic":"delivery-diagnostics","title":"消息诊断","text":"增加卡片大小、发送结果和更新差异的诊断记录,不记录卡片正文或请求凭据。"},{"topic":"delivery-diagnostics","title":"消息诊断","text":"关联任务结果确认、恢复等待与连接关闭记录,帮助区分卡片发送失败和连接中断。"}],"details":"### Changed\n- Add bounded, metadata-only diagnostics for Feishu card delivery, including serialized UTF-8 sizes, delivery outcomes, and changes since the last successful update.\n- Correlate task-result acknowledgements, recovery timers, and WebSocket closure events to distinguish card delivery failures from connection interruptions.\n- Redact SDK delivery error logging so diagnostic events do not include card contents or request credentials."},{"version":"1.6.219","text":"### Windows 和 macOS 子会话清理\n- 补充 Windows 和 macOS 的受管子会话自动清理,保留代码成果及导出文件。\n- 清理前确认子进程退出;遇到归属冲突或退出状态不明时保留历史和恢复记录。","changes":[{"topic":"delegation","title":"委派任务","text":"补充 Windows 和 macOS 的受管子会话自动清理,保留代码成果及导出文件。"},{"topic":"delegation","title":"委派任务","text":"清理前确认子进程退出;遇到归属冲突或退出状态不明时保留历史和恢复记录。"}],"details":"### Added\n- Add Windows Job containment and macOS native process identity checks for managed worker and cleanup-process shutdown.\n- Add handle-relative native history deletion and bounded artifact reads on Windows and macOS, preserving recorded ownership, generation, retry, and deliverable checks.\n- Build and test bundled Node-API helpers on native x64 and arm64 runners; package validation requires matching platform binaries without install-time compilation.\n\n### Fixed\n- Enable compatible managed history capture on Windows and macOS and honor the private AGY user profile on Windows.\n- Record confirmed managed-tree exit in the ownership journal while retaining interrupted launches whose native evidence was lost."},{"version":"1.6.218","text":"### 重启后保留线程卡片操作\n- 新版 Router 保存卡片关联,重启后仍可在原有七天有效期内点击线程切换或回复卡片。\n- 切换前确认目标线程仍存在;已过期、已失效或升级前丢失关联的卡片可通过 `/thread list` 重新获取。\n- 切换保存较慢时提示等待确认,避免先显示失败却在后台切换线程。","changes":[{"topic":"thread-selection","title":"线程选择","text":"新版 Router 保存卡片关联,重启后仍可在原有七天有效期内点击线程切换或回复卡片。"},{"topic":"thread-selection","title":"线程选择","text":"切换前确认目标线程仍存在;已过期、已失效或升级前丢失关联的卡片可通过 `/thread list` 重新获取。"},{"topic":"thread-selection","title":"线程选择","text":"切换保存较慢时提示等待确认,避免先显示失败却在后台切换线程。"}],"details":"### Fixed\n- Preserve bounded card-to-thread routing associations across Router restarts within their original seven-day lifetime.\n- Validate thread-switch destinations against the connected device's current catalog and retain ownership checks and durable invalidation.\n- Keep asynchronous thread validation cancellable through timeout and disconnect, and avoid invalidating fresh cards after delayed device-switch notifications.\n- Remove all active continuation-card routes on interruption, retry failed removals, and preserve queue confirmations when route persistence fails before dispatch.\n- Distinguish cancellation before selection-save admission from pending or uncertain persistence, and report late durable outcomes without replaying a switch.\n\n### Tests\n- Cover persisted Router recreation, card expiry, ownership changes, invalidation, and ordinary thread routing with isolated fixtures."},{"version":"1.6.217","text":"### 扩展子代理会话清理\n- Linux 上为新建的 OpenCode、AGY、DSH 和 ZCode 子会话增加清理支持,主会话 clear 或 new 后按归属和退出状态清理。\n- 保留子代理的代码和交付物,清理条件不足时保留记录并说明原因。\n- 修复清理维护进程退出状态和不同后端会话标识的持久化处理。\n- 旧 AGY 子会话即使暂时无法清理,也能继续正常执行任务。","changes":[{"topic":"delegation-sessions","title":"子代理会话","text":"Linux 上为新建的 OpenCode、AGY、DSH 和 ZCode 子会话增加清理支持,主会话 clear 或 new 后按归属和退出状态清理。"},{"topic":"delegation-sessions","title":"子代理会话","text":"保留子代理的代码和交付物,清理条件不足时保留记录并说明原因。"},{"topic":"delegation-sessions","title":"子代理会话","text":"修复清理维护进程退出状态和不同后端会话标识的持久化处理。"},{"topic":"delegation-sessions","title":"子代理会话","text":"旧 AGY 子会话即使暂时无法清理,也能继续正常执行任务。"}],"details":"### Added\n- Extend managed child-session retirement to OpenCode, AGY, DSH, and ZCode using recorded creation ownership and backend-specific history or protocol checks, without pinning installed package versions.\n- Preserve native deliverables independently before ZCode history deletion and isolate new managed DSH history storage while retaining normal authentication and configuration sources.\n\n### Fixed\n- Persist maintenance-writer fences for Codex cleanup and retain them when process-group shutdown cannot be confirmed.\n- Persist deletion preparations for backend-native session identifiers rather than requiring every backend to use UUIDs.\n- Preserve ordinary AGY execution in legacy shared-cache lanes while holding cleanup, and reject case-only aliases of adopted native identities.\n\n### Tests\n- Cover native creation, reused worker contexts, durable cleanup recovery, retained outputs, and synthetic filesystem boundaries."},{"version":"1.6.216","text":"### 修复子会话清理被无关记录阻塞\n- 修复无关的非原生 Codex 会话记录可能阻止正常子会话清理的问题,保留归属和退出状态保护。\n- 清理无法继续时提供更明确的失败阶段,便于定位原因。","changes":[{"topic":"delegation-sessions","title":"子代理会话","text":"修复无关的非原生 Codex 会话记录可能阻止正常子会话清理的问题,保留归属和退出状态保护。"},{"topic":"delegation-sessions","title":"子代理会话","text":"清理无法继续时提供更明确的失败阶段,便于定位原因。"}],"details":"### Fixed\n- Prevent provably unrelated non-native Codex pointer IDs from blocking eligible managed-worker cleanup while preserving target identity, alias, filesystem, shutdown, and retry checks.\n- Report bounded cleanup validation stages without exposing private paths or raw backend errors.\n\n### Tests\n- Isolate activity fixtures from real backend homes and cover unrelated pointers, ambiguous ownership, and cleanup recovery with synthetic data."},{"version":"1.6.215","text":"### 放宽子会话清理的版本要求\n- Kimi 和 Claude 子会话清理按实际接口能力和历史格式判断,不再绑定某一个安装版本。\n- 兼容升级前保存的清理记录,仍保留会话归属和退出状态检查。","changes":[{"topic":"delegation-sessions","title":"子代理会话","text":"Kimi 和 Claude 子会话清理按实际接口能力和历史格式判断,不再绑定某一个安装版本。"},{"topic":"delegation-sessions","title":"子代理会话","text":"兼容升级前保存的清理记录,仍保留会话归属和退出状态检查。"}],"details":"### Fixed\n- Determine managed Kimi and Claude session cleanup compatibility from deletion capabilities and validated history formats instead of exact installed backend versions.\n- Preserve existing owned-session identities and immutable deletion receipts across compatible backend upgrades; retain ownership, shutdown, path, and retry safeguards.\n\n### Tests\n- Cover compatible version labels, incompatible capabilities and history layouts, and recovery with legacy deletion records using isolated synthetic fixtures."},{"version":"1.6.214","text":"### 修复 Codex 子会话清理兼容性\n- 清理 Codex 子会话时按实际接口能力判断,不再限定必须使用某一个 Codex 版本。\n- 保留已有清理记录,归属不明确或尚未确认退出的会话仍不会被误删。","changes":[{"topic":"delegation-sessions","title":"子代理会话","text":"清理 Codex 子会话时按实际接口能力判断,不再限定必须使用某一个 Codex 版本。"},{"topic":"delegation-sessions","title":"子代理会话","text":"保留已有清理记录,归属不明确或尚未确认退出的会话仍不会被误删。"}],"details":"### Fixed\n- Determine managed Codex session cleanup compatibility from native protocol behavior and validated metadata instead of rejecting every server version except 0.166.0.\n- Preserve exact ownership and shutdown checks, and retain existing deletion preparations when retrying cleanup after an upgrade.\n\n### Tests\n- Cover compatible version labels, unavailable methods, invalid acknowledgements, legacy receipt recovery, and ambiguous deletion failures.\n- Verify Codex 0.165.0 list/read/delete and exact missing-target responses using isolated synthetic histories without model calls or real user history access."},{"version":"1.6.213","text":"### 修复 Windows 子代理运行\n- 修复 Windows 保存子代理状态时可能失败的问题,保留原有会话清理与恢复保护。","changes":[{"topic":"delegation-sessions","title":"子代理会话","text":"修复 Windows 保存子代理状态时可能失败的问题,保留原有会话清理与恢复保护。"}],"details":"### Fixed\n- Preserve managed worker metadata durability with file handles that support flushing on Windows, without suppressing write or synchronization failures.\n\n### Tests\n- Keep host-native storage and ownership behavior in cleanup fixtures, and verify quarantined initialization before any worker is constructed."},{"version":"1.6.212","text":"### 更多子代理会话可自动清理\n- 扩展 Kimi、Pi 和 Claude 子会话清理:清空或新建主会话后,清理归属明确且已退出的旧子会话。\n- 清空前仍可复用上下文;任务结果、代码产物和恢复记录继续保留,不改为归档。\n- 退出未确认、旧会话或暂不支持的情况保留待处理状态,不删除来源不明的会话。","changes":[{"topic":"delegation-sessions","title":"子代理会话","text":"扩展 Kimi、Pi 和 Claude 子会话清理:清空或新建主会话后,清理归属明确且已退出的旧子会话。"},{"topic":"delegation-sessions","title":"子代理会话","text":"清空前仍可复用上下文;任务结果、代码产物和恢复记录继续保留,不改为归档。"},{"topic":"delegation-sessions","title":"子代理会话","text":"退出未确认、旧会话或暂不支持的情况保留待处理状态,不删除来源不明的会话。"}],"details":"### Changed\n- Extend parent-reset cleanup to newly owned Kimi, Pi, and Claude delegated sessions, retaining context reuse until `/clear` or `/new` and preserving task artifacts and recovery records.\n- Use backend-specific native deletion or exact owned history paths, with durable ownership receipts and retry state instead of archiving or deleting shared session stores.\n- Keep unsupported platforms, unconfirmed shutdown, adopted sessions, and ambiguous ownership outside automatic deletion.\n\n### Tests\n- Cover managed creation receipts, parent-reset generations, adopted-history conflicts, partial deletion recovery, and maintenance exit fencing with isolated synthetic fixtures.\n- Reproduce parent-directory substitution and detached-pointer file conflicts; verify descriptor-anchored removal, procfs failure handling, and handle cleanup."},{"version":"1.6.211","text":"### 清空主会话时清理子代理\n- 清空或新建主会话时,请求清理旧子代理会话;清空前仍可复用子代理的上下文。\n- 首版支持 Linux 上新产生且校验通过的 Codex 0.166.0 子会话;旧会话、其他后端等暂不支持的情况会保留状态,不改为归档。\n- 任务结果、代码产物和恢复记录继续保留,不随会话历史删除。","changes":[{"topic":"delegation-sessions","title":"子代理会话","text":"清空或新建主会话时,请求清理旧子代理会话;清空前仍可复用子代理的上下文。"},{"topic":"delegation-sessions","title":"子代理会话","text":"首版支持 Linux 上新产生且校验通过的 Codex 0.166.0 子会话;旧会话、其他后端等暂不支持的情况会保留状态,不改为归档。"},{"topic":"delegation-sessions","title":"子代理会话","text":"任务结果、代码产物和恢复记录继续保留,不随会话历史删除。"}],"details":"### Changed\n- Initially support newly recorded Codex 0.166.0 sessions on Linux with confirmed process-group exit and no native descendants. Preserve explicit holds for legacy identities, unsupported versions/platforms/backends, and uncertain ownership.\n- Request permanent deletion of owned delegated-worker native sessions when the parent conversation is cleared with `/clear` or `/new`, while preserving context reuse before reset and retaining task artifacts and recovery records.\n- Track deferred cleanup separately from conversation reset; require confirmed shutdown and supported native deletion, and retain explicit failure or unsupported state instead of archiving or claiming pointer removal deleted native history.\n\n### Tests\n- Cover parent reset races, native ownership retained across worker resets, incomplete exit evidence, bounded recovery receipts, and lost deletion acknowledgements with realistic native metadata fixtures.\n- Verify Codex 0.166.0 deletion and missing-target retry against synthetic histories in an isolated native home without model calls or real user history access."},{"version":"1.6.210","text":"### 子代理提示更精简\n- 复用子代理会话时,不再重复发送已确认接收的固定说明,保留已有上下文。\n- 每项任务仍提供最新目标和工作目录等信息;新会话或初始化未确认时重新发送完整说明。","changes":[{"topic":"delegation-prompts","title":"子代理提示","text":"复用子代理会话时,不再重复发送已确认接收的固定说明,保留已有上下文。"},{"topic":"delegation-prompts","title":"子代理提示","text":"每项任务仍提供最新目标和工作目录等信息;新会话或初始化未确认时重新发送完整说明。"}],"details":"### Changed\n- Send fixed delegated-worker instructions once per confirmed native conversation while refreshing task objectives, workspace/checkpoint details, external-link warnings, and export requirements on every task.\n- Restore full instructions for fresh or unconfirmed contexts, including missing-history fallback and failed initialization, without disabling worker conversation reuse.\n\n### Tests\n- Cover prompt initialization across executor recreation, manager restart, context reset, missing pointers, native fallback, and refreshed Git task metadata."},{"version":"1.6.209","text":"### 外部软链接直接可用\n- 新子任务可直接使用普通外部软链接,无需逐条配置白名单;保留链接及原来的目标,不复制目标内容。\n- 保留自动回写和清理时的目录检查;外部目标中的修改仍不会进入任务产物或随任务回滚。","changes":[{"topic":"delegation-symlinks","title":"子任务软链接","text":"新子任务可直接使用普通外部软链接,无需逐条配置白名单;保留链接及原来的目标,不复制目标内容。"},{"topic":"delegation-symlinks","title":"子任务软链接","text":"保留自动回写和清理时的目录检查;外部目标中的修改仍不会进入任务产物或随任务回滚。"}],"details":"### Changed\n- Admit ordinary external symbolic links in new managed Git tasks without requiring per-link grants. Preserve original link text in checkpoints and the original external target in worker checkouts without copying target contents.\n- Keep external target edits outside artifact review, integration, and rollback. Retain link identity, protected-target, and automatic write and cleanup checks, including recorded policies for existing artifacts.\n\n### Tests\n- Cover automatic external-link admission, target-preserving checkout mapping, link-only artifacts, and guarded closeout and lane reuse."},{"version":"1.6.208","text":"### 授权无需重启\n- 新增或移除外部软链接授权后,新子任务直接读取最新配置,无需重启 CLI 或会话;已有任务继续按启动时的授权完成收尾。\n- 保存后端等其他设置时保留磁盘中的最新授权,避免丢失新授权或恢复已撤销的授权。\n- 延长上传后的版本确认等待时间,适应 npm 发布扫描延迟,避免误报失败;不会重复上传。","changes":[{"topic":"delegation-symlinks","title":"子任务软链接","text":"新增或移除外部软链接授权后,新子任务直接读取最新配置,无需重启 CLI 或会话;已有任务继续按启动时的授权完成收尾。"},{"topic":"delegation-symlinks","title":"子任务软链接","text":"保存后端等其他设置时保留磁盘中的最新授权,避免丢失新授权或恢复已撤销的授权。"},{"topic":"npm-publishing","title":"自动发布","text":"延长上传后的版本确认等待时间,适应 npm 发布扫描延迟,避免误报失败;不会重复上传。"}],"details":"### Fixed\n- Read shared-symlink grants from the current local configuration before each new managed Git task without requiring a CLI or conversation restart.\n- Keep running tasks and saved artifacts pinned to their recorded policy, and reject invalid or unreadable policy without falling back to stale grants or rewriting configuration.\n- Preserve current on-disk grants during unrelated configuration saves, including additions, revocations, and invalid policy, instead of restoring stale runtime grants.\n- Allow ten minutes of post-upload registry confirmation polling for npm publish-time scanning while retaining single uploads, integrity checks, and immediate failure on lookup errors.\n\n### Tests\n- Cover same-instance grant addition and removal, missing and malformed configuration, sanitized failures, and unchanged in-memory settings and configuration files."},{"version":"1.6.207","text":"### 兼容 Windows 软链接\n- 修复 Windows 下软链接文本转换导致子任务启动失败的问题,保留链接语义与目录边界检查。","changes":[{"topic":"delegation-symlinks","title":"子任务软链接","text":"修复 Windows 下软链接文本转换导致子任务启动失败的问题,保留链接语义与目录边界检查。"}],"details":"### Fixed\n- Preserve native symbolic-link semantics using Git-compatible Windows separators in checkpoint indexes and checkout verification, retaining alias components, canonical containment, and link-identity checks.\n\n### Tests\n- Cover native link-text conversion, replacement during opaque index insertion, and internal-link collection, reclamation, and lane reuse.\n- Bound each large-repository lifecycle test phase separately and drain unfinished work before removing its fixture."},{"version":"1.6.206","text":"### 保留子任务软链接\n- 修复目录改为仓库内软链接后子任务启动失败的问题,保留链接及主工作区的暂存状态。\n- 可按仓库和链接逐项授权外部共享目标,子任务保留链接而不复制内容;通过链接修改的共享内容不会进入任务产物或回滚。","changes":[{"topic":"delegation-symlinks","title":"子任务软链接","text":"修复目录改为仓库内软链接后子任务启动失败的问题,保留链接及主工作区的暂存状态。"},{"topic":"delegation-symlinks","title":"子任务软链接","text":"可按仓库和链接逐项授权外部共享目标,子任务保留链接而不复制内容;通过链接修改的共享内容不会进入任务产物或回滚。"}],"details":"### Added\n- Add exact local grants for shared external symbolic links, preserving original link text in artifacts and mapping owned worker links to their original targets without copying target contents.\n- Snapshot link policy with worker artifacts and disclose that shared-target edits occur directly outside artifact collection and rollback.\n\n### Fixed\n- Preserve repository-local symbolic links when a tracked directory is replaced, without traversing stale indexed child paths or modifying the source index.\n\n### Tests\n- Cover symbolic-link replacements, ignored tracked replacements, unchanged source state, and rejected external targets.\n- Verify explicit shared-link grants, direct content edits, logical artifact trees, restart and lane reuse, protected cleanup, bounded policy records, and typed configuration repair.\n- Reject shared-link directory races without staging payload blobs or enumerating shared paths, and keep unrelated project grants independent."},{"version":"1.6.205","text":"### 加固 Router 对外入口\n- 隐藏公开健康接口中的设备标识,卡片操作统一通过飞书长连接处理,并限制异常绑定请求和未注册连接;保留旧版 CLI 的正常注册方式。","changes":[{"topic":"router-security","title":"Router 安全","text":"隐藏公开健康接口中的设备标识,卡片操作统一通过飞书长连接处理,并限制异常绑定请求和未注册连接;保留旧版 CLI 的正常注册方式。"}],"details":"### Security\n- Remove device identifiers from public health responses and retire the unauthenticated HTTP card callback; Feishu card actions continue through the native long connection.\n- Bound binding requests and unregistered WebSocket admission while retaining legacy device registration and existing enrolled-device proofs.\n\n### Tests\n- Cover health redaction, rejected HTTP callback ingress, bounded admission, registration deadlines, resource release, and legacy reconnect compatibility."},{"version":"1.6.204","text":"### 看清 Claude 模型映射\n- 模型列表显示别名对应的实际模型标识并保留供应商前缀,方便区分同名选项;模型选择和调用方式不变。","changes":[{"topic":"claude-model-labels","title":"Claude 模型名称","text":"模型列表显示别名对应的实际模型标识并保留供应商前缀,方便区分同名选项;模型选择和调用方式不变。"}],"details":"### Changed\n- Show Claude Code model aliases alongside their native resolved model IDs, preserving provider prefixes and falling back to native names when resolution is unavailable. Keep direct/default labels, selection values, native metadata, and other backends unchanged.\n\n### Tests\n- Cover alias labels, provider preservation, fallback and bounds handling, and unchanged model selection and native metadata."},{"version":"1.6.203","text":"### 保留 Codex 原生请求标识\n- 使用 Codex 后端时保留原生 app-server 的 User-Agent,不再附加 remote-cli 标识;无需升级 Router。","changes":[{"topic":"codex-user-agent","title":"Codex 请求标识","text":"使用 Codex 后端时保留原生 app-server 的 User-Agent,不再附加 remote-cli 标识;无需升级 Router。"}],"details":"### Changed\n- Preserve native Codex app-server User-Agent construction during initialization instead of adding the remote-cli client identity. Keep product metadata and global Codex configuration unchanged.\n\n### Tests\n- Cover native-preserving initialization, inherited process settings, Codex version detection, and rejected-handshake cleanup/retry without model requests."},{"version":"1.6.202","text":"### 自动执行时减少提问打断\n- Kimi 默认启用原生 Never Ask,OpenCode 默认关闭提问工具;关闭自动批准后保留交互模式,无需升级 Router。","changes":[{"topic":"backend-automation","title":"后端自动执行","text":"Kimi 默认启用原生 Never Ask,OpenCode 默认关闭提问工具;关闭自动批准后保留交互模式,无需升级 Router。"}],"details":"### Changed\n- Apply Kimi native Never Ask mode before new and restored automatically approved sessions receive a task; preserve explicit manual approval behavior and reject unconfirmed mode setup.\n- Disable the OpenCode question tool for automatically approved managed processes without changing global backend configuration or other backends.\n\n### Tests\n- Cover native mode configuration, resumed sessions, initialization failures, and process-local question policies with synthetic ACP fixtures."},{"version":"1.6.201","text":"### 修复 Windows 路径与存储兼容性\n- 修复 Windows 下目录选择、子任务工作区和 Router 提示存储的兼容问题,保留 Linux 与 macOS 的路径和文件安全检查。","changes":[{"topic":"windows-compatibility","title":"Windows 兼容性","text":"修复 Windows 下目录选择、子任务工作区和 Router 提示存储的兼容问题,保留 Linux 与 macOS 的路径和文件安全检查。"}],"details":"### Fixed\n- Handle Windows filesystem and Git path representations without relaxing canonical-path, symbolic-link, or ownership validation on Linux and macOS.\n- Apply POSIX permission-bit checks only where those bits represent filesystem permissions, retaining structural validation of private Router storage.\n- Use Windows named pipes for approval IPC tests and short private Unix socket paths, with cleanup and retry after failed listener startup. Native Windows Claude sandboxing remains unsupported.\n\n### Tests\n- Use native temporary paths, explicit symbolic-link types, and platform-appropriate executable and permission fixtures across the CLI and Router suites.\n- Keep native Linux, macOS, and Windows build/test jobs as the release gate."},{"version":"1.6.200","text":"### 推送新版本后自动发布\n- 更新版本号并推送到 GitHub 主分支后,自动完成检查和两个 npm 包的发布,无需每次手动点击;保留手动重跑入口。\n- 发布后短暂查不到新版本时会等待确认,避免缓存延迟造成误报,不重复上传。","changes":[{"topic":"npm-publishing","title":"自动发布","text":"更新版本号并推送到 GitHub 主分支后,自动完成检查和两个 npm 包的发布,无需每次手动点击;保留手动重跑入口。"},{"topic":"npm-publishing","title":"自动发布","text":"发布后短暂查不到新版本时会等待确认,避免缓存延迟造成误报,不重复上传。"}],"details":"### Changed\n- Automatically publish both npm packages when a push to GitHub main increases the synchronized root package version. Compare against the push event's prior revision so multi-commit pushes are handled correctly.\n- Retain manual release recovery, skip unchanged versions, and reject invalid versions, downgrades, or unreadable prior revisions before publishing.\n- Bypass registry caches and poll for bounded post-publish visibility so a temporarily missing version does not immediately abort a successful upload; retain exact integrity matching and never automatically repeat the upload."},{"version":"1.6.199","text":"### 通过 GitHub 发布 npm 包\n- 支持在 GitHub Actions 手动触发两个包的发布;完成一次可信发布配置后,无需每次在本机登录 npm。\n- 发布前检查版本并运行构建和测试;部分发布成功后,可从原记录重跑,核对内容一致后继续发布剩余包。","changes":[{"topic":"npm-publishing","title":"自动发布","text":"支持在 GitHub Actions 手动触发两个包的发布;完成一次可信发布配置后,无需每次在本机登录 npm。"},{"topic":"npm-publishing","title":"自动发布","text":"发布前检查版本并运行构建和测试;部分发布成功后,可从原记录重跑,核对内容一致后继续发布剩余包。"}],"details":"### Added\n- Add a manually triggered GitHub Actions workflow for npm trusted publishing of both public packages, with locked dependencies, build/test gates, synchronized release-version checks, and exact package-integrity checks before skipping an already published version.\n- Reconcile uncertain publish outcomes against the registry without automatically repeating a publish request; reject conflicting versions and ambiguous registry failures.\n\n### Changed\n- Correct package repository attribution to the public GitHub repository and document one-time trusted-publisher setup and partial-release recovery."},{"version":"1.6.198","text":"### 旧子任务记录不再阻塞新委派\n- 个别旧记录损坏、无法读取或格式不兼容时,仍可启动新子任务;保留旧记录和历史,不自动复用异常记录,无需离线迁移。\n- 修复删除默认线程时报错前已清理会话数据的问题;现在会先拒绝操作,保留默认线程的会话和子任务。","changes":[{"topic":"delegation-runtime","title":"子任务委派","text":"个别旧记录损坏、无法读取或格式不兼容时,仍可启动新子任务;保留旧记录和历史,不自动复用异常记录,无需离线迁移。"},{"topic":"thread-controls","title":"线程切换","text":"修复删除默认线程时报错前已清理会话数据的问题;现在会先拒绝操作,保留默认线程的会话和子任务。"}],"details":"### Fixed\n- Allow fresh worker allocation despite unreadable or incompatible individual historical lane records. Preserve excluded records and native history, report incomplete inventory, and retain ownership, live-writer, and destructive-cleanup safeguards.\n- Reject attempts to delete the default thread before cancelling work, closing bridges, removing worker records, or deleting native session data.\n\n### Tests\n- Cover fresh allocation beside incompatible history, preservation and reuse boundaries, and default-thread deletion rejection through the command entry point without cleanup side effects."},{"version":"1.6.197","text":"### 修复取消回执、线程隔离和旧记录委派\n- 旧子任务记录缺少新版字段时可直接启动新委派,无需离线迁移;保留旧文件和会话,不复用异常旧任务,实际运行中的任务仍受冲突保护。\n- 委派启动失败时显示具体原因,便于定位问题。\n- 修复请求准备期间取消后没有回执的问题;单个线程的恢复记录损坏不再把其他线程已成功的请求报成失败。","changes":[{"topic":"delegation-runtime","title":"子任务委派","text":"旧子任务记录缺少新版字段时可直接启动新委派,无需离线迁移;保留旧文件和会话,不复用异常旧任务,实际运行中的任务仍受冲突保护。"},{"topic":"delegation-runtime","title":"子任务委派","text":"委派启动失败时显示具体原因,便于定位问题。"},{"topic":"thread-controls","title":"线程切换","text":"修复请求准备期间取消后没有回执的问题;单个线程的恢复记录损坏不再把其他线程已成功的请求报成失败。"}],"details":"### Fixed\n- Complete requests cancelled during admission exactly once, without waiting for attachment initialization or leaving a late attachment claim behind.\n- Isolate unreadable thread-generation metadata in thread listings and result summaries. Healthy threads keep working, while affected threads remain unavailable for execution and global backend changes.\n- Allow fresh delegation when historical dirty lanes lack newer shutdown fields. Keep native ownership and live-writer checks, preserve dirty metadata, files and sessions, and never reuse those lanes automatically. No offline migration is required.\n- Include the underlying ownership failure in managed-delegation errors.\n\n### Tests\n- Cover admission cancellation, sibling and default-thread recovery failures, unchanged historical records across restarts, and fresh-worker admission without relaxing native ownership checks."},{"version":"1.6.196","text":"### 旧子任务记录不再阻塞普通聊天\n- 修复升级后因旧子任务记录导致正常会话无法聊天、`/clear` 和 `/new` 后仍无法继续的问题,需升级本机 CLI。\n- 保留旧任务文件、成果和恢复记录;实际运行中的任务仍受冲突保护,子任务存储和成果处理继续检查所有权。","changes":[{"topic":"delegation-runtime","title":"子任务委派","text":"修复升级后因旧子任务记录导致正常会话无法聊天、`/clear` 和 `/new` 后仍无法继续的问题,需升级本机 CLI。"},{"topic":"delegation-runtime","title":"子任务委派","text":"保留旧任务文件、成果和恢复记录;实际运行中的任务仍受冲突保护,子任务存储和成果处理继续检查所有权。"}],"details":"### Fixed\n- Separate ordinary execution admission from historical managed-worker storage recovery. Legacy or unavailable metadata no longer blocks existing chats, unrelated threads, supported native commands, or compaction after `/clear` and `/new`.\n- Preserve live-worker conflict checks and strict ownership requirements for managed-worker storage, artifact integration, lane reuse, and cleanup. Preserve historical records and files without claiming uncertain workers have exited.\n\n### Tests\n- Cover conversation recovery with retained legacy metadata, sibling threads, delegation enabled and disabled, native commands, and active worker conflicts using isolated temporary homes."},{"version":"1.6.195","text":"### 子任务中断后可重新开始对话\n- 将清空会话与旧子任务收尾分开;`/clear` 和 `/new` 开始新的对话,旧任务的待处理成果不再拖住新请求,恢复文件与历史记录继续保留。\n- 中止主会话不再排在子任务收尾之后等待;旧任务迟到的结果不会干扰新请求,需升级本机 CLI。\n- 仍可能运行的任务继续接受停止和清理处理;与其冲突的代码执行仍受限制,不会把退出未确认的任务当作已安全结束。\n- 关闭 CLI 时,正在处理的请求会收到一次取消通知,迟到的完成结果不会再覆盖它。\n- 不支持的后端命令会正常提示原因,不再被旧子任务状态的报错掩盖;实际执行仍保留冲突检查。","changes":[{"topic":"delegation-runtime","title":"子任务委派","text":"将清空会话与旧子任务收尾分开;`/clear` 和 `/new` 开始新的对话,旧任务的待处理成果不再拖住新请求,恢复文件与历史记录继续保留。"},{"topic":"delegation-runtime","title":"子任务委派","text":"中止主会话不再排在子任务收尾之后等待;旧任务迟到的结果不会干扰新请求,需升级本机 CLI。"},{"topic":"delegation-runtime","title":"子任务委派","text":"仍可能运行的任务继续接受停止和清理处理;与其冲突的代码执行仍受限制,不会把退出未确认的任务当作已安全结束。"},{"topic":"delegation-runtime","title":"子任务委派","text":"关闭 CLI 时,正在处理的请求会收到一次取消通知,迟到的完成结果不会再覆盖它。"},{"topic":"delegation-runtime","title":"子任务委派","text":"不支持的后端命令会正常提示原因,不再被旧子任务状态的报错掩盖;实际执行仍保留冲突检查。"}],"details":"### Fixed\n- Separate managed-worker conversation recovery from process shutdown and artifact cleanup. `/clear` and `/new` detach historical worker context and closeout obligations while preserving recovery files, archives, ownership evidence, and unfinished cleanup.\n- Interrupt the coordinator independently of worker finalization, bound conversation-facing cancellation waits, and fence late output and completion against newer requests. Preserve direct-backend shutdown checks and restrictions on execution that conflicts with uncertain workers, including when delegation is disabled.\n- Keep recovery commands available without requiring healthy historical worker inventory. Upgrade the local CLI; native provider-resume behavior and the Router protocol are unchanged.\n\n- Restore one terminal cancellation response when the CLI shuts down an active request, while fencing late completions and retaining worker shutdown checks.\n- Return unsupported native-command errors before checking worker ownership; retain execution checks for supported native commands and compaction.\n\n### Tests\n- Cover interrupted worker cleanup, durable reset and restart, historical context separation, late callbacks, resource conflicts, failed persistence, and direct-executor shutdown safeguards with isolated fixtures.\n- Isolate backend and message-flow fixtures from real home directories and worker state; cover recovery, shutdown responses, and directory/session reset semantics in the full CLI suite."},{"version":"1.6.194","text":"### 修复含大文件仓库的子任务收尾\n- 修复仓库包含 Git LFS 文件时,子任务执行成功却在成果收尾时报错的问题;本地文件内容完整且可恢复时正常完成,需升级本机 CLI。\n- 文件缺失、内容不匹配或存储路径不安全时仍保留工作目录;不会自动下载大文件或清理此前失败的任务目录。","changes":[{"topic":"delegation-runtime","title":"子任务委派","text":"修复仓库包含 Git LFS 文件时,子任务执行成功却在成果收尾时报错的问题;本地文件内容完整且可恢复时正常完成,需升级本机 CLI。"},{"topic":"delegation-storage","title":"委派目录清理","text":"文件缺失、内容不匹配或存储路径不安全时仍保留工作目录;不会自动下载大文件或清理此前失败的任务目录。"}],"details":"### Fixed\n- Verify supported Git LFS pointers and local payloads during disposable worker finalization instead of rejecting every LFS-managed path. Preserve checkout recovery holds for missing or mismatched payloads, unsafe object storage and unsupported transformations; keep child-exit and artifact-disposition requirements unchanged.\n- Keep LFS verification local and leave historical failed worker records untouched. Upgrade the local CLI; Router protocol and native backend configuration are unchanged.\n\n### Tests\n- Exercise real local Git LFS payloads, unchanged and changed output, empty files, pointer-only checkouts, conservative reclamation, custom storage, corrupted or missing objects, unsafe paths, file replacement, and successful manager closeout. Keep the new fixture suite in the bounded real-Git process pool."},{"version":"1.6.193","text":"### 修复子任务传输超时后卡住\n- 修复嵌套 Git 仓库传输失败或超时后,子进程已退出但委派仍卡住的问题;仍确认两个子进程退出后才清理本次临时数据,不影响其他任务目录。需升级本机 CLI。","changes":[{"topic":"delegation-runtime","title":"子任务委派","text":"修复嵌套 Git 仓库传输失败或超时后,子进程已退出但委派仍卡住的问题;仍确认两个子进程退出后才清理本次临时数据,不影响其他任务目录。需升级本机 CLI。"}],"details":"### Fixed\n- Disconnect and drain failed nested Git transfer pipes before waiting for child closure. Preserve the original failure, SIGTERM/SIGKILL escalation, and the requirement that both children close before removing this transfer's quarantine; leave unrelated temporary directories intact.\n\n### Tests\n- Reproduce backpressure with real subprocesses, including a producer that exits before a receiver ignoring SIGTERM. Verify deadline rejection, forced receiver exit, both-close cleanup ordering, and isolation of another quarantine. Bound fixture cleanup waits with process and stream diagnostics."},{"version":"1.6.192","text":"### 恢复子任务委派\n- 使用系统级锁并记录子进程:空闲进程崩溃或本机重启后可自动恢复,仍在运行的子进程和无法确认的旧锁继续保护;恢复锁不会直接删除目录或会话。\n- 修复 1.6.191 发布包中无法列出后端或启动子任务的问题;需升级本机 CLI,单独升级 Router 不生效。\n- 正常停止服务或按 Ctrl+C 时,先等待子任务和会话退出再释放存储锁,避免重启后因旧锁阻塞聊天;无法确认退出时继续保留恢复状态。","changes":[{"topic":"delegation-runtime","title":"子任务委派","text":"使用系统级锁并记录子进程:空闲进程崩溃或本机重启后可自动恢复,仍在运行的子进程和无法确认的旧锁继续保护;恢复锁不会直接删除目录或会话。"},{"topic":"delegation-runtime","title":"子任务委派","text":"修复 1.6.191 发布包中无法列出后端或启动子任务的问题;需升级本机 CLI,单独升级 Router 不生效。"},{"topic":"delegation-runtime","title":"子任务委派","text":"正常停止服务或按 Ctrl+C 时,先等待子任务和会话退出再释放存储锁,避免重启后因旧锁阻塞聊天;无法确认退出时继续保留恢复状态。"}],"details":"### Fixed\n- Replace existence-only delegation exclusion with persistent native kernel gates for storage and shared repositories. Record hashed host, boot, PID namespace and owner process identity, and durably journal managed backend and Git child launches before spawn. Recover dead idle owners and same-host rebooted owners without unlink races or PID-age heuristics; retain live or uncertain child groups and legacy ownership metadata. Keep normal execution outside ownership scopes unchanged and preserve disposal checks independently of lock recovery.\n- Restore delegation backend discovery and task admission in the published CommonJS runtime by avoiding a local name collision with module exports. Preserve required artifact-export validation and task closeout behavior.\n- Handle SIGTERM and SIGINT through a shared asynchronous shutdown path registered before worker inventory initialization. Await client, executor, and delegation teardown before exiting; release storage ownership only after verified cleanup. Clean up partial startup failures, preserve uncertain-exit recovery state, and share teardown with automatic updates.\n- Canonicalize worker-context reset test roots, isolate their home directories, and cover temporary-directory aliases without weakening runtime path checks. Surface reset initialization failures directly rather than leaving a test waiting for a callback that cannot run.\n\n### Tests\n- Exercise real process contention, SIGKILL and concurrent recovery, surviving child groups, interrupted metadata publication, legacy locks, PID reuse, reboot/namespace identity, durable launch failures and ordinary spawn compatibility. Native Linux execution does not establish native macOS/Windows acceptance.\n- Compile the CLI with its shipping TypeScript configuration and run backend discovery, export validation, and a complete synthetic delegated task in a separate Node process. Cover worker reset and reuse through a filesystem alias while retaining rejection of noncanonical storage paths."},{"version":"1.6.191","text":"### 子任务结束后自动释放临时目录\n- Linux 上的新委派任务确认进程组退出并完成成果处理后自动清理临时工作目录和依赖;失败任务保存可恢复代码后也能清理,已有成果和原生会话保留。\n- 重启后继续发现待处理成果和未完成清理;无法确认进程退出或内容安全时明确保留原因。\n- 增加本地存量目录检查和显式离线清理流程,离线删除目前仅支持 Linux;升级不会直接删除旧目录,需要升级本机 CLI。","changes":[{"topic":"delegation-storage","title":"委派目录清理","text":"Linux 上的新委派任务确认进程组退出并完成成果处理后自动清理临时工作目录和依赖;失败任务保存可恢复代码后也能清理,已有成果和原生会话保留。"},{"topic":"delegation-storage","title":"委派目录清理","text":"重启后继续发现待处理成果和未完成清理;无法确认进程退出或内容安全时明确保留原因。"},{"topic":"delegation-storage","title":"委派目录清理","text":"增加本地存量目录检查和显式离线清理流程,离线删除目前仅支持 Linux;升级不会直接删除旧目录,需要升级本机 CLI。"}],"details":"### Changed\n- Treat new Linux managed Git worktrees as disposable execution storage after confirmed managed process-group exit and durable artifact closeout. Reclaim delivered and retained output, including recoverable failed tasks and temporary dependencies, while preserving native conversations and Git artifact references.\n- Coordinate storage ownership and shared repository operations, resume eligible cleanup, and rediscover pending artifacts independently of expiring task diagnostics. Preserve explicit recovery holds for uncertain exit, unsafe identity, uncaptured content and unresolved parent application.\n- Add explicit offline delegation storage inventory and historical disposal with frozen identity checks, including receipt-backed integration scratch. Preserve lane/native recovery metadata when reclamation fails, and fence shutdown admission while allowing teardown retries. Bind completed offline discard to its original obligation and keep bounded inventory diagnostics separate from task closeout. Keep macOS/Windows on conservative checkout policy. Existing worktrees are never swept or silently opted into disposal on reuse after upgrade; Router protocol and native backend settings are unchanged.\n\n### Tests\n- Cover disposable success/failure closeout, pending delivery after restart, failed/retained recreation, ownership exclusion and scoped historical cleanup with isolated filesystem/Git fixtures. Require kernel-confirmed group absence across fork races and preserve group obligations during missing-session retries; retain imported disposable receipts on unsupported platforms."},{"version":"1.6.190","text":"### 工具授权结果正确传达给后端\n- 修复 Kimi 和 OpenCode 无法正确识别工具批准、拒绝或取消结果的问题;需升级本机 CLI,单独升级 Router 不生效。\n- 保留原有授权设置和对话:自动批准关闭时仍需确认,模型提出的问题仍等待回答,不会自动启用“从不询问”模式。","changes":[{"topic":"acp-approval","title":"工具授权","text":"修复 Kimi 和 OpenCode 无法正确识别工具批准、拒绝或取消结果的问题;需升级本机 CLI,单独升级 Router 不生效。"},{"topic":"acp-approval","title":"工具授权","text":"保留原有授权设置和对话:自动批准关闭时仍需确认,模型提出的问题仍等待回答,不会自动启用“从不询问”模式。"}],"details":"### Fixed\n- Serialize shared Kimi and OpenCode permission decisions with the nested ACP v1 outcome for approvals, rejections, cancellations, and error paths. Preserve fail-closed validation, manual approval settings, interactive questions, and existing backend session bindings; native permission modes and the Router protocol are unchanged.\n\n### Tests\n- Exercise real Kimi/OpenCode executors and ACP NDJSON transport against a schema-validating synthetic agent, covering automatic approval, manual allow-once/allow-always, denial/cancellation, and interactive question selection/skip. Retain DSH interoperability checks and malformed-selection regression coverage."},{"version":"1.6.189","text":"### 重启后记住每台设备的线程\n- Router 现在按用户和设备保存所选线程,重启或在设备间来回切换都能恢复;旧版 CLI 也可使用,不会重置原有对话。\n- 已失效的卡片回复会明确报错,不会误发到默认线程;确认线程已删除后会通知并恢复默认,失败消息不会自动重发。偏好记录损坏时,可用 `/thread list` 获取新的线程选择按钮。\n- 修复续卡上的线程按钮和回复无法使用的问题;新建线程只有在完整清单确认后才会被选中,异常清单不会覆盖原选择。","changes":[{"topic":"thread-selection","title":"线程选择","text":"Router 现在按用户和设备保存所选线程,重启或在设备间来回切换都能恢复;旧版 CLI 也可使用,不会重置原有对话。"},{"topic":"thread-selection","title":"线程选择","text":"已失效的卡片回复会明确报错,不会误发到默认线程;确认线程已删除后会通知并恢复默认,失败消息不会自动重发。偏好记录损坏时,可用 `/thread list` 获取新的线程选择按钮。"},{"topic":"thread-selection","title":"线程选择","text":"修复续卡上的线程按钮和回复无法使用的问题;新建线程只有在完整清单确认后才会被选中,异常清单不会覆盖原选择。"}],"details":"### Fixed\n- Persist each Feishu user's selected thread per bound device with prompt FIFO durable writes, so Router restarts and A→B→A device switches restore selection without changing native sessions or the protocol-v1 CLI contract. Keep known replies independent, reject expired parent routes and stale card controls, and fence selection intents against late New Thread responses and ownership changes. Bind thread controls on actual delivered continuation cards and require a validated complete catalog before adopting a New Thread selection.\n- Reset a deleted selection only after a fresh authoritative catalog or an exactly correlated legacy missing-thread response; notify the user and never replay the failed message. Quarantine malformed optional preferences without disabling valid bindings or silently overwriting raw data, and preserve the previous selection when persistence fails. A narrow `/thread list` recovery path uses the existing legacy status response to refresh selection controls without executing a prompt.\n\n### Tests\n- Cover real Router/store reconstruction with legacy registration, per-user/device isolation and A→B→A restoration, `/clear` and reconnects, unbind/rebind, FIFO preference commits, stale intents and catalogs, card provenance, exact deletion handling without replay, durable uncertainty, malformed preferences, actual continuation finalization and replies, and New Thread creation versus selection persistence failures."},{"version":"1.6.188","text":"### 解绑设备不再留下归属异常\n- 修复解绑保存失败时设备仍显示已绑定却无法连接的问题;现在解绑记录与设备归属一起更新,失败时保持原状。","changes":[{"topic":"binding-storage","title":"设备绑定","text":"修复解绑保存失败时设备仍显示已绑定却无法连接的问题;现在解绑记录与设备归属一起更新,失败时保持原状。"}],"details":"### Fixed\n- Apply each device unbind in one durable snapshot, covering the user record, reverse ownership mapping, active-device fallback, and last-device deletion. A failed replacement now preserves both ownership representations instead of leaving a listed device without its mapping.\n\n### Tests\n- Cover active, inactive, and last-device unbinds, pre-replacement failure coherence in memory and after reload, and queued storage mutations that must not resurrect removed ownership."},{"version":"1.6.187","text":"### 绑定文件异常时保留原始数据\n- 修复绑定文件结构异常时可能被重置为空的问题:现在保留原文件并明确报错,修正或恢复文件后再启动 Router;合法旧格式和旧版 CLI 继续兼容。","changes":[{"topic":"binding-storage","title":"设备绑定","text":"修复绑定文件结构异常时可能被重置为空的问题:现在保留原文件并明确报错,修正或恢复文件后再启动 Router;合法旧格式和旧版 CLI 继续兼容。"}],"details":"### Fixed\n- Validate binding-file structure and supported versions before adopting data, migrating legacy records, or removing expired codes. Preserve malformed files without replacement and block reads and writes on the rejected instance instead of silently publishing empty bindings.\n- Retain valid version-1 records and versionless single-device migrations, including empty legacy stores and opaque dictionary keys. Keep parser input out of reported errors and preserve protocol-v1 CLI compatibility.\n\n### Tests\n- Cover malformed roots, collections, nested records, timestamps and versions, byte-preserving failure, blocked post-failure access, valid legacy/current reloads, private parser diagnostics, and recovery through a fresh instance after repair."},{"version":"1.6.186","text":"### Pi 长任务不再中途失败\n- 修复 Pi 后端在任务进行到 10 分钟时被强制中断:只要连续 10 分钟内不断有事件(输出、工具执行、扩展 UI 的提示与回复都算),任务就会继续;单个工具长时间没有任何事件时仍会按超时结束。等待用户回答扩展 UI 问题期间不计入无活动超时(调用方设置的硬上限仍生效),但需要回复或 /abort 才会继续。\n- 超时和 `/abort` 不再显示成 “Request aborted”,而是给出明确的原因说明。","changes":[{"topic":"pi-turn-timeout","title":"Pi 长任务","text":"修复 Pi 后端在任务进行到 10 分钟时被强制中断:只要连续 10 分钟内不断有事件(输出、工具执行、扩展 UI 的提示与回复都算),任务就会继续;单个工具长时间没有任何事件时仍会按超时结束。等待用户回答扩展 UI 问题期间不计入无活动超时(调用方设置的硬上限仍生效),但需要回复或 /abort 才会继续。"},{"topic":"pi-turn-timeout","title":"Pi 长任务","text":"超时和 `/abort` 不再显示成 “Request aborted”,而是给出明确的原因说明。"}],"details":"### Fixed\n- Make the Pi inactivity watchdog the `ExecuteOptions.inactivityTimeout` window (10 minutes by default), re-armed by every Pi event so a long tool chain no longer fails exactly 10 minutes after the prompt. An extension-UI prompt suspends the watchdog until the user answers while a positive hard limit stays armed, and a dialog that Pi resolves on its own timer re-arms the watchdog. A positive `ExecuteOptions.timeout` is a one-shot hard limit and a non-finite one arms nothing, while `inactivityTimeout: 0` / `timeout: 0` each disable only their own deadline, matching the Agy and Codex executors.\n- Claim remote-cli's own failure reason before Pi settles its aborted turn, so a deadline or an explicit `/abort` no longer surfaces Pi's raw `Request aborted`. A turn already failing is never failed twice, overlapping deadline and `/abort` paths send a single `abort`, `/abort` waits for the in-flight cleanup instead of releasing the turn early, and cleanup of a settled turn no longer aborts, recycles, or cancels the input dialog of a turn started afterwards.\n\n### Tests\n- Cover the deadline-versus-abort ordering, continuous tool activity that outlasts the watchdog window, the hard limit that events cannot extend, a single abort while the failure is in flight, a waiting input dialog that suspends the watchdog without cancelling the hard limit, a dialog that Pi resolves itself, a dialog still open when the turn settles, concurrent `/abort` cleanup, an `/abort` still clearing the queue when a successor starts, the cleared watchdog after a settled turn, the disabled, non-finite and default deadlines, and cleanup ownership after settlement."},{"version":"1.6.185","text":"### 修复消息归属、设备绑定与执行异常\n- 加强任务结果与通知的用户归属校验,继续支持旧版 CLI 的正常连接和结果回传。\n- 修复并发绑定和保存顺序问题,避免设备重复绑定或解绑后状态恢复;保存失败时明确报错。\n- 修复权限确认异常时可能自动放行工具的问题,此项需要升级 CLI 生效。\n- 修复 Codex 启动异常后任务状态过早释放的问题;停止失败可用 `/abort` 重试,确认停止后再接新任务,此项需要升级 CLI 生效。","changes":[{"topic":"router-security","title":"Router 安全","text":"加强任务结果与通知的用户归属校验,继续支持旧版 CLI 的正常连接和结果回传。"},{"topic":"binding-storage","title":"设备绑定","text":"修复并发绑定和保存顺序问题,避免设备重复绑定或解绑后状态恢复;保存失败时明确报错。"},{"topic":"cli-permissions","title":"权限确认","text":"修复权限确认异常时可能自动放行工具的问题,此项需要升级 CLI 生效。"},{"topic":"codex-runtime","title":"Codex 执行","text":"修复 Codex 启动异常后任务状态过早释放的问题;停止失败可用 `/abort` 重试,确认停止后再接新任务,此项需要升级 CLI 生效。"}],"details":"### Fixed\n- Validate Router task-output recipients against current device ownership while retaining protocol-v1 registration, legacy response shapes, background notifications, and owner-validated result recovery.\n- Serialize competing device binding operations and binding-code consumption to prevent one device from being assigned to different users concurrently.\n- Publish binding changes only after serialized atomic persistence succeeds; reject failed drafts, block uncertain replacements, preserve damaged input, and drain accepted writes early during shutdown while propagating failures after resource cleanup.\n- Cancel ACP permission requests when the approval callback fails or returns an invalid selection instead of selecting the first option.\n- Keep Codex execution fenced after an ambiguous turn-start failure until transport termination is confirmed, without automatically replaying uncertain work; allow an explicit `/abort` retry to recover after an unconfirmed stop.\n\n### Tests\n- Add regressions for recipient ownership, bound legacy clients, binding and storage races, failed approvals, and ambiguous native-turn cleanup."},{"version":"1.6.184","text":"### 修复 Docker 重建后的启动失败\n- 修复容器重建后因残留 PID 文件反复提示服务已运行的问题,保留真正重复启动的检查。\n- 完善启动失败和停止时的清理,避免停止请求后继续启动服务,并保护后续实例的运行记录。","changes":[{"topic":"router-lifecycle","title":"Router 启停","text":"修复容器重建后因残留 PID 文件反复提示服务已运行的问题,保留真正重复启动的检查。"},{"topic":"router-lifecycle","title":"Router 启停","text":"完善启动失败和停止时的清理,避免停止请求后继续启动服务,并保护后续实例的运行记录。"}],"details":"### Fixed\n- Recover from a persisted Router PID equal to the new startup process, including Docker PID 1 after container recreation, while retaining ordinary stop/status process checks and rejecting another live PID.\n- Register shutdown handling before asynchronous startup and use bounded cleanup for initialization failures and termination. Preserve replacement PID records and prevent interrupted initialization from continuing into a new server start.\n\n### Tests\n- Cover self-PID recovery, duplicate-process refusal, initialization failures, early signals, bounded shutdown, and ownership-safe cleanup with isolated fixtures."},{"version":"1.6.183","text":"### 两个 Codex 提醒彩蛋\n- 新增周额度状态和重置卡张数增加提醒的彩蛋图解,小贴士共 27 条;明确卡片只是检测快照,不会自动发放、领取或消耗重置卡。","changes":[{"topic":"tips","title":"使用技巧","text":"新增周额度状态和重置卡张数增加提醒的彩蛋图解,小贴士共 27 条;明确卡片只是检测快照,不会自动发放、领取或消耗重置卡。"}],"details":"### Added\n- Add two Easter-egg Tips explaining the passive Codex weekly-quota and banked-reset-credit increase notices, including their sampling limits and the distinction from resetting context or granting, claiming, or consuming credits.\n- Expand the bundled catalog, native-card-based SVG/PNG illustrations, preview gallery, contact sheet, and download archive to 27 tutorials while preserving existing content and progress.\n\n### Tests\n- Cover passive notification copy and artwork, complete packaging, and preserved reading progress and opt-outs when upgrading from the 25-tip catalog."},{"version":"1.6.182","text":"### 新增八个工具操作图解\n- 小贴士扩充至 25 条,新增目录选择、独立线程、工具详情、委派开关和会话清理、Codex 速度与目标、命令沙箱的操作说明和配图。\n- 原有阅读记录继续保留,图册与下载包同步补齐全部新图。","changes":[{"topic":"tips","title":"使用技巧","text":"小贴士扩充至 25 条,新增目录选择、独立线程、工具详情、委派开关和会话清理、Codex 速度与目标、命令沙箱的操作说明和配图。"},{"topic":"tips","title":"使用技巧","text":"原有阅读记录继续保留,图册与下载包同步补齐全部新图。"}],"details":"### Added\n- Add eight illustrated tool-operation Tips for directory selection, named project threads, tool details, delegation controls and targeted worker resets, Codex speed and native goals, and backend-specific command sandboxing. Preserve the existing 17 topic IDs and reading progress.\n- Expand the bundled catalog and editable SVG/PNG gallery to 25 tutorials, with a complete dynamically sized contact sheet and downloadable bundle.\n\n### Tests\n- Cover the expanded catalog, operation-specific prerequisites and illustrations, complete gallery coverage, and byte-identical packaged assets."},{"version":"1.6.181","text":"### 小贴士直接显示示例\n- 移除“看个例子”按钮,可复制的示例直接显示在使用方式下方,卡片仅保留下一条、我学会了和推送设置。","changes":[{"topic":"tips","title":"使用技巧","text":"移除“看个例子”按钮,可复制的示例直接显示在使用方式下方,卡片仅保留下一条、我学会了和推送设置。"}],"details":"### Changed\n- Remove the separate example button from illustrated Tips. Show copyable example instructions directly below usage, alongside the illustration and inline usage notes, with only Next, Mastered, and Settings controls.\n- Refresh previously delivered example and detail controls into the current card after normal ownership and expiry checks.\n\n### Tests\n- Cover inline examples, the three passive controls, and safe handling of both legacy callbacks without changing progress or preferences."},{"version":"1.6.180","text":"### 小贴士直接显示使用提示\n- 移除“展开讲讲”按钮,必要的使用限制直接显示在正文中,保留示例、下一条、已掌握和推送设置。","changes":[{"topic":"tips","title":"使用技巧","text":"移除“展开讲讲”按钮,必要的使用限制直接显示在正文中,保留示例、下一条、已掌握和推送设置。"}],"details":"### Changed\n- Remove the extra detail button from illustrated Tips and show concise usage notes directly in the card body. Keep examples, next-tip navigation, progress marking, and subscription settings available.\n- Refresh previously delivered detail controls into the simplified card after normal ownership and expiry validation.\n\n### Tests\n- Verify inline notes, the four remaining controls, example rendering, and safe handling of legacy detail callbacks."},{"version":"1.6.179","text":"### 默认每天收到一个小技巧\n- 小贴士默认每天推送一条,无需手动开启;可随时暂停、停止推送,或改为每周二、四。\n- 已主动停止推送的账号保持关闭,已有静音期限和阅读进度继续保留。","changes":[{"topic":"tips","title":"使用技巧","text":"小贴士默认每天推送一条,无需手动开启;可随时暂停、停止推送,或改为每周二、四。"},{"topic":"tips","title":"使用技巧","text":"已主动停止推送的账号保持关闭,已有静音期限和阅读进度继续保留。"}],"details":"### Changed\n- Enable daily illustrated Tips by default for new users and legacy default-off records, without requiring manual subscription. Preserve explicit opt-outs, mute deadlines, chosen frequencies, reading progress, and delivery timing protections.\n- Update Tips settings and documentation to explain the default cadence and pause or stop controls.\n\n### Tests\n- Cover automatic delivery without enrollment, legacy preference migration, and preservation of explicit stops, pauses, progress, and restart behavior."},{"version":"1.6.178","text":"### 每次学会一个实用技巧\n- 新增 17 个中文图解小技巧,按实际面板和任务卡重绘配图,并提供 SVG 源图与可复制示例,发送 `/tips` 即可浏览。\n- 可主动订阅每日或每周两次推送,支持按天静音、恢复和关闭;按用户去重,避开近期操作及 Router 可观察到的任务时段,默认不自动推送。","changes":[{"topic":"tips","title":"使用技巧","text":"新增 17 个中文图解小技巧,按实际面板和任务卡重绘配图,并提供 SVG 源图与可复制示例,发送 `/tips` 即可浏览。"},{"topic":"tips","title":"使用技巧","text":"可主动订阅每日或每周两次推送,支持按天静音、恢复和关闭;按用户去重,避开近期操作及 Router 可观察到的任务时段,默认不自动推送。"}],"details":"### Added\n- Bundle 17 illustrated Chinese scenario tips with deterministic manual browsing and passive Feishu cards. Each tip includes a distinct packaged PNG redrawn from the real settings or task-card UI, an editable SVG, and a copyable example that is never executed by a card action. All examples use synthetic content.\n- Add Router-owned explicit daily or twice-weekly subscriptions, timezone settings, permanent opt-out, and timed mute controls. Deduplicate per user across devices; skip recent activity, observed tasks, offline users, and exhausted catalogs.\n- Persist private preferences and pre-dispatch delivery intent. Suppress ambiguous sends after failures or restarts, validate card ownership and expiry, and stop scheduling before Router shutdown.\n\n### Tests\n- Cover content and packaging, subscription and delivery state transitions, failure recovery, action validation, transport isolation, and Router integration with mocked Feishu APIs."},{"version":"1.6.177","text":"### 清空对话同时重置子 Agent\n- `/clear` 和 `/new` 同时重置当前线程在各后端的主会话及全部委派 Worker 会话,避免旧上下文在后续委派或切回后端时重新带入。\n- 保留项目文件、工作产物、历史存档和配置;清理失败或中断会明确提示并阻止继续使用旧会话,可修复后重试,其他线程不受影响。\n- 服务重启前等待未完成的清理并确认后端退出,失败时明确报告,避免把未完成的关闭当作成功。","changes":[{"topic":"delegation","title":"委派任务","text":"`/clear` 和 `/new` 同时重置当前线程在各后端的主会话及全部委派 Worker 会话,避免旧上下文在后续委派或切回后端时重新带入。"},{"topic":"delegation","title":"委派任务","text":"保留项目文件、工作产物、历史存档和配置;清理失败或中断会明确提示并阻止继续使用旧会话,可修复后重试,其他线程不受影响。"},{"topic":"delegation","title":"委派任务","text":"服务重启前等待未完成的清理并确认后端退出,失败时明确报告,避免把未完成的关闭当作成功。"}],"details":"### Changed\n- Make `/clear` and `/new` reset every direct backend session binding and managed worker continuation owned by the current thread, including inactive backends and parallel worker lanes. Preserve files, artifacts, archived transcripts, settings, and other threads.\n- Persist reset intent before clearing native pointers. After intent is saved, failed or interrupted resets remain retryable and prevent old context from resuming, including after CLI restarts; running, queued, and uncertain worker activity refuses an unsafe reset.\n- Reject incomplete worker inventories and unconfirmed native exits. Bound shutdown waits while preserving reset intent and process ownership for safe retries.\n- Join retained reset cleanup during service shutdown, preserve conversation data and reset intent, and propagate shutdown failures before automatic restart.\n- Keep single-worker card clearing and explicit `/delegation reset [backend]` available with their existing scopes. This CLI change uses the existing Router protocol.\n\n### Tests\n- Add regressions for both aliases, all-backend and multiple-worker isolation, reset failure/retry/restart handling, admission guards, and preservation of artifacts and settings. Verify that Pi workers start with a fresh native identity after pointer-only clearing while their archived transcripts remain available."},{"version":"1.6.176","text":"### 在模型设置中选择 Codex 速度\n- 支持原生速度选项的 Codex 模型可在模型卡片中单独选择速度,也可明确选择标准速度或跟随原生配置。\n- 速度按线程和后端保存,后续任务及委派工作使用对应设置;未选择速度的线程和其他后端保持原有行为。\n- 已选速度不再可用时仍可恢复原生配置;降级 Codex 后,旧会话可能需要升级或清空后才能安全继续。","changes":[{"topic":"model-speed","title":"模型速度","text":"支持原生速度选项的 Codex 模型可在模型卡片中单独选择速度,也可明确选择标准速度或跟随原生配置。"},{"topic":"model-speed","title":"模型速度","text":"速度按线程和后端保存,后续任务及委派工作使用对应设置;未选择速度的线程和其他后端保持原有行为。"},{"topic":"model-speed","title":"模型速度","text":"已选速度不再可用时仍可恢复原生配置;降级 Codex 后,旧会话可能需要升级或清空后才能安全继续。"}],"details":"### Added\n- Add a separate Speed section to model settings when the selected Codex model exposes native service tiers. Preserve native tier names and descriptions, with explicit Standard and Follow native config choices.\n- Persist speed independently per thread and backend, including future delegated workers, and apply sticky speed policy before activating native goals.\n- Negotiate model speed settings independently so older peers and backends without native speed controls retain their existing model behavior.\n\n### Safety\n- Validate speed against the selected model, reject incompatible model changes, and restore native configured speed explicitly instead of retaining a previous sticky override. Untouched threads send no new speed parameters or settings requests.\n- Keep speed reset available after tier removal. Require an upgrade or explicit conversation reset when a downgraded Codex protocol cannot safely clear a saved tier."},{"version":"1.6.175","text":"### 自动刷新 Kimi 模型列表\n- 查看或刷新 Kimi 模型列表时自动更新原生模型目录,无需先去电脑终端手动刷新或重新登录。\n- 刷新失败或超时会明确提示,可稍后重试;实际可用模型仍以 Kimi 账号返回的目录和权限为准。","changes":[{"topic":"kimi-models","title":"Kimi 模型","text":"查看或刷新 Kimi 模型列表时自动更新原生模型目录,无需先去电脑终端手动刷新或重新登录。"},{"topic":"kimi-models","title":"Kimi 模型","text":"刷新失败或超时会明确提示,可稍后重试;实际可用模型仍以 Kimi 账号返回的目录和权限为准。"}],"details":"### Fixed\n- Refresh Kimi Code's native managed model catalog automatically when listing models, so newly available models can appear without opening the native terminal or signing in again.\n- Bound refresh requests and local server cleanup, coalesce concurrent refreshes, and report discovery failures instead of silently presenting stale metadata as refreshed.\n- Reload an idle Kimi ACP process before applying discovered aliases while preserving its conversation binding, including choices discovered by temporary settings previews.\n\n### Tests\n- Cover native refresh ordering, new model discovery, failure and timeout handling, concurrent requests, and preservation of ordinary backend execution."},{"version":"1.6.174","text":"### 直接显示线程切换按钮\n- 恢复直接显示线程按钮和新建按钮,切换线程不再需要先点击展开。\n- 卡片元素上限从 150 提高到 180,减少因元素数量触发的拆卡,同时保留正文和完成信息的容量保护。","changes":[{"topic":"thread-controls","title":"线程切换","text":"恢复直接显示线程按钮和新建按钮,切换线程不再需要先点击展开。"},{"topic":"thread-controls","title":"线程切换","text":"卡片元素上限从 150 提高到 180,减少因元素数量触发的拆卡,同时保留正文和完成信息的容量保护。"}],"details":"### Changed\n- Restore directly visible thread-switch buttons and the new-thread button on completed cards, removing the thread folding panel while preserving reply attribution and routing behavior.\n- Increase the recursive card element budget from 150 to 180 tagged nodes, retaining completion reserves and the existing size and table limits.\n\n### Tests\n- Cover visible thread controls through finalization and refresh, switching callbacks, and recursive pagination boundaries at the new limit."},{"version":"1.6.173","text":"### 生成图片直接显示在回复中\n- Codex 返回受支持的原生或工具图片时会自动显示到卡片,无需再要求模型补写 Markdown 图片链接。\n- 修复回复结束时图片尚未上传完成而漏显的问题,同一回复中的相同图片只展示一次。\n- 图片读取和上传设有数量、大小与等待限制;异常时提示省略原因,正常文字回复仍可完成。完整改进需要同时升级 CLI 和 Router。","changes":[{"topic":"image-output","title":"图片输出","text":"Codex 返回受支持的原生或工具图片时会自动显示到卡片,无需再要求模型补写 Markdown 图片链接。"},{"topic":"image-output","title":"图片输出","text":"修复回复结束时图片尚未上传完成而漏显的问题,同一回复中的相同图片只展示一次。"},{"topic":"image-output","title":"图片输出","text":"图片读取和上传设有数量、大小与等待限制;异常时提示省略原因,正常文字回复仍可完成。完整改进需要同时升级 CLI 和 Router。"}],"details":"### Fixed\n- Forward recognized Codex native, MCP, and dynamic-tool image results directly to response cards without requiring Markdown. Prefer inline bytes and allow explicit native saved paths only through the local directory policy; omit image bytes from tool diagnostics.\n- Drain admitted image uploads before Router response finalization, including ordinary replies. Bound image work and fence late results after timeout, cancellation, disconnect, or stream replacement.\n- Deduplicate images by decoded content within a reply, retain changed content at the same path, and harden local reads with canonical-path checks, regular-file verification, bounded reads, and format validation. Keep image failures separate from task success.\n\n### Tests\n- Cover structured image variants, inline/file/Markdown deduplication, read and upload limits, finalization ordering, late results, filesystem boundaries, and unchanged text and goal behavior."},{"version":"1.6.172","text":"### 在 Codex 线程中持续推进目标\n- 支持 /goal 创建和查看原生目标,使用 pause、resume、clear 暂停、恢复或清除,并可通过 --budget 显式设置 token 预算。\n- 连续执行期间保留输出和审批入口;首版启动目标前需关闭当前线程的 managed delegation 并清空队列,进程恢复后需显式继续目标。","changes":[{"topic":"codex-goal","title":"Codex 目标","text":"支持 /goal 创建和查看原生目标,使用 pause、resume、clear 暂停、恢复或清除,并可通过 --budget 显式设置 token 预算。"},{"topic":"codex-goal","title":"Codex 目标","text":"连续执行期间保留输出和审批入口;首版启动目标前需关闭当前线程的 managed delegation 并清空队列,进程恢复后需显式继续目标。"}],"details":"### Added\n- Support Codex native `/goal`, `/goal <objective>`, `/goal pause`, `/goal resume`, and `/goal clear`, with optional explicit token budgets on activation or resume. Goal state and continuation remain owned by Codex's thread-goal APIs, without prompt-based continuation loops.\n- Keep goal output, approvals, activity, and thread admission attached across native continuation turns. Status and stop controls remain available during execution; unsupported backends fail without forwarding goal text to a model.\n\n### Changed\n- Initially require managed delegation disabled and an empty queue before activating a goal. Preserve native goal state on process loss and require explicit recovery; avoid accidentally resuming goals through status queries. Threads that never use native goals retain their existing execution path.\n\n### Tests\n- Cover command parsing, explicit budgets, native lifecycle transitions, multi-turn output ownership, stop and recovery behavior, unsupported versions, queue/settings exclusion, and unchanged ordinary execution."},{"version":"1.6.171","text":"### 稳定展开线程列表\n- 线程按钮改用飞书原生折叠面板,点击标题即可展开或收起,避免旧交互更新方式导致展开后立即复原;回复所属线程信息保持可见。","changes":[{"topic":"thread-controls","title":"线程切换","text":"线程按钮改用飞书原生折叠面板,点击标题即可展开或收起,避免旧交互更新方式导致展开后立即复原;回复所属线程信息保持可见。"}],"details":"### Fixed\n- Use the native Feishu Card 2.0 collapsible panel for completed-card thread controls. Expanding or collapsing the list requires no application callback or message PATCH, avoiding the previous PATCH-before-callback-response path that could immediately revert the expansion.\n- Keep thread selection and New controls inside the panel, with reply-source information outside it. Hidden controls remain included in recursive card budgets; existing backend execution, thread routing, and protocol behavior are preserved.\n\n### Tests\n- Cover native panel payloads, generated non-default thread selections, reply-source preservation, recursive budgets, and existing card fallback and Worker controls."},{"version":"1.6.170","text":"### 回滚线程卡片改动\n- 撤销今日的线程卡片折叠改动,恢复 1.6.168 的线程按钮显示和卡片拆分行为。","changes":[{"topic":"thread-controls","title":"线程切换","text":"撤销今日的线程卡片折叠改动,恢复 1.6.168 的线程按钮显示和卡片拆分行为。"}],"details":"### Reverted\n- Revert the 1.6.169 thread-card presentation change, restoring the always-visible thread controls and 150-node recursive card budget from 1.6.168."},{"version":"1.6.168","text":"### 用卡片浏览和切换目录\n- 输入 /cd 即可在卡片中浏览上一级、下一级和允许的根目录,只显示目录;点击“使用此目录”才切换当前线程,浏览本身不会清空会话。\n- 切换前检查目录权限和任务状态,拒绝过期或已变化的选择;大目录会明确提示列表限制,原有 /cd 路径命令仍可使用。","changes":[{"topic":"directory-browser","title":"目录浏览","text":"输入 /cd 即可在卡片中浏览上一级、下一级和允许的根目录,只显示目录;点击“使用此目录”才切换当前线程,浏览本身不会清空会话。"},{"topic":"directory-browser","title":"目录浏览","text":"切换前检查目录权限和任务状态,拒绝过期或已变化的选择;大目录会明确提示列表限制,原有 /cd 路径命令仍可使用。"}],"details":"### Added\n- Open bare `/cd` as a directory-only browser when both peers negotiate `directoryCards` and `settingsCards`. Navigate child/parent/root directories without executing a backend; apply only with Use this directory and preserve text `/cd <path>` for all peers.\n- Bind bounded local listings to owner, thread/configuration, allowlist, expiry, canonical roots, directory and ancestor identities. Omit symbolic-link directories, stop at the nearest allowed root, explicitly report partial listings, and reuse budgeted card rendering and exact-request receipts.\n\n### Changed\n- Serialize card and text directory changes through shared settings admission, reject active/queued/delegated work, and preserve existing all-backend context reset, same-directory no-op, and delegation workspace-generation cleanup. External filesystem races and bind mounts remain outside the application-level isolation guarantee.\n\n### Tests\n- Cover directory-only browsing, roots, busy navigation, changed identities/ancestors, symlinks, stale/forged/expired selections, duplicate Apply, text compatibility, card budgets, and optional capability negotiation."},{"version":"1.6.167","text":"### 子任务结果展示更完整\n- 子任务完成卡片的结果摘要上限提高至 4 KiB,减少过早截断,保留长结果的开头和结论。\n- 带省略标记的结果片段改用安全纯文本展示,避免截断代码块、表格或链接导致排版错乱;完整结果仍保留 Markdown 格式。","changes":[{"topic":"delegation","title":"委派任务","text":"子任务完成卡片的结果摘要上限提高至 4 KiB,减少过早截断,保留长结果的开头和结论。"},{"topic":"delegation","title":"委派任务","text":"带省略标记的结果片段改用安全纯文本展示,避免截断代码块、表格或链接导致排版错乱;完整结果仍保留 Markdown 格式。"}],"details":"### Fixed\n- Expand terminal Worker card summaries from 1000 bytes to 4 KiB for Router 1.6.167 or newer, retain UTF-8-safe beginning/end excerpts, and accept the full summary through Router validation and rendering. Older or unknown Routers retain the legacy budget; strict version precedence excludes 1.6.167 prereleases, and current registration metadata is rechecked after reconnect. Full delegated results and continuations retain their existing 32 KiB and 64 KiB limits.\n- Render worker result excerpts containing standalone omission markers as escaped literal text with a separate explanation, preventing head/tail splices from reinterpreting orphaned Markdown fences, links, tables, or card markup. Intact result Markdown and streaming activity formatting remain unchanged.\n\n### Tests\n- Cover larger ASCII/Unicode summaries, retained conclusions, legacy omission markers, Markdown and card-tag safety, Router boundary validation, and atomic Worker pagination under node, size, and table budgets."},{"version":"1.6.166","text":"### 工具结果不再导致客户端退出\n- 修复 Claude Code 返回多块工具结果时客户端崩溃的问题;仅提取文本,不把图片等非文本内容当作文件路径处理。\n- 本地图片检测或转发失败时保留正常任务回复,不再中断客户端或影响后续任务。","changes":[{"topic":"image-output","title":"图片输出","text":"修复 Claude Code 返回多块工具结果时客户端崩溃的问题;仅提取文本,不把图片等非文本内容当作文件路径处理。"},{"topic":"image-output","title":"图片输出","text":"本地图片检测或转发失败时保留正常任务回复,不再中断客户端或影响后续任务。"}],"details":"### Fixed\n- Normalize Claude native tool-result content blocks to text before forwarding; ignore embedded media and unknown payloads instead of passing them to string-only consumers.\n- Exclude native tool-result payloads from raw stdout logging before normalization.\n- Ignore non-string input in local-image detection and contain optional image-forwarding failures without terminating the CLI or failing an otherwise successful task. Preserve web-result exclusions and directory/size checks.\n\n### Tests\n- Cover mixed Claude content blocks, malformed image-detector input, asynchronous tool-result scan failures, final-output failures, and subsequent task execution."},{"version":"1.6.165","text":"### Pi 会话连接更可靠\n- 同一客户端内,不同线程不能同时连接同一个 Pi 会话;连接或断开写盘失败会明确提示失败,不再误报成功。\n- Pi 会话切换与模型等设置修改互斥,后台任务未结束或自动升级时不会切换上下文;Claude Code、Codex 仍仅提供只读列表。\n- 修正 Pi 自定义目录下的会话发现,并让本机重开命令正确处理含空格的会话路径;仍需避免本机与远程同时执行。","changes":[{"topic":"session-handoff","title":"会话接续","text":"同一客户端内,不同线程不能同时连接同一个 Pi 会话;连接或断开写盘失败会明确提示失败,不再误报成功。"},{"topic":"session-handoff","title":"会话接续","text":"Pi 会话切换与模型等设置修改互斥,后台任务未结束或自动升级时不会切换上下文;Claude Code、Codex 仍仅提供只读列表。"},{"topic":"session-handoff","title":"会话接续","text":"修正 Pi 自定义目录下的会话发现,并让本机重开命令正确处理含空格的会话路径;仍需避免本机与远程同时执行。"}],"details":"### Fixed\n- Reserve a selected Pi session file before asynchronous startup across threads in one daemon. Failed or unknown cleanup keeps the file quarantined until recovery; this is not an OS or cross-process writer lock.\n- Require successful pointer persistence before acknowledging Pi connection or detach. Failed writes retain the previous association; cancelled startup cannot commit a new connection.\n- Serialize Pi session confirmations with settings admission and reject context changes during queued work, active delegated tasks, or automatic updates. Claude Code and Codex remain read-only catalogs with unchanged executor and history behavior.\n- Discover default Pi sessions under `PI_CODING_AGENT_DIR`, fail closed for unresolved agent roots, and shell-quote Pi-only local reopen guidance.\n\n### Tests\n- Add concurrent-confirmation, persistence-failure, restart, cancellation, settings-conflict, custom-directory, and non-Pi read-only regressions."},{"version":"1.6.164","text":"### Pi 会话名称可区分\n- 新建 Pi 会话的默认名称使用独立的 session ID,不再重复使用线程 ID;重新打开已保存会话不会覆盖本机设置的名称。已有重名历史不自动改写。","changes":[{"topic":"session-handoff","title":"会话接续","text":"新建 Pi 会话的默认名称使用独立的 session ID,不再重复使用线程 ID;重新打开已保存会话不会覆盖本机设置的名称。已有重名历史不自动改写。"}],"details":"### Fixed\n- Give newly created Pi foreground sessions a default name based on their independent native session ID, not the reusable remote thread ID. `/new` sessions are distinguishable in `/resume`, and reopening a persisted file no longer appends `--name` or overwrites names assigned locally. Adopted sessions and synthetic runtime naming remain unchanged. Existing duplicate names are not rewritten automatically."},{"version":"1.6.163","text":"### Pi 新建对话保留旧会话\n- Pi 前台 `/new` 和 `/clear` 保留旧 session 的历史,为新对话使用独立 ID;旧会话可以通过 `/resume` 再次连接,不会把旧上下文带入新对话。\n- Pi 删除线程也保留原生历史;选择已有会话后、确认成功前,普通消息仍进入当前会话。委派 Worker 和临时元数据会话的清理规则不变。","changes":[{"topic":"session-handoff","title":"会话接续","text":"Pi 前台 `/new` 和 `/clear` 保留旧 session 的历史,为新对话使用独立 ID;旧会话可以通过 `/resume` 再次连接,不会把旧上下文带入新对话。"},{"topic":"session-handoff","title":"会话接续","text":"Pi 删除线程也保留原生历史;选择已有会话后、确认成功前,普通消息仍进入当前会话。委派 Worker 和临时元数据会话的清理规则不变。"}],"details":"### Changed\n- Pi foreground `/new` and `/clear` now remove only the current association and preserve native session history for `/resume`. Fresh conversations use independent random IDs rather than the stable remote thread ID, so retained files cannot resurrect cleared context, including after restart before the next prompt.\n- Pi foreground thread-data deletion also preserves native history. Delegated-worker and temporary metadata runtimes retain their disposable cleanup and thread-ID behavior.\n\n### Tests\n- Cover foreground A to `/new` to independent B, ordinary messages remaining in B during an unconfirmed resume draft, and confirmed native switching back to A. Cover reset/restart identity separation and unchanged synthetic-runtime cleanup."},{"version":"1.6.162","text":"### Pi 会话无需释放即可顺序切换\n- 移除 `/session release`:接管的 Pi 会话每轮飞书任务前会重新加载并校验,同一会话在本机新增的历史会被读入,不需要重新在飞书选择会话;`/session detach` 仍用于解除绑定。\n- 两侧 Pi 可以保持打开,但请保证不同时执行任务;切回本机窗口时仍需原生 `/resume` 重新加载。当前不提供自动本机刷新或并发互斥。","changes":[{"topic":"session-handoff","title":"会话接续","text":"移除 `/session release`:接管的 Pi 会话每轮飞书任务前会重新加载并校验,同一会话在本机新增的历史会被读入,不需要重新在飞书选择会话;`/session detach` 仍用于解除绑定。"},{"topic":"session-handoff","title":"会话接续","text":"两侧 Pi 可以保持打开,但请保证不同时执行任务;切回本机窗口时仍需原生 `/resume` 重新加载。当前不提供自动本机刷新或并发互斥。"}],"details":"### Changed\n- Remove `/session release`, the executor release operation and the persisted released-state gate. Existing adopted pointers with an old released flag remain usable; `/session detach` still confirms association removal without deleting native history.\n- Reload and verify the exact adopted Pi session before every remote prompt, including native slash prompts, so sequential local writes are visible without another remote resume or release step. Idle local Pi windows may remain open, but must resume the same file before their next turn. Simultaneous writing is unsupported and can create separate native branches; no automatic local refresh or writer exclusion is claimed.\n- Reserve remote turn preparation against overlapping execution/context changes and cancel preparation before prompt dispatch on abort/reset/shutdown. Keep legacy private sessions and worker execution unchanged.\n\n### Fixed\n- Synchronize the lockfile package versions with all package manifests."},{"version":"1.6.161","text":"### 会话接续\n- 一个线程现在可以连接并继续一个已有的 Pi 会话:`/resume` 列出当前工作目录的会话,`/resume select` 或 `id` 选中后显示确认,`/resume confirm` 连接;连接不发送任务。\n- 连接时会校验 Pi 实际打开的会话:不一致、已被其他线程占用、或选中后被本机修改都会被拒绝并保留原会话;接管的历史不会被 `/clear` 或 `/thread delete` 删除。\n- `/session` 查看连接状态,`/session release` 停止后端进程并锁定远程使用以方便本机继续,`/session detach` 确认后解除连接。\n- `/resume` 也支持翻页与搜索,令牌 5 分钟内有效且只对发起人、当前线程和工作目录生效。\n- 在本机运行 `remote-cli session show` 可查看重新打开会话的命令;Codex、Claude Code 等其他后端目前只能列出,还不能连接。","changes":[{"topic":"session-handoff","title":"会话接续","text":"一个线程现在可以连接并继续一个已有的 Pi 会话:`/resume` 列出当前工作目录的会话,`/resume select` 或 `id` 选中后显示确认,`/resume confirm` 连接;连接不发送任务。"},{"topic":"session-handoff","title":"会话接续","text":"连接时会校验 Pi 实际打开的会话:不一致、已被其他线程占用、或选中后被本机修改都会被拒绝并保留原会话;接管的历史不会被 `/clear` 或 `/thread delete` 删除。"},{"topic":"session-handoff","title":"会话接续","text":"`/session` 查看连接状态,`/session release` 停止后端进程并锁定远程使用以方便本机继续,`/session detach` 确认后解除连接。"},{"topic":"session-handoff","title":"会话接续","text":"`/resume` 也支持翻页与搜索,令牌 5 分钟内有效且只对发起人、当前线程和工作目录生效。"},{"topic":"session-handoff","title":"会话接续","text":"在本机运行 `remote-cli session show` 可查看重新打开会话的命令;Codex、Claude Code 等其他后端目前只能列出,还不能连接。"}],"details":"### Added\n- Reserve `/resume`, `/r` and `/session` as program-owned native session controls before executor construction, working-directory changes, queue admission or backend slash passthrough, and remove the misleading natural-language resume shortcut. Local session sharing stays disabled by default; enabling it never makes an unverified adapter available.\n- Add read-only native session discovery for Pi, Codex and Claude Code: `/resume` lists the current workspace's sessions (bounded reads, no backend process, no transcript text, no symlink following), hiding synthetic, delegated-worker, sidechain and ambiguous duplicate entries and reporting incomplete coverage. Message counts stay unavailable where they cannot be read safely.\n- Add paging and search to the read-only list: each list is a snapshot with an unguessable 12-character token, eight rows per page and a five-minute lifetime, bound to the requesting user, thread and workspace; `/resume page` and `/resume search` never reread native stores.\n- Connect a thread to an existing Pi session and continue its history. `/resume select` or `/resume id` shows a confirmation naming the session and any binding it replaces, and `/resume confirm` connects it. The loaded identity is verified through Pi RPC state without sending a prompt, so a silently substituted session is refused and the previous conversation is restored.\n- Add `/session` binding status, `/session release` (stop the owned Pi process and block remote work so a local Pi can take over) and `/session detach` (forget the association after confirmation). Adopted native history is user-owned: `/clear`, detach and `/thread delete` never delete it. A session held by another remote-cli thread, or changed locally after selection, is refused.\n- Add `remote-cli session show --thread <name> --backend <key>`: a read-only, daemon-free helper printing exact native reopen guidance."},{"version":"1.6.160","text":"### 切换后端不再需要确认按钮\n- 后端选择仍在卡片上方,点击后端直接切换,默认只影响当前线程,不再需要点击 Confirm;收到成功确认后才更新选中状态。\n- 下方范围按钮只设置下一次切换的目标,不会单独切换后端;同一卡片保留所选范围,重新打开默认当前线程,跟随全局只作用于当前线程。","changes":[{"topic":"settings-cards","title":"设置卡片","text":"后端选择仍在卡片上方,点击后端直接切换,默认只影响当前线程,不再需要点击 Confirm;收到成功确认后才更新选中状态。"},{"topic":"settings-cards","title":"设置卡片","text":"下方范围按钮只设置下一次切换的目标,不会单独切换后端;同一卡片保留所选范围,重新打开默认当前线程,跟随全局只作用于当前线程。"}],"details":"### Changed\n- Remove the backend card's Confirm section. Backend choices submit immediately using the selected scope, defaulting to Current thread, while Choose backend remains above Apply to. Scope buttons only change the next backend click's target; keep that scope within the same card after acknowledgement. Show only the acknowledged backend as selected, disable further changes while pending, and preserve exact-request retries and stale-revision validation. Follow global applies immediately to the original thread and restores the local scope to Current thread after acknowledgement. Existing CLI settings actions and text commands remain compatible."},{"version":"1.6.159","text":"### 大项目委派准备允许更长等待\n- 创建 Worker 工作目录和切换检出内容的超时从 15 秒提高到 120 秒,减少大项目在子 Agent 启动前超时;其他 Git 操作保持原有时限。\n- Git 超时提示显示具体操作、耗时和时限,方便定位准备阶段的问题。","changes":[{"topic":"delegation","title":"委派任务","text":"创建 Worker 工作目录和切换检出内容的超时从 15 秒提高到 120 秒,减少大项目在子 Agent 启动前超时;其他 Git 操作保持原有时限。"},{"topic":"delegation","title":"委派任务","text":"Git 超时提示显示具体操作、耗时和时限,方便定位准备阶段的问题。"}],"details":"### Fixed\n- Allow delegated `git worktree add` and `git checkout` commands up to 120 seconds so larger working trees can finish preparing. Other Git commands and nested object transfers retain their 15-second deadlines. Timeout messages identify the worktree subcommand and report elapsed time and the deadline without including paths or checkout references. Preserve child-exit waiting, kill escalation, output limits, task reservations and cancellation ordering."},{"version":"1.6.158","text":"### 减少空正文的完成续卡\n- 收尾时在容量允许的情况下,将最后一段正文和完成信息、线程按钮放在同一张卡片,避免单独多出一张只有完成区的续卡;保留 Worker 分组和卡片容量限制。","changes":[{"topic":"tool-cards","title":"工具卡片","text":"收尾时在容量允许的情况下,将最后一段正文和完成信息、线程按钮放在同一张卡片,避免单独多出一张只有完成区的续卡;保留 Worker 分组和卡片容量限制。"}],"details":"### Fixed\n- Keep the completion note, optional execution metadata and thread controls with the final body item or complete worker group when they fit together within continuation-card node, size and table budgets. Avoid a preventable footer-only continuation, including replies without execution metadata; retain the body when refreshing thread controls. Oversized indivisible groups still respect capacity limits. Streaming, queue confirmations and bare settings cards retain their existing behavior."},{"version":"1.6.157","text":"### 委派后端状态恢复彩色标签\n- 后端可用性恢复彩色状态标签:主 Agent 蓝色、已安装绿色、受限橙色、不可用红色,未知状态灰色;On/Off 操作保持不变。","changes":[{"topic":"delegation","title":"委派任务","text":"后端可用性恢复彩色状态标签:主 Agent 蓝色、已安装绿色、受限橙色、不可用红色,未知状态灰色;On/Off 操作保持不变。"}],"details":"### Changed\n- Restore colored status badges in the `/delegation` card's backend-availability section: blue for the coordinator, green for installed workers, orange for blocked workers, red for unavailable backends and neutral for unknown worker availability. Preserve literal detail escaping, card capacity accounting and acknowledged On/Off controls."},{"version":"1.6.156","text":"### 委派开关支持卡片操作\n- /delegation 新增当前线程的 On/Off 开关卡片,选中项蓝色高亮;点击后收到成功确认才更新状态。\n- 后端可用性单独展示,明确提示未安装和沙箱限制;运行中仍可查看,切换需等待任务完成,旧版本继续使用文字命令。","changes":[{"topic":"delegation","title":"委派任务","text":"/delegation 新增当前线程的 On/Off 开关卡片,选中项蓝色高亮;点击后收到成功确认才更新状态。"},{"topic":"delegation","title":"委派任务","text":"后端可用性单独展示,明确提示未安装和沙箱限制;运行中仍可查看,切换需等待任务完成,旧版本继续使用文字命令。"}],"details":"### Added\n- Add a thread-scoped `/delegation` settings card with blue checked On/Off controls and a separate backend-availability section. Clicks submit immediately, update selection only after durable CLI acknowledgement, and preserve pending/unknown states and exact-request retries. Running work and queued commands block mutation, not inspection or refresh; reset remains a separate text command.\n- Negotiate `delegationCards` in addition to `settingsCards` on protocol v1. Older peers retain the existing delegation status text and parameterized commands. Reuse immutable snapshots, ownership checks, admission barriers and native cleanup for card/text toggles; distinguish the enabled preference from sandbox restrictions, installation, authentication and quota."},{"version":"1.6.155","text":"### 设置卡片减少翻页,选中与后端分区更清晰\n- 模型和思考等级能放下一张卡片时全部展示,只有实际超出容量才分页,不再每八项强制翻页。\n- 后端卡片中选中的影响范围用蓝色高亮,选择当前线程或全部线程后仍需确认才生效。\n- 模型和思考等级卡片将当前主后端与其他后端分区展示,查看其他后端不会切换主后端。","changes":[{"topic":"settings-cards","title":"设置卡片","text":"模型和思考等级能放下一张卡片时全部展示,只有实际超出容量才分页,不再每八项强制翻页。"},{"topic":"settings-cards","title":"设置卡片","text":"后端卡片中选中的影响范围用蓝色高亮,选择当前线程或全部线程后仍需确认才生效。"},{"topic":"settings-cards","title":"设置卡片","text":"模型和思考等级卡片将当前主后端与其他后端分区展示,查看其他后端不会切换主后端。"}],"details":"### Changed\n- Show all model and effort choices when the complete settings card fits its recursive node and UTF-8 JSON budgets. Paginate only oversized catalogs, packing each page by actual capacity instead of a fixed eight-choice limit. Count headers, sections, backend groups, navigation, notices and pending/retry controls, preserve every opaque choice and retain existing callback validation and single-card delivery.\n- Highlight the drafted backend application scope in blue. Separate the current thread's main backend from other backends' worker preferences in model/effort cards, keeping the main role tied to the coordinator while viewing other targets. Preserve same-backend preference sharing, explicit backend confirmation and immediate acknowledged model/effort changes; no native request or protocol capability is added."},{"version":"1.6.154","text":"### 设置选择更清晰,减少测试等待\n- 后端、模型和思考等级按功能分区,补充小标题和选中标记,后端选择、影响范围与确认按钮不再混在一起。\n- 兼容 AGY 模型列表的两种列格式,空结果或无法识别的列表会明确提示,不再无说明地显示空菜单。\n- 减少大仓库检查和测试样本准备的串行开销,移除模拟进程测试中的真实等待,八核以上机器可并行运行更多 Git 测试;发布仍执行全量测试,不降低安全检查或缩小压力样本。","changes":[{"topic":"settings-cards","title":"设置卡片","text":"后端、模型和思考等级按功能分区,补充小标题和选中标记,后端选择、影响范围与确认按钮不再混在一起。"},{"topic":"settings-cards","title":"设置卡片","text":"兼容 AGY 模型列表的两种列格式,空结果或无法识别的列表会明确提示,不再无说明地显示空菜单。"},{"topic":"delegation","title":"委派任务","text":"减少大仓库检查和测试样本准备的串行开销,移除模拟进程测试中的真实等待,八核以上机器可并行运行更多 Git 测试;发布仍执行全量测试,不降低安全检查或缩小压力样本。"}],"details":"### Changed\n- Separate backend, model and effort cards into numbered functional sections with subtitles and dividers. Mark the drafted backend, applied backend and selected scope explicitly; keep Confirm separate. Model/effort cards separate the target backend, native choices and secondary actions, checking configured or known effective selections without guessing defaults. Include all new section elements in recursive node and byte accounting; retain existing validation, acknowledgements and old-peer behavior.\n- Accept both tab-delimited and formatted multi-space AGY model catalogs, preserving opaque native IDs and exact current-model matching. Reject empty, unusable and oversized responses explicitly instead of silently producing an empty or truncated menu. Query native metadata only; never prompt a model to invent catalog entries.\n- Bound filesystem verification to eight concurrent checks and drain all started work before propagating failure. Share complete ancestor-validation promises within each checkpoint pass, and give checkout byte readers independent buffers up to 1 MiB each. Preserve every file hash, symlink/mode check, HEAD/index recheck, both working-file passes and both reclamation audits; do not cache state across captures or relax production deadlines.\n- Replace real startup/stop waits in mocked Claude executor tests with controlled clocks. Advance the nested transfer timeout only after real producer/receiver startup and a nonempty partial pack, retaining process-exit and quarantine-cleanup assertions. Generate document ZIP fixture CRCs with a lookup table while preserving identical archive bytes, full expansion-bomb payloads and the full publish test suite. Use at most four isolated Git test processes only on hosts with at least eight available CPUs; lower-core limits and ordinary test deadlines are unchanged."},{"version":"1.6.153","text":"### 测试提速,Codex 命令说明更完整\n- 调整真实 Git 测试的并行资源并减少重复建仓开销,发布仍执行完整测试,不放宽委派文件安全检查或普通测试超时。\n- Codex 命令在没有原生动作摘要时也能显示简短操作标签,无法可靠识别时显示通用说明,不展示命令参数或把阶段思考套到工具上。\n- 晚到的原生动作信息可补充原来的工具栏,成功和失败结果仍更新原行,不新增卡片元素。","changes":[{"topic":"delegation","title":"委派任务","text":"调整真实 Git 测试的并行资源并减少重复建仓开销,发布仍执行完整测试,不放宽委派文件安全检查或普通测试超时。"},{"topic":"tool-cards","title":"工具卡片","text":"Codex 命令在没有原生动作摘要时也能显示简短操作标签,无法可靠识别时显示通用说明,不展示命令参数或把阶段思考套到工具上。"},{"topic":"tool-cards","title":"工具卡片","text":"晚到的原生动作信息可补充原来的工具栏,成功和失败结果仍更新原行,不新增卡片元素。"}],"details":"### Changed\n- Keep real Git suites in isolated processes while allowing up to two Git forks on hosts with at least four available CPUs and one to four lightweight threads. Reuse only pristine test fixture templates, copying repository metadata and files into independent owned directories for every test. The publish lifecycle still runs the entire suite without changing production Git checks or ordinary deadlines.\n- Fill Codex shell-call labels for absent and native unknown command actions with bounded fixed operation descriptions. Simple allowlisted programs receive labels such as Run npm command; compound or unrecognized commands stay generic. Preserve native read/search/list descriptions and every operation in compound action sets. Never copy shell arguments, complete paths, execution output, or turn-level reasoning into fallback headings, and do not claim model-authored purpose summaries.\n- Forward optional public native titles and allow later action metadata to enrich a pending tool row before its first result. Suppress duplicate starts after a result so repeated completion updates retain the original invocation. Reuse existing tool metadata, compact heading limits, asynchronous status updates, and card-element accounting without a wire-version change or extra model call."},{"version":"1.6.152","text":"### 后端、模型与思考等级可点击选择\n- `/backend` 打开选择卡片,默认只改当前线程;选择后端和影响范围后点击确认才生效,未安装的后端会明确标为不可选。\n- `/model`、`/effort` 可以直接点击原生选项,也能为其他后端设置模型和思考等级,不必先切换主 Agent;没有原生选项时会说明原因,不猜测支持情况。\n- 设置成功后才显示已应用;旧卡片、重复点击和忙碌线程会受到保护,旧版仍可使用文字命令。","changes":[{"topic":"settings-cards","title":"设置卡片","text":"`/backend` 打开选择卡片,默认只改当前线程;选择后端和影响范围后点击确认才生效,未安装的后端会明确标为不可选。"},{"topic":"settings-cards","title":"设置卡片","text":"`/model`、`/effort` 可以直接点击原生选项,也能为其他后端设置模型和思考等级,不必先切换主 Agent;没有原生选项时会说明原因,不猜测支持情况。"},{"topic":"settings-cards","title":"设置卡片","text":"设置成功后才显示已应用;旧卡片、重复点击和忙碌线程会受到保护,旧版仍可使用文字命令。"}],"details":"### Added\n- Negotiate standalone backend, model, and effort settings cards on protocol version 1. Backend selection defaults to the original current thread; selecting a backend or device-wide scope only edits a draft until Confirm. Model and effort choices submit immediately, including preferences for an inactive target backend without switching the coordinator. Missing backends remain disabled; unavailable native catalogs and model-specific effort controls are explicit rather than generated from prompts.\n- Bind immutable choices to the original owner, device, thread, working context and configuration revision. Serialize native changes and persistence with affected command admission, invalidate stale menus, and acknowledge only confirmed changes. Bound snapshot and retry receipts, paginate choices with recursive card-node and byte accounting, and preserve parameterized text-command semantics and older-peer fallbacks. No backend installation, credential mutation, live deployment or inference is performed to build menus.\n\n### Changed\n- Use native structured model and effort metadata, including grouped ACP choices, model-specific Pi thinking levels, bounded AGY model rows, and capability-gated Claude control initialization. Keep configured selections distinct from native reports and defaults. Isolated metadata identities inherit policy resolved under the real thread ID, never share coordinator/Worker pointers, and clean up only their own confirmed-exited data. Claude model updates also maintain its legacy preference field.\n- Bound ACP control requests without timing out normal inference, preserve opaque native IDs, refresh Claude capabilities per process, and reject incompatible model/effort changes rather than silently changing a second preference. Release known temporary ACP sessions before transport shutdown and defer own-pointer cleanup after a timed-out query until settlement and confirmed exit."},{"version":"1.6.151","text":"### 委派快照与测试更稳\n- 减少普通仓库和子模块委派快照的重复 Git 查询,继续检查文件变化、仓库边界和成果回收安全,不跨任务复用旧文件状态。\n- 限制真实 Git 测试同时占用的资源,并修复断言失败后收尾卡住的问题;不改变 Worker 的启动、退出和 Git 命令超时。","changes":[{"topic":"delegation","title":"委派任务","text":"减少普通仓库和子模块委派快照的重复 Git 查询,继续检查文件变化、仓库边界和成果回收安全,不跨任务复用旧文件状态。"},{"topic":"delegation","title":"委派任务","text":"限制真实 Git 测试同时占用的资源,并修复断言失败后收尾卡住的问题;不改变 Worker 的启动、退出和 Git 命令超时。"}],"details":"### Changed\n- Reduce delegated Git checkpoint subprocesses by reading paths, conflict stages, and hidden-entry flags together from each private index. Resolve the source index path once per pass and audit identical content-addressed trees once per capture; retain both full working-file passes, source HEAD/index rechecks, copied-index timestamps, nested-repository validation, and independent checkout byte audits. Reject existing zero-byte indexes instead of treating corrupt metadata as missing; legitimate missing and serialized zero-entry indexes remain supported. No state is cached across captures and Git deadlines are unchanged.\n- Bound real Git integration suites to one isolated process alongside at most two lightweight test threads. Keep ordinary test and hook deadlines unchanged; give historical delivery the same explicit 30-second budget as other Git suites. Release controlled lifecycle gates in finally blocks, cover slow collection and early assertion failure, and guard subprocess counts against regressions."},{"version":"1.6.150","text":"### Codex Banked Reset 增加提醒\n- Codex 的 Banked Reset 数量比上一次有效检查增加时发送提醒,显示前后数量及增加量;减少或不变不提醒,减少后再增长也能正常提醒。\n- 复用启动及每小时的额度检查,首次检查、重启或切换账号只建立基线;读不到数量不会当成零,也不会自动使用重置次数,旧版仍保持原有提醒。\n- 提醒已送达但确认消息丢失时,CLI 重连会确认原来的卡片,不会为同一次增长重复发送提醒。","changes":[{"topic":"maintenance-notices","title":"更新与额度提醒","text":"Codex 的 Banked Reset 数量比上一次有效检查增加时发送提醒,显示前后数量及增加量;减少或不变不提醒,减少后再增长也能正常提醒。"},{"topic":"maintenance-notices","title":"更新与额度提醒","text":"复用启动及每小时的额度检查,首次检查、重启或切换账号只建立基线;读不到数量不会当成零,也不会自动使用重置次数,旧版仍保持原有提醒。"},{"topic":"maintenance-notices","title":"更新与额度提醒","text":"提醒已送达但确认消息丢失时,CLI 重连会确认原来的卡片,不会为同一次增长重复发送提醒。"}],"details":"### Added\n- Notify about Codex Banked Reset balance increases using the existing independent startup/hourly status read and native `rateLimitResetCredits.availableCount`. First observations and account switches are silent; compare each valid count with the previous valid count for that account, not a historical maximum. Decreases update the baseline without notifying, and missing or invalid fields remain unknown rather than zero.\n- Reuse standalone, notification-only quota cards and delivery acknowledgements, with previous/current balances and the increase. Keep banked-credit events separate from weekly quota delivery suppression, cancel pending notices on observed consumption/account changes, and retry only the latest pending event. Retain up to 1,000 banked delivery receipts in Router memory until notice expiry, including in-flight reservations, so lost-ACK retries across CLI reconnects revalidate ownership and acknowledge the existing card instead of sending duplicates; action bindings remain connection-scoped. A new additive `bankedResetReminder` capability prevents old Routers from mislabeling banked-credit notices. No extra native read, model request, credit consumption, expiry warning, or persisted balance is introduced."},{"version":"1.6.149","text":"### 更多工具调用有简短说明\n- AGY 的工具调用显示它自带的本次调用摘要;Codex 的读取文件、搜索和列目录命令也能显示简短动作说明,无法识别时仍保持简洁,不把整个任务的阶段摘要套到工具上。\n- 说明复用原有工具栏,不增加卡片元素或额外模型调用;晚到的成功、失败结果仍更新原行的状态颜色。\n- Codex 网页工具的展开详情可以查看搜索、打开网页和页内查找的结果标题、来源链接和摘要;预览最多五条,省略数量会明确提示,不再把缺少结果字段误显示为空结果。\n- 修复 AGY 部分搜索调用丢失搜索词,以及非文本工具输出被忽略的问题;网页结果复用原有详情区域,不增加卡片元素。\n- 网页摘要不会因提到本地图片路径而自动上传图片,兼容旧版的文本预览也保持为纯文本;AGY 工具失败时保留错误原因和结构化输出。","changes":[{"topic":"tool-cards","title":"工具卡片","text":"AGY 的工具调用显示它自带的本次调用摘要;Codex 的读取文件、搜索和列目录命令也能显示简短动作说明,无法识别时仍保持简洁,不把整个任务的阶段摘要套到工具上。"},{"topic":"tool-cards","title":"工具卡片","text":"说明复用原有工具栏,不增加卡片元素或额外模型调用;晚到的成功、失败结果仍更新原行的状态颜色。"},{"topic":"tool-cards","title":"工具卡片","text":"Codex 网页工具的展开详情可以查看搜索、打开网页和页内查找的结果标题、来源链接和摘要;预览最多五条,省略数量会明确提示,不再把缺少结果字段误显示为空结果。"},{"topic":"tool-cards","title":"工具卡片","text":"修复 AGY 部分搜索调用丢失搜索词,以及非文本工具输出被忽略的问题;网页结果复用原有详情区域,不增加卡片元素。"},{"topic":"tool-cards","title":"工具卡片","text":"网页摘要不会因提到本地图片路径而自动上传图片,兼容旧版的文本预览也保持为纯文本;AGY 工具失败时保留错误原因和结构化输出。"}],"details":"### Changed\n- Forward AGY's native per-call `toolSummary` and fallback `toolAction` as tool descriptions while preserving explicit descriptions and titles. Terminal results keep the original invocation identity and do not synthesize new calls or copy execution-wide activity into labels.\n- Describe Codex's structured `commandActions` as file reads, searches, and directory listings. Use file basenames only, omit raw commands and search arguments, and leave absent, unknown, or partly unknown action sets unlabeled. Reserve omitted-label counts within the existing 60-character heading budget. Reuse existing description fields and compact headings without additional model calls, protocol changes, or card elements.\n- Preserve Codex's native web search, open-page, and find-in-page actions and result entries instead of reporting empty output. Foreground tools show up to five bounded titles, source links, and snippets in the existing output node, with explicit omitted-entry counts and distinct missing, unsupported, and empty-result notices. An additive optional result preview retains a plaintext fallback for older Routers; source links are revalidated and result text is rendered literally. Delayed result updates keep the original invocation slot and recursive pagination limits.\n- Accept AGY's native lowercase `query` as well as legacy `Query`, and preserve non-string tool outputs as JSON alongside any supplied failure explanation instead of discarding either. Add web-result passthrough regressions for Claude, shared ACP backends (OpenCode, Kimi, ZCode, DSH), and Pi without assuming unavailable native samples were verified.\n- Treat structured web previews and recognized web-tool results as display data, not local-image instructions; repeated results retain their origin until an explicit new call reuses the ID. Ordinary local-tool image forwarding remains available. Prefix every native fallback field so untrusted snippets cannot close older Routers' fixed code fences."},{"version":"1.6.148","text":"### 工具状态颜色更直观\n- 工具调用统一使用小圆点:成功绿色、执行中蓝色、失败红色,去掉沙漏和叉号;结果晚到仍在原行更新颜色,不增加卡片元素。","changes":[{"topic":"tool-cards","title":"工具卡片","text":"工具调用统一使用小圆点:成功绿色、执行中蓝色、失败红色,去掉沙漏和叉号;结果晚到仍在原行更新颜色,不增加卡片元素。"}],"details":"### Changed\n- Use a consistent dot in every foreground tool heading: green after success, blue while awaiting a result, and red after failure. Preserve per-call labels, explicit expanded status text, fixed-slot asynchronous updates, and recursive card-node counts without adding elements."},{"version":"1.6.147","text":"### 工具调用说明更清楚\n- 工具名后优先显示后端提供的本次调用说明或标题,没有说明时显示文件名等明确标签;不重复工具名,也不把整个任务的阶段摘要套到每条工具上。\n- 调用说明和晚到的成功、失败结果仍更新原来的工具栏,不增加卡片元素;没有说明的后端保持简洁显示。","changes":[{"topic":"tool-cards","title":"工具卡片","text":"工具名后优先显示后端提供的本次调用说明或标题,没有说明时显示文件名等明确标签;不重复工具名,也不把整个任务的阶段摘要套到每条工具上。"},{"topic":"tool-cards","title":"工具卡片","text":"调用说明和晚到的成功、失败结果仍更新原来的工具栏,不增加卡片元素;没有说明的后端保持简洁显示。"}],"details":"### Changed\n- Prefer meaningful backend-provided per-call descriptions and titles in foreground tool headings, falling back to file basenames and omitting redundant tool-name labels. Preserve ACP call/update titles and explicit AGY/Pi parameter labels that tool mapping previously discarded; never synthesize a call to refresh a terminal-result title.\n- Carry optional tool labels over the existing version-1 stream without new capabilities or model calls. Keep execution-wide activity separate, retain fixed-slot asynchronous result updates, and verify unchanged recursive card-node budgets through pagination and shrink."},{"version":"1.6.146","text":"### 工具栏样式更统一清爽\n- Bash 和文件工具统一显示状态符号、工具名和简短说明:成功用浅灰小点,失败用浅灰普通叉,等待结果用沙漏,不再堆叠彩色状态标签。\n- 完整工具编号、参数、输出和修改预览保留在展开详情里;长回复继续自动分片,结果晚到也会更新原来的工具栏。","changes":[{"topic":"tool-cards","title":"工具卡片","text":"Bash 和文件工具统一显示状态符号、工具名和简短说明:成功用浅灰小点,失败用浅灰普通叉,等待结果用沙漏,不再堆叠彩色状态标签。"},{"topic":"tool-cards","title":"工具卡片","text":"完整工具编号、参数、输出和修改预览保留在展开详情里;长回复继续自动分片,结果晚到也会更新原来的工具栏。"}],"details":"### Changed\n- Use one compact foreground tool heading for Bash and other tools: a gray success dot, pending hourglass, or gray failure cross, followed by the tool name and an optional bounded public description or file basename. Keep raw commands out of headings and move full tool IDs and explicit status labels into the existing expanded details.\n- Preserve input, result, diff previews, stable call identities, and existing cross-card cleanup. Verify recursive tagged-node counts at the card boundary through delayed results, activity tails, and completion controls; no multi-call aggregation, execution, or wire-protocol change."},{"version":"1.6.145","text":"### 工具调用反馈更紧凑\n- 同一次工具调用和结果合为一条折叠栏,完成后直接更新成功或失败状态,减少长回复中的滚动。\n- 展开仍可查看参数、输出和代码修改预览;不同工具调用继续分开显示,错误状态保持醒目。","changes":[{"topic":"tool-cards","title":"工具卡片","text":"同一次工具调用和结果合为一条折叠栏,完成后直接更新成功或失败状态,减少长回复中的滚动。"},{"topic":"tool-cards","title":"工具卡片","text":"展开仍可查看参数、输出和代码修改预览;不同工具调用继续分开显示,错误状态保持醒目。"}],"details":"### Changed\n- Render each foreground tool call and its matching result as one collapsed row, updating its status in place while retaining bounded input, output, and per-file diff previews. Keep later text and worker slots stable; preserve unmatched results without guessing a pairing.\n- Keep independent calls separate, including adapter ID reuse after a completed invocation. Remove previous tool copies before cross-card moves, including still-active and surplus pages, preserving worker context controls and retryable updates. Backend execution, protocol version, and approval flows are unchanged."},{"version":"1.6.144","text":"### 随时看清 Agent 正在做什么\n- 主 Agent 在最新回复卡片底部显示当前活动,子 Agent 在自己的标题下显示;长回复翻页后仍能看到最新进度。\n- 显示后端提供的公开进度、计划步骤和工具说明,等待输入或任务结束时切换状态;不展示原始思考,也不猜测完成百分比。","changes":[{"topic":"agent-activity","title":"运行进度","text":"主 Agent 在最新回复卡片底部显示当前活动,子 Agent 在自己的标题下显示;长回复翻页后仍能看到最新进度。"},{"topic":"agent-activity","title":"运行进度","text":"显示后端提供的公开进度、计划步骤和工具说明,等待输入或任务结束时切换状态;不展示原始思考,也不猜测完成百分比。"}],"details":"### Added\n- Show bounded public activity at the tail of the latest active coordinator card and below each managed worker's identity. Separate explicit Codex commentary and public reasoning summaries, public assistant updates, plan steps, and safe tool descriptions from answer text; never promote raw thinking or estimate completion percentages.\n- Negotiate optional activity progress without a protocol-version change. Coalesce snapshots, preserve worker-result publication barriers, prioritize input and terminal states, discard late events, and leave older peers on their existing presentation."},{"version":"1.6.143","text":"### Codex 用量查询等待时间延长\n- 将 `/status` 查询 Codex 用量的等待时间从 5 秒延长至 10 秒,减少响应较慢时缺少用量信息的情况。","changes":[{"topic":"codex-usage","title":"Codex 用量","text":"将 `/status` 查询 Codex 用量的等待时间从 5 秒延长至 10 秒,减少响应较慢时缺少用量信息的情况。"}],"details":"### Fixed\n- Increase the Codex account-usage RPC timeout from five to ten seconds for `/status`, without adding retries or changing failure handling."},{"version":"1.6.142","text":"### 同一后端也能分工协作\n- 主 Agent 现在也可调用同一后端的独立 Worker,不共用主会话;Git 项目仍可并行分工,成果仍需明确合并或保留。","changes":[{"topic":"delegation","title":"委派任务","text":"主 Agent 现在也可调用同一后端的独立 Worker,不共用主会话;Git 项目仍可并行分工,成果仍需明确合并或保留。"}],"details":"### Added\n- Allow unrestricted coordinators to delegate to their own backend through independent managed worker sessions. Preserve synthetic lane identities, isolated Git checkouts, shared-directory FIFO scheduling, explicit artifact integration, context-reset ownership, and existing task/concurrency budgets.\n\n### Changed\n- Report the coordinator backend's worker eligibility in discovery and status using the same admission policy, and align injected tool instructions. Do not advertise sandbox-restricted workers as eligible in the delegation menu. Keep restricted coordinators and read_only requests ineligible; native backend subagents and the Router wire protocol remain unchanged."},{"version":"1.6.141","text":"### 含子仓库的项目也能委派\n- 已初始化的 Git 子模块和嵌套仓库现在可以参与委派,包含未提交修改;应用成果时保留原有会话、仓库提交和暂存状态。\n- 文件与目录互换不再误报;未初始化的子模块不阻止审阅其他代码,真正不支持的文件会显示具体路径和类型。","changes":[{"topic":"delegation","title":"委派任务","text":"已初始化的 Git 子模块和嵌套仓库现在可以参与委派,包含未提交修改;应用成果时保留原有会话、仓库提交和暂存状态。"},{"topic":"delegation","title":"委派任务","text":"文件与目录互换不再误报;未初始化的子模块不阻止审阅其他代码,真正不支持的文件会显示具体路径和类型。"}],"details":"### Fixed\n- Include initialized local submodules and embedded repositories in private delegated snapshots, with staged, unstaged, and nonignored files captured through their own temporary indexes. Stream local Git objects without remote fetching or a repository-size cap; workers receive ordinary files rather than nested Git metadata or histories.\n- Apply nested working-file changes through explicit artifact integration while preserving all source HEADs, indexes, and gitlinks. Include nested state in delivery revisions, reject changed repository identities and boundary replacements, preserve uncertain worker-created Git metadata for manual recovery, and keep uninitialized submodules empty without blocking unrelated work.\n- Allow ordinary file/directory replacements and identify unsupported filesystem entries by repository-relative path and type. Cover nested snapshots, conflicts, state preservation, streamed transfer, artifact delivery, and guarded checkout reclamation/reuse with real temporary Git repositories.\n- Preserve warm index stat caches and the original index timestamp so racy-clean detection still catches same-size edits; reuse completed local object transfers within each stable capture. Reject ancestor worktrees, external nested Git metadata, nested-local command filters, and partial-clone hydration. Keep unsupported no-change metadata pending until explicit retention, and wait for deterministic Git lifecycle signals in cancellation tests.\n- Receive nested packs in a per-transfer quarantine and publish complete packs with indexes last. Clean failed and timed-out transfers after both processes exit without sweeping other operations. Discover embedded repositories exposed by gitlink replacements and support initialized submodules owned by linked-worktree metadata stores."},{"version":"1.6.140","text":"### 大项目委派与异常恢复更稳妥\n- 准备工作区或收集成果较慢时,不再误判后台进程异常、锁住整个项目;取消任务后也不会偷偷启动 Worker。\n- 无法完整读取被 Git 标记隐藏的修改时,会明确提示并保留文件,不再把遗漏的修改当成已完整交付。","changes":[{"topic":"delegation","title":"委派任务","text":"准备工作区或收集成果较慢时,不再误判后台进程异常、锁住整个项目;取消任务后也不会偷偷启动 Worker。"},{"topic":"delegation","title":"委派任务","text":"无法完整读取被 Git 标记隐藏的修改时,会明确提示并保留文件,不再把遗漏的修改当成已完整交付。"}],"details":"### Fixed\n- Reject assume-unchanged and skip-worktree index entries before capturing delegated Git checkpoints. Do not silently omit hidden edits, reinterpret absent sparse files as deletions, or modify the source index; preserve unresolved worker files for manual recovery.\n- Keep managed Git baseline capture, checkout preparation, and repository-lock waits outside the native worker startup deadline. Await owned mutations before releasing execution capacity, and prevent late worker startup after cancellation.\n- Bound accepted Git delegation and cancellation response waits below the tool adapter's timeout. Return the existing task ID and explicit pending status for later polling without aborting owned operations, pretending cleanup finished, or encouraging duplicate submission.\n- Separate confirmed process shutdown from artifact collection. Slow collection no longer quarantines the source workspace or leaks global worker slots; collection and lane-persistence failures retain the affected lane while releasing unrelated capacity after Git operations settle. Preserve native-exit quarantine, individual Git command deadlines, non-Git FIFO scheduling, and old-peer compatibility."},{"version":"1.6.139","text":"### 大仓库也能正常委派任务\n- 取消按仓库总大小和文件数量拒绝子任务的限制,大型项目也可执行委派、合并成果并再次使用工作目录。","changes":[{"topic":"delegation","title":"委派任务","text":"取消按仓库总大小和文件数量拒绝子任务的限制,大型项目也可执行委派、合并成果并再次使用工作目录。"}],"details":"### Fixed\n- Remove the fixed 128 MiB repository-size and 10,000-file limits from delegated Git input snapshots, filtered trees, artifact collection, and checkout reclamation verification. Large repositories keep their complete staged, unstaged, and nonignored untracked input without a replacement size configuration.\n- Preserve path and entry validation, artifact ownership and reference checks, streamed byte hashing before reclamation, parent index and branch isolation, and existing Git command deadlines and output-buffer limits. Add regression coverage for large committed and untracked files and complete artifact integration, reclamation, and reuse beyond the former limits."},{"version":"1.6.138","text":"### 委派收尾与会话恢复更可靠\n- 子任务成果已处理完时,不再因为其他会话忙碌而误报收尾失败或反复要求处理。\n- 重试旧卡片的上下文清理时,不再影响后来创建的 Worker 会话;状态不明的旧会话仍会保留。\n- 子任务在准备工作区之前启动失败时,可继续复用原 Worker;工作区状态不确定时仍保留安全保护。","changes":[{"topic":"delegation","title":"委派任务","text":"子任务成果已处理完时,不再因为其他会话忙碌而误报收尾失败或反复要求处理。"},{"topic":"delegation","title":"委派任务","text":"重试旧卡片的上下文清理时,不再影响后来创建的 Worker 会话;状态不明的旧会话仍会保留。"},{"topic":"delegation","title":"委派任务","text":"子任务在准备工作区之前启动失败时,可继续复用原 Worker;工作区状态不确定时仍保留安全保护。"}],"details":"### Fixed\n- Validate settled worker artifact receipts independently of source-workspace contention, avoiding spurious closeout failures and extra coordinator turns. Keep ownership, reference, recovery, cancellation, and receipt-integrity checks; history reconciliation still requires the source lease.\n- Keep a superseded shared-directory lane non-reusable after a context-clear retry, without deleting another worker's conversation. Persist pooling mode for independent Git lanes and preserve ambiguous legacy duplicate contexts instead of scheduling automatic deletion.\n- Return reused Git lanes to ready after failures before checkout preparation starts. Continue preserving uncertain prepared lanes, and distinguish executor setup failures from checkout failures in recovery diagnostics."},{"version":"1.6.137","text":"### 单独清理子任务上下文\n- 子任务结束后,无论成功还是失败,都可在卡片上点击 Clear context,让该 Worker 下次从新会话开始,不影响主 Agent、其他 Worker 或代码成果。\n- 清理收到本机确认后才显示成功;运行中的任务和过期卡片不会误清新会话,失败可重试,不会自动重跑任务。","changes":[{"topic":"delegation","title":"委派任务","text":"子任务结束后,无论成功还是失败,都可在卡片上点击 Clear context,让该 Worker 下次从新会话开始,不影响主 Agent、其他 Worker 或代码成果。"},{"topic":"delegation","title":"委派任务","text":"清理收到本机确认后才显示成功;运行中的任务和过期卡片不会误清新会话,失败可重试,不会自动重跑任务。"}],"details":"### Added\n- Add an owner-bound Clear context control outside delegated Worker card details after successful or failed execution. Reset only the exact idle lane's native continuation, retaining workspaces, artifacts, archived transcripts, authentication, and settings without replaying the task or resetting the coordinator.\n- Negotiate optional workerContextReset support and require CLI acknowledgement before confirming success. Persist reset intents and context epochs, serialize reset with lane acquisition, reject stale or unsafe targets, and permit explicit retries after interrupted resets. Keep controls consistent across streaming, continuation cards, and thread-footer refreshes with a bounded ephemeral Router cache; legacy peers remain compatible."},{"version":"1.6.136","text":"### 委派成果自动收尾\n- 主 Agent 回复完成前,自动检查子任务成果是否已交付或明确保留;有遗漏会继续处理,最多补两轮。\n- 仍无法处理的成果会明确列出并保留,不再把“任务执行完了”当作“代码已交付”,也不会自动丢弃文件。","changes":[{"topic":"delegation","title":"委派任务","text":"主 Agent 回复完成前,自动检查子任务成果是否已交付或明确保留;有遗漏会继续处理,最多补两轮。"},{"topic":"delegation","title":"委派任务","text":"仍无法处理的成果会明确列出并保留,不再把“任务执行完了”当作“代码已交付”,也不会自动丢弃文件。"}],"details":"### Added\n- Enforce artifact closeout before successful coordinator completion. Drain accepted tasks and tool calls, reconcile historical delivery under existing ownership guards, then inspect durable receipts rather than cached results. Pending changes, missing or invalid receipts, failed collection, and unretained recovery state prevent success; verified no-change, applied, and deliberately retained outcomes need no further decision.\n- Resume the same coordinator session for at most two artifact-closeout rounds per request, combining unread worker results when available. Preserve attachments, result acknowledgement, approval/input, model recovery, and cancellation boundaries; new workers do not reset the budget. An unresolved final check returns bounded task IDs and artifact references as a failure, pausing queued execution while preserving recoverable output. No new wire messages, implicit merging, automatic cross-request replay, or non-Git lifecycle changes."},{"version":"1.6.135","text":"### 工作区自动回收\n- 无文件改动的成功任务,以及已确认合并的成果,会自动回收安全的 Worker 工作目录;保留上下文,下次在原路径重建并读取最新代码。\n- 有未交付成果、遗留文件或状态不明的工作目录继续保留;清理失败不影响任务结果,也不会强删文件。\n- 成果提交已进入主工作分支历史时,会自动确认交付;之后主分支撤回改动也不会重新挂起旧任务,遗留文件仍受安全检查保护。","changes":[{"topic":"delegation","title":"委派任务","text":"无文件改动的成功任务,以及已确认合并的成果,会自动回收安全的 Worker 工作目录;保留上下文,下次在原路径重建并读取最新代码。"},{"topic":"delegation","title":"委派任务","text":"有未交付成果、遗留文件或状态不明的工作目录继续保留;清理失败不影响任务结果,也不会强删文件。"},{"topic":"delegation","title":"委派任务","text":"成果提交已进入主工作分支历史时,会自动确认交付;之后主分支撤回改动也不会重新挂起旧任务,遗留文件仍受安全检查保护。"}],"details":"### Added\n- Automatically reclaim verified delegated Git checkout directories after successful no-change tasks or durable artifact application. Preserve native conversation pointers, stable lane paths, immutable artifacts, and private input/output/history references; recreate absent, unregistered owned paths from fresh delivery input when the lane is reused.\n- Persist present/reclaiming/reclaimed checkout state and exact output receipts. Resolve interrupted intents only from verified intact checkouts or confirmed absent/unregistered paths; never infer ownership from a missing legacy directory, overwrite occupied reclaimed paths, prune registrations, or sweep historical workspaces.\n- Recognize successful pending worker outcomes as historically delivered when their recorded artifact snapshot commit is an ancestor of delivery HEAD, including after a later revert. Persist the observed HEAD and repair interrupted pending-marker clears; reconcile guarded inspection, ready-lane admission, and idle turn closure without content-subset heuristics, automatic merges, staging, commits, or changes to patch-only apply. Keep replacement-object bypass, owner/ref checks, fail-soft errors, and independent safe-reclamation verification.\n\n### Changed\n- Independently bound and hash actual tracked bytes, modes, and symlink targets before checkout deletion, accounting for ignored files, extra directories, unknown entries, and Git index flags. Preserve pending, retained, failed/cancelled, locked, or unresolved recovery workspaces. Transformed bytes that cannot be proven equivalent fail closed.\n- Serialize lane lifecycle and Git worktree metadata operations within the CLI process. Await optional reclamation outside the worker-stop deadline before marking a lane ready; cleanup failure does not change a successful task or artifact application. Native backend execution, non-Git FIFO scheduling, and Router protocol remain unchanged.\n- Keep full byte verification outside the shared repository guard so independent lanes can start during a slow audit. Isolate a reused Git lane whose checkout preparation fails without discarding its existing native context; preserve lazy recovery of valid interrupted-removal receipts."},{"version":"1.6.134","text":"### 本阶段更新汇总(1.6.90~1.6.133)\n- 默认开启多 Agent 委派;Git 项目最多 5 个 Worker 隔离并行,成果由主 Agent 确认合并,非 Git 目录仍串行。\n- 新增 DSH 后端,支持模型与 effort 切换、上下文续接,以及在 /status 中查询余额。\n- 支持接收最大 20 MiB 的文件,提取文本文件、文字型 PDF、DOCX 和 XLSX 内容;设备授权后,上传文件再发送处理指令即可。\n- 优化手机端的进度和结果展示,支持 Markdown 富文本;Worker 活动详情和后台任务结果默认折叠。\n- 主 Agent 和子 Agent 卡片底部都用小号灰字显示各自的模型与 effort,方便了解本次任务的执行配置。\n- 新增中文升级摘要与 Codex Reset 额度提醒;跨版本升级时按功能汇总变化,重启和升级后保留已确认送达的提醒记录。","changes":[{"topic":"delegation","title":"委派任务","text":"默认开启多 Agent 委派;Git 项目最多 5 个 Worker 隔离并行,成果由主 Agent 确认合并,非 Git 目录仍串行。"},{"topic":"dsh-backend","title":"DSH 后端","text":"新增 DSH 后端,支持模型与 effort 切换、上下文续接,以及在 /status 中查询余额。"},{"topic":"file-attachments","title":"文件附件","text":"支持接收最大 20 MiB 的文件,提取文本文件、文字型 PDF、DOCX 和 XLSX 内容;设备授权后,上传文件再发送处理指令即可。"},{"topic":"worker-cards","title":"任务卡片","text":"优化手机端的进度和结果展示,支持 Markdown 富文本;Worker 活动详情和后台任务结果默认折叠。"},{"topic":"execution-metadata","title":"执行信息","text":"主 Agent 和子 Agent 卡片底部都用小号灰字显示各自的模型与 effort,方便了解本次任务的执行配置。"},{"topic":"maintenance-notices","title":"更新与额度提醒","text":"新增中文升级摘要与 Codex Reset 额度提醒;跨版本升级时按功能汇总变化,重启和升级后保留已确认送达的提醒记录。"}],"details":"This stage summary consolidates confirmed source changes from 1.6.90 through 1.6.133, including Git-confirmed changes whose per-version notes were missing. It replaces the available entries in that range, not Git history, and is not a complete npm publication ledger. Version 1.6.134 reorganizes release documents, synchronizes package versions, and permits up to six summary bullets in build-time and bundled-artifact validation; backend execution and Router behavior are unchanged.\n\n### Added\n- Integrate DeepSeek Harness (DSH) through its native persistent ACP server, with model and reasoning-effort controls, cancellation, permission prompts, context reporting when available, and isolated coordinator/worker sessions. Keep native capability boundaries: images require advertised support, and unsupported interactive slash commands, plan mode, and elicitation do not fall back to another backend.\n- Preserve DSH session pointers across backend switches and restarts. Recover explicitly non-resumable sessions with an honest fresh-session notice; retain pointers on authentication, provider, network, rate-limit, timeout, or directory-mismatch failures. Summarize-then-reset compaction uses a private, durable handoff rather than claiming native transcript compaction, and refuses to summarize unavailable original context.\n- Show DSH official recharge and bonus wallet balances in `/status` when native account authentication makes them available. Retain native precision and currency, distinguish balances from token usage or plan quota, and use a short-lived account-query process without creating a model turn or changing the ACP conversation.\n- Receive file attachments up to 20 MiB through explicit device enrollment and a same-Router HTTPS download path. Transfer file bytes from Feishu to a private Router spool and CLI staging area; WebSocket messages contain only bounded references, hashes, sizes, and authorization metadata. Enforce authenticated device ownership, actual byte limits, hashes, deadlines, storage quotas, and explicit failure feedback without weakening legacy text/image support.\n- Extract bounded previews from text/code, CSV, JSON, YAML, textual PDF, DOCX main-body text, and XLSX cells, retaining page/sheet/cell provenance. Keep parsing off the control event loop, bound expanded archives and output, and never execute macros or formulas. OCR, protected documents, legacy Office formats, and general archive extraction remain unsupported; saved, parsed, partial, and unsupported outcomes stay distinct.\n- Stage files for a subsequent instruction or a reply to their status card, including instructions with images, rather than starting a model task on file upload alone. Pin queued attachments, bind references to the admitted device/thread/directory, expose `/files` and `/files clear`, and preserve active references during cleanup. Backend tools retain their normal permissions when reading original or preview paths outside the project.\n- Persist isolated delegated-worker lanes separately from direct backend sessions, retaining only each lane's own earlier delegated context. Reuse requires confirmed process exit and valid session state; directory changes invalidate the old workspace generation, and failed lane cleanup remains retryable rather than silently freeing uncertain ownership.\n- Accept multiple independent delegated tasks in one coordinator request, with individual cancellation, queued status, bounded queue waits, cumulative admission limits, and automatic collection of all results. Retain source-workspace ownership while the queue drains; queued work has no execution timestamp or progress card before it starts.\n- Run Git workers in reusable per-lane worktrees with bounded snapshots of staged, unstaged, and nonignored untracked input. Refresh every detached task checkout to an explicit baseline while preserving native lane identity. Non-Git directories use code-enforced FIFO serial scheduling and are never initialized as Git repositories implicitly; worktrees are not process sandboxes.\n- Preserve immutable worker artifacts under private Git references and expose revision-guarded inspection, integration, or retention. Preflight conflicts in a separate recovery worktree; applying changes never stages, commits, or pushes the delivery workspace. Pending artifacts or unknown dirty files block lane reuse. File application is not atomic: preserve before/target snapshots and a durable pending receipt for manual recovery after an incomplete apply, and validate captured tree limits after Git filters and both rename endpoints against the selected-directory scope.\n- Attach bounded execution-scoped model and reasoning-effort metadata to AI responses, terminal recovery, and each delegated worker's progress/results. Distinguish backend reports, configured selections, defaults, and unavailable values without extra model requests. Keep launch preferences stable, retain final worker snapshots before cleanup, and never substitute coordinator settings or attribute a model to an unstarted queued task.\n- Show compact gray model/effort notes below Completed on main replies and outside collapsed worker details. Preserve metadata through long-output splitting, thread-button refresh, and optional protocol-v1 fields, while legacy peers and local control commands retain their existing display.\n- Add standalone CLI upgrade notices with cumulative bundled notes, offline delivery, negotiated capabilities, and a silent baseline on first adoption. Advance notification progress only after acknowledged delivery, retain skipped-upgrade ranges, and keep maintenance cards separate from thread selection and task routing.\n- Add hourly, status-only Codex weekly-quota inspection and notification-only reminders using existing file-backed ChatGPT credentials. Do not send model prompts, create user threads, refresh credentials, or probe other backends. Missing/expired credentials, unsupported native APIs, and failed samples remain unavailable evidence; the experimental native token-handoff API is not a compatibility guarantee.\n\n### Changed\n- Enable managed delegation by default for new and existing threads with no saved preference; explicit off remains off through upgrades, context resets, backend switches, and restarts. Exposing delegation tools does not automatically launch workers.\n- Restrict managed delegation to a different backend without changing native backend subagent tools. Unrestricted coordinators launch unrestricted workers; sandboxed coordinators have no eligible cross-backend targets until policy translation is supported. Discovery and launch enforce the same policy.\n- Raise the shared starting/running worker limit from three to five. Git-backed requests can occupy five isolated execution slots; additional accepted tasks remain queued, non-Git requests still run one worker at a time, and the cumulative 12-task limit spans coordinator continuations without refunds for failures or cancellation.\n- Use real worker tool activity for liveness timeouts, with separate idle and tool-idle deadlines, rather than treating a quiet stdout stream as proof that a worker stalled. UI text and card heartbeats do not extend execution liveness.\n- Enrich the local CLI's Linux/macOS startup PATH with verified runtime and conventional installation directories, preserving inherited precedence. Use the same command resolution for startup checks, backend menus, delegation, and auxiliary queries, honor explicit executable overrides, and preserve ZCode's native empty-command discovery without falling back from a nonempty invalid override. Valid existing services do not need reinstallation; startup does not source shell profiles, install tools, or rewrite their service files.\n- Render nested/live worker activity and results as rich Markdown, with independent per-worker text, elapsed/tool activity, consistent icons, and compact mobile layouts. Keep detailed activity collapsed, separate result labels from worker Markdown, preserve stable update slots and card-wide table limits, and make the delegation status menu easier to scan.\n- Label standalone task notifications as Background task, retain their originating thread and task identity, collapse result/output-path details by default, and keep short failures visible. This presentation is separate from foreground replies and managed-worker cards.\n- Show thread/workspace headers on initial streaming and continuation cards before final completion, preserving reply provenance rather than waiting for the terminal card update.\n- Bundle concise Chinese user summaries alongside English technical details at build time. Validate matching nonempty current-version entries, one short heading and one to six single-line user bullets, stable feature tags/titles, and bounded package payloads; never fetch, translate, or summarize release notes with a model at runtime. Version 1.6.134 raises the per-release bullet limit from three to six while retaining the 2 KiB summary budget.\n- Aggregate the entire pending device-upgrade range by feature, removing exact duplicate items only. Keep available summaries and technical details collapsed and paged, report bounded-overview omissions, and preserve legacy-peer fallback, first-adoption silence, and protocol version 1. This release represents the consolidated 1.6.90-1.6.133 range with the 1.6.134 stage summary rather than reconstructing a per-device subset of those changes.\n- Use the title \"Codex Reset\" with a target emoji and \"Weekly quota reset: 100%\". Explain why to send Codex a normal task without verification or activation steps, remove the sampling-disclaimer footer and redundant Dismiss button, and retain passive validated legacy callbacks. Eligibility requires two roughly hourly zero-usage observations with approximately seven days remaining and a deadline that advances with the sampling interval; it is a snapshot heuristic, not confirmation of a provider reset or a guarantee that one request starts a usage window.\n\n### Fixed\n- Validate incomplete or incompatible tool parameters before specialized card formatting, using bounded text or no-parameters fallbacks without interrupting later tool events or task completion.\n- Retry confirmed Feishu Markdown-parser failures as literal text, preserve that mode on later updates and thread-button refreshes, and retain table-limit fallback without treating unrelated failures as parse errors.\n- Require successful recovery-notice delivery before acknowledging reuse of a surviving card, avoid duplicate notices within a recovery round, and retain originating thread information through recovery and continuation cards.\n- Reset every backend's remote-cli session binding when a thread changes to a different normalized working directory, preserve backend-native history and thread preferences, and keep a same-directory selection a no-op.\n- Distinguish a deleted or inaccessible selected working directory from a missing backend executable, refuse fallback execution in another directory, and cover remaining executor and passthrough startup paths with actionable errors.\n- Refresh Codex's model catalog and idle app-server after a native CLI version change while preserving the conversation binding, and improve model-recovery card delivery without replaying accepted worker launches.\n- Retain bounded worker results through coordinator continuations and terminal failures without replaying the original request, attachments, or completed workers. Keep execution-scoped result acknowledgement separate from worker completion, suppress premature coordinator output while results are pending, and prevent stale worker progress from overwriting unrelated cards.\n- Deduplicate ACP tool updates and keep reasoning/thought chunks out of answer text, final output, and delegated summaries for Kimi, OpenCode, ZCode, and DSH, while preserving separate native reasoning handling. Generate unique, paired Pi fallback tool IDs so concurrent tool calls cannot collide or report an unrelated result.\n- Filter bounded standalone Claude Code model-recognition stderr diagnostics for SDK queries and session-title generation, including delegated-worker streaming/results and slash-command error details. Preserve actual API/authentication errors, nonzero exits, assistant text, unknown sources, malformed records, and other backends; raw local stderr and telemetry behavior are unchanged.\n- Refuse ambiguous plain-text input when multiple workers are waiting, retain request-specific approval routing, and require confirmed cleanup before releasing occupied slots or workspace ownership.\n- Keep queued diagnostic records out of live terminal pruning, reconcile unfinished records as interrupted after restart without replaying tasks, and make retained worker-lane cleanup retryable.\n- Persist acknowledged Codex reminder suppression across CLI upgrades, restarts, reconnects, and credential refreshes using a private account/bucket fingerprint ledger. Only valid non-candidate observations rearm reminders; unavailable probes do not. Wait for accepted acknowledgement writes on shutdown, preserve corrupt/unavailable storage without affecting normal messaging, and do not claim exactly-once delivery across crashes.\n\n### Security\n- Disable DSH's official extra session-log attachment and OTel telemetry paths independently with a private temporary configuration overlay and the native telemetry-disable flag. Leave existing profiles, credentials, and other backends untouched and remove the overlay after process exit. Normal model requests still send task context to the selected provider and native local history remains; this is not an offline mode or a guarantee about third-party plugins.\n\n### Maintenance\n- Require staged-change and outgoing-commit privacy checks before publication, and sanitize documentation references without changing functional behavior.\n- Remove redundant presentation/fixture assertions while retaining behavioral regression coverage, clean temporary test fixtures reliably, and make ZCode discovery assertions portable across aliased filesystem paths."}]}
|
|
1
|
+
{"format":1,"firstVersion":"1.6.123","sections":[{"version":"1.6.265","text":"### 在原线程运行定时任务\n- CLI 和 Router 都升级到 1.6.265 后,八个后端默认支持定时任务。在原会话里说出要做的事、时间和时区,结果会发回创建者的原飞书线程。设备重新绑定后,旧绑定的任务停止运行。\n- 重启 CLI 后仍保留任务,执行时需要能继续原会话。离线期间错过的周期会跳过,无法确认是否已发送的那次不会重跑。\n- 用 `/schedule list` 查看任务,用 `/schedule cancel <id>` 取消后续执行。旧原生任务保留供手动清理,不会自动迁移。","changes":[{"topic":"native-schedules","title":"定时任务","text":"CLI 和 Router 都升级到 1.6.265 后,八个后端默认支持定时任务。在原会话里说出要做的事、时间和时区,结果会发回创建者的原飞书线程。设备重新绑定后,旧绑定的任务停止运行。"},{"topic":"native-schedules","title":"定时任务","text":"重启 CLI 后仍保留任务,执行时需要能继续原会话。离线期间错过的周期会跳过,无法确认是否已发送的那次不会重跑。"},{"topic":"native-schedules","title":"定时任务","text":"用 `/schedule list` 查看任务,用 `/schedule cancel <id>` 取消后续执行。旧原生任务保留供手动清理,不会自动迁移。"}],"details":"### Changed\n- Enable CLI-owned one-shot and five-field cron schedules by default for Claude Code, Codex, DSH, AGY, OpenCode, Kimi, Pi, and ZCode. The CLI handles timing, cancellation, startup recovery, and delivery retries without inference. Each occurrence targets the original conversation and its owner's Feishu thread.\n- Reload saved definitions after a CLI restart, skip cron firings missed offline, and suppress repeat dispatch when the previous dispatch outcome is unknown. Running a task still requires safe access to its original backend conversation.\n- Require a Router that confirms the current user and device binding epoch. Recheck this binding before dispatch and Feishu delivery.\n- Use the managed task ID to cancel future runs. Existing native tasks remain available for manual cleanup without migration."},{"version":"1.6.264","text":"### 修复 AGY 提问流程\n- AGY 提问时显示等待输入,直接在原线程回复即可继续。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"AGY 提问时显示等待输入,直接在原线程回复即可继续。"}],"details":"### Fixed\n- Keep AGY ACP foreground turns open while native questions await an answer. Route replies to the same session and require the native Stop receipt before completing the turn. Release queue admission when a failed foreground leaves the host fenced."},{"version":"1.6.263","text":"### 恢复 Claude 旧会话中的定时任务管理\n- 重连原 Claude 会话后,可以让 Agent 列出并删除选定的旧任务,再在同一会话创建新任务。","changes":[{"topic":"native-schedules","title":"定时任务","text":"重连原 Claude 会话后,可以让 Agent 列出并删除选定的旧任务,再在同一会话创建新任务。"}],"details":"### Fixed\n- Restore agent-requested cleanup and new schedule creation in the original managed Claude session after a restart. Install SDK admission hooks at initialization and reject unclassified resumed input without a current foreground command. Explicit Cron disables remain effective."},{"version":"1.6.262","text":"### 改善 Claude 和 AGY 定时任务创建\n- Claude 会话缺少所需定时工具时,直接提示原因,避免等待无法执行的创建操作。\n- 旧会话启动时禁用定时工具,会明确提示查看历史列表无法解锁清理;删除任务需要核对原生删除回执。\n- 修复 AGY 思考或查询状态较久时,尚未调用创建工具就超时失败的问题;取消和未确认任务仍保留保护。","changes":[{"topic":"native-schedules","title":"定时任务","text":"Claude 会话缺少所需定时工具时,直接提示原因,避免等待无法执行的创建操作。"},{"topic":"native-schedules","title":"定时任务","text":"旧会话启动时禁用定时工具,会明确提示查看历史列表无法解锁清理;删除任务需要核对原生删除回执。"},{"topic":"native-schedules","title":"定时任务","text":"修复 AGY 思考或查询状态较久时,尚未调用创建工具就超时失败的问题;取消和未确认任务仍保留保护。"}],"details":"### Fixed\n- Refuse Claude schedule creation when native initialization reports missing Cron tools or lifecycle support, before reserving schedule ownership or returning a native creation action.\n- Report when Claude started with Cron disabled. Reviewed cleanup requires a native inventory and an exact deletion receipt for each selected task.\n- Start the AGY same-turn native receipt deadline at the exact authorized tool dispatch, so model reasoning, tool discovery and operation polling do not expire an uninvoked action. Keep bounded post-dispatch waits and existing uncertainty protections.\n- Retire pending AGY actions on foreground completion, cancellation or ownership loss; a final inventory receipt cannot authorize a successor action after its turn ends."},{"version":"1.6.261","text":"### 更正 AGY 定时能力提示\n- 明确旧会话需主动清空、ACP 子任务不支持原生定时任务;保留历史与清理保护,不自动恢复任务。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"明确旧会话需主动清空、ACP 子任务不支持原生定时任务;保留历史与清理保护,不自动恢复任务。"}],"details":"### Fixed\n- Correct AGY scheduling capability text: legacy stream-json selections require explicit clear, and managed workers use ACP without native scheduling. This does not change execution, ownership or cleanup policy.\n\n### Tests\n- Replace obsolete AGY stream-json activity and internal-queue fixtures with ACP/hook terminal, cancellation and overlap regressions; exercise the real managed-child registration guard.\n- Canonicalize receipt fixture HOME through the native realpath API, expose bounded capture diagnostics in tests, and verify alias/replaced-root refusal before any prompt. Windows CI remains required for platform acceptance."},{"version":"1.6.260","text":"### AGY 统一会话通信与更多并行任务\n- 主会话和子任务统一使用 ACP,旧会话需主动清空后再开始;不会自动迁移历史或恢复定时任务。\n- 空闲会话可直接确认模型和思考强度,支持审批与图片输入;存在定时任务或未确认状态时保留保护限制。\n- 全局同时运行名额增至 20,单个 Git 请求最多同时运行 12 个任务;累计仍限 12 个,非 Git 目录仍串行执行。\n- 异常退出后,仅在确认旧进程组已退出时修复遗留钩子;未知归属保留并提示处理,子任务清空不会误报成功。\n- 工具拒绝请求或后台任务创建记录会阻止会话复用,避免把原生成功状态误当成安全续聊依据。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"主会话和子任务统一使用 ACP,旧会话需主动清空后再开始;不会自动迁移历史或恢复定时任务。"},{"topic":"agy-session","title":"AGY 会话","text":"空闲会话可直接确认模型和思考强度,支持审批与图片输入;存在定时任务或未确认状态时保留保护限制。"},{"topic":"delegation","title":"委派任务","text":"全局同时运行名额增至 20,单个 Git 请求最多同时运行 12 个任务;累计仍限 12 个,非 Git 目录仍串行执行。"},{"topic":"agy-session","title":"AGY 会话","text":"异常退出后,仅在确认旧进程组已退出时修复遗留钩子;未知归属保留并提示处理,子任务清空不会误报成功。"},{"topic":"agy-session","title":"AGY 会话","text":"工具拒绝请求或后台任务创建记录会阻止会话复用,避免把原生成功状态误当成安全续聊依据。"}],"details":"### Changed\n- Use ACP exclusively for AGY main and worker conversation execution. Remove persistent stream-json spawning, parsing and fallback; legacy selections require explicit clear. Keep native history, exact ownership and cleanup guards.\n- Confirm AGY live model/effort controls, route manual approvals, preserve native hook terminal errors, and record worker creation receipts before prompting. Loaded or reconfigured sessions cannot acquire fresh scheduling admission; uncertain outcomes remain refused.\n- Increase global occupied worker capacity to 20 and effective Git-request parallelism to 12. Keep the cumulative 12-task quota, serial non-Git workspaces, admission rejection at full capacity, FIFO, cancellation and exact exit/artifact slot accounting.\n- Forward AGY image inputs over ACP and retain bounded native informational helpers and explicit summarize-then-reset compaction. No automatic schedule restoration or exit-time handoff is added.\n\n### Fixed\n- Restore only proven-owned stale AGY hook overlays after exact prior owner/group exit, using per-HOME kernel exclusion and durable atomic restoration metadata. Preserve user hook edits and refuse unknown legacy or ambiguous ownership with actionable diagnostics.\n- Permanently fence AGY host continuity after any requested tool denial or observed background-task creation receipt, including DONE receipts followed by successful Stop. Older continuity receipts no longer grant worker reuse.\n- Keep worker-card Clear truthful for unconfirmed AGY allocation/schedule ownership, archive ACP selections, and guide settings attempts on refused saved main selections to explicit clear. Busy AGY transitions do not bypass shared reset admission."},{"version":"1.6.259","text":"### 修复定时任务状态保留\n- 修复 Windows 重复记录 DSH 会话保护标记时的刷盘错误,保留原有凭据和续聊限制。\n- 取消未能确认完成时,保留任务原本的中断原因及取消意图,不会把进程退出误报为原生任务已删除。","changes":[{"topic":"native-schedules","title":"定时任务","text":"修复 Windows 重复记录 DSH 会话保护标记时的刷盘错误,保留原有凭据和续聊限制。"},{"topic":"native-schedules","title":"定时任务","text":"取消未能确认完成时,保留任务原本的中断原因及取消意图,不会把进程退出误报为原生任务已删除。"}],"details":"### Fixed\n- Reopen existing DSH refusal markers with write access before flushing on Windows, without truncating evidence or bypassing file/symlink validation. Repeated marking retains the permanent refusal and all durability checks.\n- Preserve the original interruption diagnostic when retained cancellation fails. Cancellation still reports its error and retains intent; confirmed process exit is never promoted to native deletion success or permission to clean up through a successor.\n\n### Tests\n- Correct late Claude CREATE fixtures to assert unresolved deletion separately from confirmed process exit, retaining the exact handle, interruption reason and no-successor-prompt assertions.\n- Await delegation terminal receipts before asserting notice counts, with a controlled final-metadata gate. Give native artifact entry and completion separate 30-second fixture phases, with regressions for false shared-budget timeouts and continued ownership after real phase timeouts. No production Git deadlines or publication gates were relaxed."},{"version":"1.6.258","text":"### 修复 AGY 新会话设置\n- 新建 ACP 会话会先确认所选模型和思考强度,再开始聊天或接收定时任务,避免因不支持的启动参数悄悄失去定时能力。\n- 设置失败会显示脱敏原因;已分配的失败会话保留历史,需主动 /clear 后再尝试新会话,不会自动恢复。\n- 已有 ACP 会话中修改模型或思考强度仍沿用旧传输切换方式,兼容性未确认;建议在允许清空时主动 /clear,将设置应用到新 ACP 会话。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"新建 ACP 会话会先确认所选模型和思考强度,再开始聊天或接收定时任务,避免因不支持的启动参数悄悄失去定时能力。"},{"topic":"agy-session","title":"AGY 会话","text":"设置失败会显示脱敏原因;已分配的失败会话保留历史,需主动 /clear 后再尝试新会话,不会自动恢复。"},{"topic":"agy-session","title":"AGY 会话","text":"已有 ACP 会话中修改模型或思考强度仍沿用旧传输切换方式,兼容性未确认;建议在允许清空时主动 /clear,将设置应用到新 ACP 会话。"}],"details":"### Fixed\n- Configure fresh AGY ACP model and thinking-level selections through session controls instead of unsupported launch flags. Persist allocation before setup; grant host admission only after native state confirms the requested settings.\n- Fence prompts during initial ACP setup and invalidate setup on competing session controls, cancellation or process retirement. Preserve ordinary ACP backend behavior and DSH callback ownership semantics.\n- Report sanitized startup stage/category diagnostics and visible pre-allocation stream-json fallback. After allocated setup failure, keep the saved selection refused, release only a confirmed-closed runtime, and support explicit archival reset without restoring saved sessions or exit handoff.\n\n### Tests\n- Cover settings confirmation, native aliases, rejected controls, setup races/timeouts, guided refusal/reset and generic ACP backends. Live ACP model/effort switching still uses the existing unverified stream-json transition; use explicit clear for fresh ACP settings."},{"version":"1.6.257","text":"### 定时任务仅在当前会话运行\n- 移除自动恢复功能;CLI、电脑或原生会话进程重启后,未完成任务显示为中断,不会自动重建或补跑。\n- 保留运行中的创建、查看、取消、精确清理及已完成结果投递;原始会话历史不会自动删除。\n- 退出和更新不再通过模型交接定时任务;历史未确认任务保留清理证据,不再挤占当前可运行任务的名额。\n- AGY ACP 保存会话重启后无法安全续聊,即使没有定时任务日志;无任务归属和过渡锁时可主动 /clear 开启新会话,旧历史和未确认凭据保留,线程删除仍受限制;未加载的 AGY 仍有任务归属记录时,切换后端也无法清空或改目录,需使用新线程。\n- 新建 DSH 任务记录准确的原会话归属,创建前启动失败不再误封续聊,不阻塞无关的新会话;旧记录缺少归属时仍保守拒绝,请勿删除未确认凭据。","changes":[{"topic":"native-schedules","title":"定时任务","text":"移除自动恢复功能;CLI、电脑或原生会话进程重启后,未完成任务显示为中断,不会自动重建或补跑。"},{"topic":"native-schedules","title":"定时任务","text":"保留运行中的创建、查看、取消、精确清理及已完成结果投递;原始会话历史不会自动删除。"},{"topic":"native-schedules","title":"定时任务","text":"退出和更新不再通过模型交接定时任务;历史未确认任务保留清理证据,不再挤占当前可运行任务的名额。"},{"topic":"agy-session","title":"AGY 会话","text":"AGY ACP 保存会话重启后无法安全续聊,即使没有定时任务日志;无任务归属和过渡锁时可主动 /clear 开启新会话,旧历史和未确认凭据保留,线程删除仍受限制;未加载的 AGY 仍有任务归属记录时,切换后端也无法清空或改目录,需使用新线程。"},{"topic":"native-schedules","title":"定时任务","text":"新建 DSH 任务记录准确的原会话归属,创建前启动失败不再误封续聊,不阻塞无关的新会话;旧记录缺少归属时仍保守拒绝,请勿删除未确认凭据。"}],"details":"### Changed\n- Remove automatic schedule restoration and the cancelled recovery experiment: HTTP admission server, durable journals, DSH controller, recovery capability flags and startup reconstruction. Native schedules run in the live original conversation; host loss or restart marks unfinished work interrupted without replay.\n- Keep shutdown and updates free of schedule handoff, model/RPC checkpointing and result draining. Idle future definitions do not indefinitely block updates; active work, native mutations and pending results retain their safety gates.\n- Preserve catalog versions 1–6, exact cancellation and cleanup, history purge selectors, outbox acknowledgements, per-thread isolation and original native histories. Legacy ownership metadata authorizes cleanup only; unsettled queued native work still blocks unsafe resume. Historical AGY/DSH cleanup without a supported management route no longer consumes live quota. Persist exact DSH session attribution before CREATE, including ambiguous failures, without fencing unrelated fresh sessions.\n- Saved AGY ACP chat remains non-resumable even without a schedule-owner journal. Explicit `/clear` may detach an owner-free selection while retaining native history and unconfirmed-retirement evidence; thread data erasure remains blocked. No automatic reset or old-session execution is authorized.\n- Compact definitively refused DSH creation attempts before the session marker so startup failures do not fence ordinary chat. Inactive AGY owner journals, including retired ones, continue to block thread-wide reset and directory changes across backends; use a new thread.\n- Preserve late CREATE deletion identities during shutdown without waiting for native work, keep original interrupted diagnostics, and load catalog state with older Routers while withholding unsupported result delivery.\n- Preserve the reviewed AGY owned-host retirement ordering and in-turn purge fixes from 1.6.256. Keep the unrelated compact-summary handoff.\n\n### Tests\n- Cover live native scheduling adapters, restart interruption without reconstruction, no exit-time scheduling RPC, legacy catalogs, cancellation/purge/outbox and ordinary chat. Remove tests exclusive to the deleted recovery and exit-handoff implementations; retain lifecycle safety regressions."},{"version":"1.6.256","text":"### 修复 AGY 定时任务清理\n- 任务在首次触发前取消后,可正常删除线程或切换目录;仍会等待原会话进程确认退出,避免误删未完成的状态。\n- 修复 AGY 在聊天过程中清理定时任务时提示忙碌的问题;只清理选中的任务,尚未确认结束的工作继续保留。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"任务在首次触发前取消后,可正常删除线程或切换目录;仍会等待原会话进程确认退出,避免误删未完成的状态。"},{"topic":"native-schedules","title":"定时任务","text":"修复 AGY 在聊天过程中清理定时任务时提示忙碌的问题;只清理选中的任务,尚未确认结束的工作继续保留。"}],"details":"### Fixed\n- Retire the exact owned AGY host before deleting or resetting a thread whose schedules were cancelled before their first possible wake. Directory changes follow the same ordering; unknown predecessors, live siblings, checkpoint transitions, and unconfirmed exits still retain their evidence.\n- Give AGY schedule purge its native management scope during a foreground turn, preserving exact list/kill receipts, request identity, siblings, and unresolved retirement obligations. History-only cleanup does not start native work.\n\n### Tests\n- Add synthetic production runtime and handler/service/provider regressions for retirement ordering, in-turn purge, stale ownership, and isolated cleanup."},{"version":"1.6.255","text":"### 修复 AGY 线程登录\n- 修复命令行已登录 AGY、线程内仍提示认证失败的问题,兼容新版登录文件并保留已有会话和线程本地凭据。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"修复命令行已登录 AGY、线程内仍提示认证失败的问题,兼容新版登录文件并保留已有会话和线程本地凭据。"}],"details":"### Fixed\n- Share AGY's `antigravity-cli/antigravity-oauth-token` login file with per-thread HOME directories, including threads initialized before login. Preserve thread-local credential replacements and private conversation data.\n\n### Tests\n- Add isolated filesystem regressions for native login discovery, later login, refreshed credentials, and local replacement preservation without launching AGY."},{"version":"1.6.254","text":"### 移除实验性常驻宿主模式\n- 移除实验性常驻宿主启动方式,保留普通启动和现有定时任务恢复能力;本次尚未新增直接停止后的恢复方案。","changes":[{"topic":"native-schedules","title":"定时任务","text":"移除实验性常驻宿主启动方式,保留普通启动和现有定时任务恢复能力;本次尚未新增直接停止后的恢复方案。"}],"details":"### Removed\n- Remove experimental retained-host mode, its launch flag, standalone host runtime, supervisor, pinned bundles, and reduced gateway profile. Ordinary startup, shared ownership safeguards, and native schedule recovery remain supported.\n- Remove retained-host configuration checks without adding a migration gate. This release does not add recovery after an abrupt stop without an exit checkpoint."},{"version":"1.6.253","text":"### 创建失败的定时任务自动收起\n- 因时区不匹配等原因、确认尚未创建的失败任务自动移出列表,启动时也会整理已有的同类记录;原请求仍显示失败,不会重复创建。\n- 结果不明的任务、待清理记录和待确认消息继续保留,不会误删正常任务。","changes":[{"topic":"native-schedules","title":"定时任务","text":"因时区不匹配等原因、确认尚未创建的失败任务自动移出列表,启动时也会整理已有的同类记录;原请求仍显示失败,不会重复创建。"},{"topic":"native-schedules","title":"定时任务","text":"结果不明的任务、待清理记录和待确认消息继续保留,不会误删正常任务。"}],"details":"### Fixed\n- Automatically remove failed fresh schedule attempts that the provider definitively refused before native admission, including native timezone mismatch. Compact existing proven refusal rows at startup while retaining owner-bound replay fences and the original failed request response.\n- Preserve ambiguous creations, recovery failures, cleanup obligations, concurrent operations, and pending results. Keep refused records if safe compaction cannot be persisted or replay-fence capacity is exhausted.\n\n### Tests\n- Cover synthetic native timezone refusal, request receipt retries, restart replay denial, startup compaction, cancellation races, retained results, and persistence/capacity failures."},{"version":"1.6.252","text":"### 定时任务失败后的会话恢复\n- 单个任务恢复失败不会误伤尚未开始恢复的同会话任务;新建任务正常交接后仍可恢复或取消,不受旧任务未确认状态影响。\n- 恢复失败的定时任务不再反复重试;等待原生管理操作结束后,可继续使用原会话聊天,保留原有历史。\n- 清理旧任务后,经运行进程核验可在原会话创建新任务,无需重启整台机器;不会重放结果不明的旧任务。\n- 保留迟到结果与待确认消息;仅有失败历史时不再持续阻塞更新和退出,仍在执行的工作继续受到保护。","changes":[{"topic":"native-schedules","title":"定时任务","text":"单个任务恢复失败不会误伤尚未开始恢复的同会话任务;新建任务正常交接后仍可恢复或取消,不受旧任务未确认状态影响。"},{"topic":"native-schedules","title":"定时任务","text":"恢复失败的定时任务不再反复重试;等待原生管理操作结束后,可继续使用原会话聊天,保留原有历史。"},{"topic":"native-schedules","title":"定时任务","text":"清理旧任务后,经运行进程核验可在原会话创建新任务,无需重启整台机器;不会重放结果不明的旧任务。"},{"topic":"native-schedules","title":"定时任务","text":"保留迟到结果与待确认消息;仅有失败历史时不再持续阻塞更新和退出,仍在执行的工作继续受到保护。"}],"details":"### Fixed\n- Quarantine failed Claude schedule restoration and consumed recovery checkpoints without retrying uncertain jobs. Join the exact failed management turn, or recycle an isolated stalled management host while preserving its original native session. Keep admitted work, late receipts and result acknowledgements protected.\n- Allow explicit new schedules in the original session after same-boot host exclusion, including legacy ownership receipts. Record native host identity and preserve dirty predecessor diagnostics separately; new admission does not certify historical task completion or authorize replay.\n- Register response recipients before schedule recovery admission checks so fenced commands receive their response. Failed-only history no longer blocks update or shutdown after live recovery work settles.\n- Preserve clean pending siblings when an earlier restoration still owns thread admission, and retry them after exact settlement subject to current admission checks.\n- Bind recovery and cleanup to the job's ownership incarnation across clean handoffs, while retaining archived predecessor uncertainty for older jobs.\n- Clear the native recovery deadline before persisting successful activation so slow checkpoint writes cannot strand an already recovered job.\n\n### Tests\n- Add public MessageHandler and synthetic native adapter coverage for recovery timeout, late terminal, bounded process recycle, ordinary chat and fresh scheduling in the same session and boot; cover durable results, repeated restart, legacy receipts, process identity and live-owner conflicts."},{"version":"1.6.251","text":"### 附件恢复与定时任务授权修复\n- 修复取消请求与写盘失败同时发生时,客户端重启可能跳过尚未报告的附件错误的问题。\n- 定时任务回合结束后,未执行的操作授权及时失效,避免后续无关回合误用旧删除授权或一直等待。","changes":[{"topic":"incoming-files","title":"文件接收","text":"修复取消请求与写盘失败同时发生时,客户端重启可能跳过尚未报告的附件错误的问题。"},{"topic":"native-schedules","title":"定时任务","text":"定时任务回合结束后,未执行的操作授权及时失效,避免后续无关回合误用旧删除授权或一直等待。"}],"details":"### Fixed\n- Preserve unreported attachment failures across cancellation, interrupted reporting and persistence errors instead of treating an unfinished report as acknowledged after restart.\n- Retire uninvoked native scheduling authorizations when their exact invocation ends, including autonomous scheduled work. Keep live-turn tool discovery independent from result deadlines and preserve ownership of already-invoked mutations and late receipts.\n\n### Tests\n- Add regressions for cancellation after attachment metadata publication with failed rollback, and for stale deletion authorization surviving a completed scheduled invocation into an unrelated foreground turn."},{"version":"1.6.250","text":"### 定时任务查询保护\n- 查询列表不再触发任务删除;核验超时或失败时保留原任务状态,避免等待中的任务意外失效。\n- 调整原生工具的等待计时,避免模型思考或查找工具超过一分钟后,原本要求的工具调用反而被拒绝。","changes":[{"topic":"native-schedules","title":"定时任务","text":"查询列表不再触发任务删除;核验超时或失败时保留原任务状态,避免等待中的任务意外失效。"},{"topic":"native-schedules","title":"定时任务","text":"调整原生工具的等待计时,避免模型思考或查找工具超过一分钟后,原本要求的工具调用反而被拒绝。"}],"details":"### Fixed\n- Keep schedule listing observational: inventory errors preserve active task state and admission, unresolved records never trigger automatic cleanup, and list receipts reject unexpected native mutations. Verified native absence remains distinct from execution completion.\n- Separate current-turn native invocation waiting from receipt deadlines so model and tool-discovery delays do not expire an uninvoked action. Preserve bounded native-result and out-of-turn management waits and retire actions on turn end, local errors, timeouts, abort, or owner loss without discarding uncertain mutation ownership.\n\n### Tests\n- Cover read-only listing through slash commands and managed tools, inventory uncertainty and absence, pending cleanup, delayed native invocation, result deadlines, foreground errors without native result frames, and late-receipt isolation with synthetic fixtures.\n- Isolate recovery catalog-lock release/reacquisition tests in the existing fork pool to prevent inherited descriptors from transiently retaining a released lock during concurrent test-worker startup."},{"version":"1.6.249","text":"### 附件失败恢复\n- 超限或接收失败的附件报错后,不再反复影响后续普通聊天,客户端重启后也会记住处理状态;明确引用失败文件时仍提示重新上传。","changes":[{"topic":"incoming-files","title":"文件接收","text":"超限或接收失败的附件报错后,不再反复影响后续普通聊天,客户端重启后也会记住处理状态;明确引用失败文件时仍提示重新上传。"}],"details":"### Fixed\n- Persist consumption of reported attachment failures so oversized or rejected files do not block later ordinary messages after a client restart. Preserve the first associated command's error and explicit-reference rejection.\n\n### Tests\n- Cover failure reporting, inbox recreation, explicit rejected references, and subsequent ordinary-message execution with isolated attachment fixtures."},{"version":"1.6.248","text":"### 定时任务升级连续性与失败保护\n- 定时任务交接失败后,其他线程可继续聊天;受影响线程仍保留保护,后续升级会重新检查是否就绪,不会重复未确认的交接。\n- 升级日志区分准备与安装,准备失败不会执行安装;已安装成功的同一版本不因收尾失败而重复安装。\n- 新增需单独配置的实验模式:新建会话的定时任务保留在独立宿主,前端更新交接不调用模型;不自动迁移旧会话,也不保证宿主崩溃后续跑。\n- 实验模式下,任务及结果已处理完毕后可正常关闭宿主;无法确认进程退出时保留任务记录与重试保护。","changes":[{"topic":"native-schedules","title":"定时任务","text":"定时任务交接失败后,其他线程可继续聊天;受影响线程仍保留保护,后续升级会重新检查是否就绪,不会重复未确认的交接。"},{"topic":"native-schedules","title":"定时任务","text":"升级日志区分准备与安装,准备失败不会执行安装;已安装成功的同一版本不因收尾失败而重复安装。"},{"topic":"native-schedules","title":"定时任务","text":"新增需单独配置的实验模式:新建会话的定时任务保留在独立宿主,前端更新交接不调用模型;不自动迁移旧会话,也不保证宿主崩溃后续跑。"},{"topic":"native-schedules","title":"定时任务","text":"实验模式下,任务及结果已处理完毕后可正常关闭宿主;无法确认进程退出时保留任务记录与重试保护。"}],"details":"### Fixed\n- Separate automatic-update preparation from installation in logs. Failed finalization releases global update admission while preserving affected schedule-thread fences; unrelated chat remains available, and retries check readiness without replaying uncertain handoff operations or starting model-mediated recovery.\n- Remember successful package installation across finalization failures so retries do not reinstall the same version. Installation and restart still require confirmed preparation.\n- Separate drained-host retirement admission from native exit proof. Explicit stop joins original executor groups, persists late callbacks and releases ownership only after confirmation; failed exits retain the same handles for retry.\n\n### Added\n- Add an opt-in retained native host with a separately updated command frontend, authenticated local epochs, durable operation receipts, scheduled result delivery and single-writer storage. Frontend replacement keeps the original host and does not invoke native schedule management. Existing monolithic sessions are not imported; the opt-in command profile and host failure/restart limitations are explicit.\n- Connect private retained-host launch records to verified immutable runtime bundles and independently named Linux/macOS service supervisors. Reusing a running owner does not restart it; uncertain or previously stopped owners require reconciliation. Windows supervision is unsupported. Actual service-manager, package-installation and live Router acceptance remain required before deployment.\n\n### Tests\n- Isolate retained-host and schedule-handler native lock tests in separate test processes, preventing unrelated child creation from transiently inheriting their locks.\n- Verify real Claude/AGY continuity in isolated Linux namespaces with deterministic loopback providers: stable native identities, once/cron execution across frontend replacement, ACK replay without execution replay, and zero inference or management calls during replacement and drained-host stop. This does not verify live services or macOS/Windows.\n- Align the legacy Claude installer-failure regression with retained thread fences and assert no recovery requests after failure or reconnect."},{"version":"1.6.247","text":"### 会话关闭修复\n- 修复线程恢复记录异常时可能阻断正常关闭的问题;仍需确认原进程退出,异常会话继续禁止执行并保留原数据。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"修复线程恢复记录异常时可能阻断正常关闭的问题;仍需确认原进程退出,异常会话继续禁止执行并保留原数据。"}],"details":"### Fixed\n- Retire existing AGY hosts during shutdown even when a thread's reset generation is corrupt or unreadable. Use stored backend summaries only for teardown; retain execution admission checks, original context data and the requirement to confirm host retirement before schedule catalog cleanup.\n\n### Tests\n- Await asynchronous AGY context reset in backend-isolation fixtures and complete discovery/shutdown test doubles. Cover corrupt-generation shutdown and unconfirmed AGY exit without weakening lifecycle guards. Join schedule recovery and durable ACK settlement before reading the catalog in restart fixtures, avoiding concurrent readers during Windows file replacement."},{"version":"1.6.246","text":"### AGY 原生定时任务与会话保护\n- 中止、切换模型或进程异常后,下一条命令会等待旧进程确认关闭,避免新旧进程同时使用同一会话。\n- 无法确认退出时保留会话并暂停新执行,可重试 /abort;清空会话和删除线程数据也会先等待退出。\n- 新的 AGY 会话可通过 /schedule 或对话工具创建原生定时任务,结果回到原线程;旧会话保留上下文,不自动迁移,也不按 AGY 版本号限制。\n- AGY 尚未到首次触发时间的安全任务可在中止当前请求或正常重启后自动续跑,保留原会话;到期、取消或状态不明的任务不会自动重放。\n- 加强 AGY 结果归属与取消后的任务检查;有安全检查点的无任务会话可直接恢复,无法确认旧提醒状态的历史会话仍保留兼容聊天方式。","changes":[{"topic":"agy-session","title":"AGY 会话","text":"中止、切换模型或进程异常后,下一条命令会等待旧进程确认关闭,避免新旧进程同时使用同一会话。"},{"topic":"agy-session","title":"AGY 会话","text":"无法确认退出时保留会话并暂停新执行,可重试 /abort;清空会话和删除线程数据也会先等待退出。"},{"topic":"native-schedules","title":"定时任务","text":"新的 AGY 会话可通过 /schedule 或对话工具创建原生定时任务,结果回到原线程;旧会话保留上下文,不自动迁移,也不按 AGY 版本号限制。"},{"topic":"native-schedules","title":"定时任务","text":"AGY 尚未到首次触发时间的安全任务可在中止当前请求或正常重启后自动续跑,保留原会话;到期、取消或状态不明的任务不会自动重放。"},{"topic":"native-schedules","title":"定时任务","text":"加强 AGY 结果归属与取消后的任务检查;有安全检查点的无任务会话可直接恢复,无法确认旧提醒状态的历史会话仍保留兼容聊天方式。"}],"details":"### Added\n- Add a reusable original-session AGY ACP schedule host/provider and authenticated hook/transcript bridge. Join native tool-step receipts, SYSTEM sender provenance and native Stop batches; bound canonical native transcript reads and preserve user hook groups. Native AGY owns once/cron timing and inference.\n- Carry AGY identities through the existing schedule catalog, durable outbox, result ACKs and Router cards. Isolated Linux acceptance exercises the compiled adapter with real native timers and a deterministic loopback provider; external delivery is mocked. Fresh production AGY sessions now use this ACP path through the executor factory, MessageHandler commands and session-scoped MCP scheduling tools. Saved stream-json sessions remain compatible without silent migration. No AGY version restriction or client timer fallback is used.\n\n- Register AGY managed tools with standard ACP session-scoped MCP servers. Preserve user hook configuration in a private HOME overlay; retire the exact host group before catalog shutdown. Completed one-shots do not start cleanup inference from a terminal callback, and inactive-thread deletion checks retained AGY ownership. Explicit context reset after confirmed retirement discards, rather than replays, old work.\n\n### Fixed\n- Require matched native invocation start/completion evidence and stable completed output before settling an AGY batch. Recheck each new wake and management receipt against current ownership while retaining already admitted late results after cancellation; native execution counters are not treated as globally unique IDs.\n- Fence AGY successor prompts on the previous host's confirmed transport close, including abort, unexpected exit and model/effort recycling. A bounded exit timeout retains the original conversation and blocks execution until explicit retirement is confirmed; signalling a process is not completion evidence.\n- Join AGY shutdown before context reset, managed-tool reconfiguration or thread-data removal. Invalidate prompts waiting on a retired context and report stream-json abort's loss of session-only timers explicitly.\n- Add deadline-bounded original-conversation AGY continuation after foreground cancellation and orderly restart/update recovery through the shared catalog. Persist and exclusively consume clean handoff proof before loading; preserve exact task ownership and outbox identities across native definition rebinding. Exact cancellation before any possible first wake can retire an individual task, preserving sibling recovery and allowing clean chat restoration after all tasks are cancelled. Unknown queued work, dirty exits, expired one-shots and cancelled jobs are not replayed.\n- Restore checkpointed no-job AGY conversations on ACP without resetting their context. Uninstrumented saved stream-json sessions remain compatible and refuse unsafe migration before inference. Ordinary no-job abort/settings behavior is preserved."},{"version":"1.6.245","text":"### 定时任务残留清理\n- 已删除历史却仍显示清理未确认的记录,现在可以明确请求忘记选中的残留追踪;不会误报原生任务已删除,也不会恢复已删除任务。\n- 修复能够确认尚未提交原生创建的失败任务仍留下无法收尾记录的问题;正在执行或清理尚未确认的任务继续受到保护。","changes":[{"topic":"native-schedules","title":"定时任务","text":"已删除历史却仍显示清理未确认的记录,现在可以明确请求忘记选中的残留追踪;不会误报原生任务已删除,也不会恢复已删除任务。"},{"topic":"native-schedules","title":"定时任务","text":"修复能够确认尚未提交原生创建的失败任务仍留下无法收尾记录的问题;正在执行或清理尚未确认的任务继续受到保护。"}],"details":"### Fixed\n- Record verified pre-dispatch native schedule refusals so failed creation can be purged without leaving an unresolvable cleanup obligation. Preserve uncertainty after native admission or mutation.\n- Add exact-ID `forgetUnresolved: true` and `/schedule purge <managed-id,...> --forget-unresolved` for user-requested erasure of cleanup tracking whose history was already purged. Preserve durable replay fences, ownership, pending-work guards, and native-absence warnings; never invoke native tools or claim native deletion when forgetting metadata."},{"version":"1.6.244","text":"### 旧定时任务历史删除\n- 缺少旧会话归属的历史记录现在也能按请求删除,连同尚未发送的结果一起清理,不再无限等待原生任务核验。\n- 历史删除与原生任务清理分别报告;未能确认清理的原生任务保留最小追踪信息,可在列表查看并重试,不会误报全部清理完成。\n- 保留正在执行和发送中的任务保护,重启后不会恢复已删除历史;新清理追踪格式需客户端 1.6.244 或更新版本读取。","changes":[{"topic":"native-schedules","title":"定时任务","text":"缺少旧会话归属的历史记录现在也能按请求删除,连同尚未发送的结果一起清理,不再无限等待原生任务核验。"},{"topic":"native-schedules","title":"定时任务","text":"历史删除与原生任务清理分别报告;未能确认清理的原生任务保留最小追踪信息,可在列表查看并重试,不会误报全部清理完成。"},{"topic":"native-schedules","title":"定时任务","text":"保留正在执行和发送中的任务保护,重启后不会恢复已删除历史;新清理追踪格式需客户端 1.6.244 或更新版本读取。"}],"details":"### Fixed\n- Delete selected owned schedule history and queued results even when legacy native attribution is missing. History removal and unresolved native cleanup are separate results; running work, pending operations, in-flight delivery, owner generations, and sibling schedules remain protected.\n- Persist a bounded deletion-only cleanup ledger, durable request selections and permanent replay fences atomically with history removal (catalog format 5, requiring CLI 1.6.244 or newer while cleanup entries or request receipts are present). Keep no prompt/output text or execution-recovery permission. List remaining obligations and retry them through the existing purge command/tool; exact attributed Claude selectors retain prompt digests for deletion and fresh absence verification in the original bound session.\n- Keep deletion-only cleanup visible and retriable for the same authenticated user/thread across context generations without changing original provenance or live-record isolation. Avoid blocking DSH context reset where no supported cleanup route depends on retaining that session.\n- Preserve explicit native-cleanup limitations for missing session attribution, unconfirmed predecessors and unsupported backend capabilities. An empty unrelated session never proves global absence; Router upgrades alone do not change CLI cleanup behavior."},{"version":"1.6.243","text":"### 定时任务历史清理修复\n- 修复原生任务已删除后,历史清理仍缺少核验入口的问题;可核实原会话归属且确认旧执行已结束的记录,现在能够清理。\n- 保存已确认的取消与执行结束结果,避免重启客户端后再次丢失清理依据;保存后需使用 1.6.243 或更新版本读取。\n- 对缺少归属信息或无法确认旧执行已结束的任务,明确说明未完成原因;不会把当前会话的空列表当成所有旧任务已清除。","changes":[{"topic":"native-schedules","title":"定时任务","text":"修复原生任务已删除后,历史清理仍缺少核验入口的问题;可核实原会话归属且确认旧执行已结束的记录,现在能够清理。"},{"topic":"native-schedules","title":"定时任务","text":"保存已确认的取消与执行结束结果,避免重启客户端后再次丢失清理依据;保存后需使用 1.6.243 或更新版本读取。"},{"topic":"native-schedules","title":"定时任务","text":"对缺少归属信息或无法确认旧执行已结束的任务,明确说明未完成原因;不会把当前会话的空列表当成所有旧任务已清除。"}],"details":"### Fixed\n- Wire production history purge to fresh original-session Claude inventory under the existing cleanup lease. Exact saved session, working directory, thread and marker attribution plus framework-confirmed predecessor retirement permit removal after reviewed native deletion, without requiring execution-recovery model metadata or recreating tasks.\n- Persist confirmed native cancellation and execution retirement for Claude and DSH so later history purge can survive a CLI restart. This optional cleanup receipt uses catalog format 4, never grants execution admission, and requires CLI 1.6.243 or newer to read while present.\n- Report missing attribution and uncertain predecessor work separately from native presence. Empty inventory in another session does not erase legacy history; unresolved cancellation tracking and sibling schedules remain intact."},{"version":"1.6.242","text":"### 定时任务删除与历史清理\n- 请求清理后,助手可直接检查并删除选中的原生任务,不再要求你复制确认命令;仍核验任务归属和删除结果。\n- 新增 /schedule purge,可取消选中的托管任务并移除确认清理完成的历史记录;未完成的清理会逐项说明,不会仅清空列表就报成功。清理后的目录格式不支持旧版客户端读取。\n- 修复原生列表查询超时后残留授权、反复积累导致后续查询受阻的问题;超时提示会区分调用和回执阶段,删除结果未知时不误报成功。","changes":[{"topic":"native-schedules","title":"定时任务","text":"请求清理后,助手可直接检查并删除选中的原生任务,不再要求你复制确认命令;仍核验任务归属和删除结果。"},{"topic":"native-schedules","title":"定时任务","text":"新增 /schedule purge,可取消选中的托管任务并移除确认清理完成的历史记录;未完成的清理会逐项说明,不会仅清空列表就报成功。清理后的目录格式不支持旧版客户端读取。"},{"topic":"native-schedules","title":"定时任务","text":"修复原生列表查询超时后残留授权、反复积累导致后续查询受阻的问题;超时提示会区分调用和回执阶段,删除结果未知时不误报成功。"}],"details":"### Changed\n- Permit scoped agent tools to execute reviewed native schedule deletion without a separate owner-text confirmation. Preserve exact inventory, owner/session, expiry, sibling and native-action receipt checks; keep the existing text command compatible.\n- Add managed schedule purge tools and commands: cancel first, remove only verified retired history and queued output, and report pending cleanup per task. Persist bounded ID/owner replay fences in catalog format 3; older format-2 clients cannot downgrade this catalog.\n\n### Fixed\n- Release expired native CronList read authorizations to prevent capacity exhaustion after repeated missing receipts. Report the stalled timeout stage without implying that an inventory read created a task; retain uncertain mutation receipts for reconciliation."},{"version":"1.6.241","text":"### 会话恢复与任务收尾\n- 新增 /schedule cleanup review:可在原会话查看旧任务并亲自确认删除选中的原生任务,不再依赖缺失的历史托管信息;仅确认当前会话的定义已删除,不误报旧进程已停止,无法确认会话归属的任务仍会明确阻止。\n- 恢复 Claude 会话时会先检查并拦截无法确认归属的旧任务,避免仅隐藏输出却继续运行;归属可验证的任务仍可恢复,历史任务的删除仍需核实,不会批量删除其他任务。 启动时先等待保护就绪,不能承接定时任务的会话、委派进程和压缩进程会禁用原生定时执行。\n- 托管任务中断或请求取消后,即使清理失败也会拦截后续执行,已开始的结果仍可回传;修复一次性任务因原生列表省略字段而无法删除的问题。\n- 子任务成果尚未处理完时,主任务会在原会话继续收尾,不再仅因超过两轮就失败,也不会重复执行已完成的子任务或重新发送原附件。\n- 多次收尾仍无进展时会逐步放缓重试;可用 /abort 停止,清理会话或关闭客户端也会取消等待,未解决的成果仍会保留。","changes":[{"topic":"native-schedules","title":"定时任务","text":"新增 /schedule cleanup review:可在原会话查看旧任务并亲自确认删除选中的原生任务,不再依赖缺失的历史托管信息;仅确认当前会话的定义已删除,不误报旧进程已停止,无法确认会话归属的任务仍会明确阻止。"},{"topic":"native-schedules","title":"定时任务","text":"恢复 Claude 会话时会先检查并拦截无法确认归属的旧任务,避免仅隐藏输出却继续运行;归属可验证的任务仍可恢复,历史任务的删除仍需核实,不会批量删除其他任务。 启动时先等待保护就绪,不能承接定时任务的会话、委派进程和压缩进程会禁用原生定时执行。"},{"topic":"native-schedules","title":"定时任务","text":"托管任务中断或请求取消后,即使清理失败也会拦截后续执行,已开始的结果仍可回传;修复一次性任务因原生列表省略字段而无法删除的问题。"},{"topic":"delegation","title":"委派任务","text":"子任务成果尚未处理完时,主任务会在原会话继续收尾,不再仅因超过两轮就失败,也不会重复执行已完成的子任务或重新发送原附件。"},{"topic":"delegation","title":"委派任务","text":"多次收尾仍无进展时会逐步放缓重试;可用 /abort 停止,清理会话或关闭客户端也会取消等待,未解决的成果仍会保留。"}],"details":"### Fixed\n- Add explicit `/schedule cleanup review` and owner text confirmation for exact session-only Claude Cron definitions, including legacy/native-only tasks without managed recovery metadata. Bind short-lived reviews to owner, connection and native host/session, verify full structured inventory before and after deletion, reconcile lost receipts only from fresh absence, and preserve unknown predecessor status. Project-persisted definitions without session attribution remain blocked. Expose review through managed scheduling tools without a model confirmation endpoint.\n- Check live managed admission at every Claude wake, including recovered jobs. Interrupted, cancelled, faulted or retired owners cannot admit new occurrences even when native cleanup fails; preserve already-admitted completion callbacks and independent sibling jobs.\n- Accept omitted native CronList recurrence for one-shot cancellation while rejecting malformed values and preserving exact definition and ownership checks.\n- Hold scheduling-enabled Claude startup with the native `--await-initialize` barrier before restored timers can run. Disable native Cron per process for non-owning foreground hosts, restricted hosts, delegated workers and external compaction; the previous settings flag did not suppress restored execution. Preserve owned adoption, delivery and exact cancellation without changing native timers.\n- Guard resumed foreground Claude schedules before chat independently of managed-tool registration. Verify callback-hook policy, reject unowned restored wakeups before inference, and preserve exact-owned adoption and delivery. Do not infer scheduler suppression from launch settings, delete unverifiable legacy definitions, or claim already-admitted predecessor work is stopped.\n- Continue unresolved delegated artifact closeout in the original coordinator request/session instead of failing after two rounds. Preserve explicit integration decisions, durable receipt and ancestry checks, worker-launch/tool-call admission limits, and existing backend failure handling; do not replay completed workers or original attachments.\n- Pace repeated unresolved closeout with a 1–30 second capped backoff. Cancel waits on abort, conversation retirement, or shutdown, retain request/queue ownership, and recheck durable disposition before another model turn.\n\n### Tests\n- Cover reviewed cleanup authorization, stale inventories and hosts, partial/error-after-commit retries, missing/foreign ownership receipts, sibling callbacks, catalog attribution and authenticated command/tool routing. Isolated Linux native acceptance verifies exact deletion and absence after a second resume while unknown scheduled wakes make no inference requests.\n- Cover continuation beyond two rounds, capped pacing and timer cleanup, cancellation during waits, model/compaction retries, unchanged admission limits, and pending/unavailable artifact preservation with synthetic executors and real Git fixtures."},{"version":"1.6.240","text":"### 清理中断的定时任务\n- 中断的 Claude 任务在原会话和归属信息可验证时,可检查并删除原生已有定义,不再因丢失运行句柄而无法清理,也不会重建任务或补跑。\n- 取消请求会保留;旧任务缺少归属证据,或同次开机内旧进程的工作仍无法确认时,会明确报告清理未完全确认,不再误报取消成功。请使用完整托管任务 ID,不要重复创建。","changes":[{"topic":"native-schedules","title":"定时任务","text":"中断的 Claude 任务在原会话和归属信息可验证时,可检查并删除原生已有定义,不再因丢失运行句柄而无法清理,也不会重建任务或补跑。"},{"topic":"native-schedules","title":"定时任务","text":"取消请求会保留;旧任务缺少归属证据,或同次开机内旧进程的工作仍无法确认时,会明确报告清理未完全确认,不再误报取消成功。请使用完整托管任务 ID,不要重复创建。"}],"details":"### Fixed\n- Route interrupted Claude schedule cancellation through a removal-only native inventory operation when the live handle is gone. Require the original session/model, durable ownership evidence, exact native ID, full marked prompt and rule before deleting; verify absence afterward without creating or admitting work.\n- Preserve cancellation intent and report partial cleanup when a same-boot predecessor remains unconfirmed. Legacy records without ownership evidence now fail explicitly instead of returning an unchanged interrupted record as a successful cancellation. Direct unscoped native deletion remains denied.\n\n### Tests\n- Cover scoped inventory/deletion receipts, mismatched ownership, expired one-shots, stale and late replies, repeated cancellation, sibling execution, predecessor fences and cancellation tombstones using isolated synthetic protocol fixtures."},{"version":"1.6.239","text":"### 按实际能力支持 Claude\n- Claude 恢复时优先接续原生已有任务,避免重复创建;新建周期任务在确认同一电脑已重新启动后可恢复后续触发,不补跑未知结果。同次开机内强制终止 CLI、原生任务无故缺失或一次性任务结果不明时仍会暂停恢复。\n- 不再仅允许指定 Claude 版本或架构恢复定时任务;实际具备所需能力的新版本和 ARM64 会话也可进行有序恢复,已开始的工作仍须完成,结果不明确时继续阻止恢复。\n- 原会话模型切换和保留会话的取消操作改为检查实际控制能力与回执,不再因版本号或架构不同直接拒绝;未确认的操作不会误报成功。\n- Linux 托管服务停止时先通知 CLI 完成交接,结果确认结束后再断开连接,避免提前结束原生进程;旧版生成的服务单元会在明确的服务操作前迁移,自定义配置需人工检查,超时或清理失败不会误报安全恢复。","changes":[{"topic":"native-schedules","title":"定时任务","text":"Claude 恢复时优先接续原生已有任务,避免重复创建;新建周期任务在确认同一电脑已重新启动后可恢复后续触发,不补跑未知结果。同次开机内强制终止 CLI、原生任务无故缺失或一次性任务结果不明时仍会暂停恢复。"},{"topic":"native-schedules","title":"定时任务","text":"不再仅允许指定 Claude 版本或架构恢复定时任务;实际具备所需能力的新版本和 ARM64 会话也可进行有序恢复,已开始的工作仍须完成,结果不明确时继续阻止恢复。"},{"topic":"model-selection","title":"模型切换","text":"原会话模型切换和保留会话的取消操作改为检查实际控制能力与回执,不再因版本号或架构不同直接拒绝;未确认的操作不会误报成功。"},{"topic":"native-schedules","title":"定时任务","text":"Linux 托管服务停止时先通知 CLI 完成交接,结果确认结束后再断开连接,避免提前结束原生进程;旧版生成的服务单元会在明确的服务操作前迁移,自定义配置需人工检查,超时或清理失败不会误报安全恢复。"}],"details":"### Fixed\n- Require exact boolean recurrence evidence when adopting native Claude schedules. On handoff-completion retries, publish the durable clean ownership receipt only after the captured host's drained EOF exit; a successful exit before that boundary is insufficient.\n- Reconcile Claude schedules against structured native CronList receipts, adopting exact owned definitions without duplicate creation. New recurring jobs may resume future firings after verified same-machine reboot using durable session ownership and exclusive catalog/host locks. Same-boot crashes, unknown predecessors, unexplained native absence and uncertain one-shots remain blocked; cancellation tombstones and the existing orderly path are preserved.\n- Give the CLI main process the first systemd stop signal with `KillMode=mixed` and an explicit 90-second supervisor timeout. Migrate only recognized generated legacy units before explicit service operations, verify effective overrides, preserve custom units, and report failed/timed-out stops without removing the unit.\n- Keep the Router connection available until native shutdown handoff and result acknowledgement settle; disconnect afterward, preserving cleanup errors and idempotent shutdown.\n- Remove exact Claude version, OS and architecture allowlists from native model control, retained-process interruption and orderly schedule recovery. Use actual initialized process/session identity, native tools/hooks/lifecycle capabilities and correlated receipts instead; newer capable ARM64 hosts are no longer excluded solely by their build or architecture.\n- Preserve restricted/worker recovery exclusions, uncertain-outcome fences, admitted-work drain, background inventory and confirmed predecessor exit. Missing protocol evidence never authorizes automatic recreation or false success.\n\n### Tests\n- Cover newer ARM64 and simulated macOS/Windows protocol branches, absent version metadata, missing lifecycle capabilities, changed process/session identity and original-session recovery. These synthetic tests do not establish native support on every OS or Claude release."},{"version":"1.6.238","text":"### 定时任务恢复与模型切换\n- 取消意图会先保存,避免清理回执丢失后误恢复;恢复过程不会自动补跑过期的一次性任务或执行结果未知的任务;Claude 已取消或拒绝的执行不会因后续成功回执被误报成功。\n- 新建 DSH 任务及 Linux x64 上 Claude 2.1.311 的托管定时任务可在确认有序退出后自动恢复,无需打开原会话;等待中的可恢复任务不再一直阻止自动升级,安装失败也会尝试恢复。\n- Claude 已触发但尚未获准执行的任务可在升级时跳过,不会误报成功或补跑;已开始的执行仍须完成,后台工作或退出结果不明时会暂缓升级;异常崩溃后的自动重建暂不支持。\n- 升级后的安全恢复若只是在等待 Router 重连,会在连接恢复后继续;不会在安装尚未结束时提前启动任务。\n- Linux x64 的 Claude 2.1.311 可在原进程内切换模型并保留后续定时任务;其他运行中的版本或平台会明确拒绝,不再为切换模型自动停止进程。\n- 切换及自动恢复的模型回执不明确时会暂缓新任务,不保存未确认选项;清理其他任务不会提前解除等待;有定时任务时会拒绝需要重启的思考强度调整,避免意外丢失任务。","changes":[{"topic":"native-schedules","title":"定时任务","text":"取消意图会先保存,避免清理回执丢失后误恢复;恢复过程不会自动补跑过期的一次性任务或执行结果未知的任务;Claude 已取消或拒绝的执行不会因后续成功回执被误报成功。"},{"topic":"native-schedules","title":"定时任务","text":"新建 DSH 任务及 Linux x64 上 Claude 2.1.311 的托管定时任务可在确认有序退出后自动恢复,无需打开原会话;等待中的可恢复任务不再一直阻止自动升级,安装失败也会尝试恢复。"},{"topic":"native-schedules","title":"定时任务","text":"Claude 已触发但尚未获准执行的任务可在升级时跳过,不会误报成功或补跑;已开始的执行仍须完成,后台工作或退出结果不明时会暂缓升级;异常崩溃后的自动重建暂不支持。"},{"topic":"native-schedules","title":"定时任务","text":"升级后的安全恢复若只是在等待 Router 重连,会在连接恢复后继续;不会在安装尚未结束时提前启动任务。"},{"topic":"model-selection","title":"模型切换","text":"Linux x64 的 Claude 2.1.311 可在原进程内切换模型并保留后续定时任务;其他运行中的版本或平台会明确拒绝,不再为切换模型自动停止进程。"},{"topic":"model-selection","title":"模型切换","text":"切换及自动恢复的模型回执不明确时会暂缓新任务,不保存未确认选项;清理其他任务不会提前解除等待;有定时任务时会拒绝需要重启的思考强度调整,避免意外丢失任务。"}],"details":"### Tests\n- Verify Claude model switching with the real isolated Linux 2.1.311 host and a loopback fake provider, including autonomous timing and late acknowledgement. Add a regression for a resumed unowned wake whose blocked hook still produces a successful native terminal; this is not schedule recovery proof.\n\n### Added\n- Add a versioned provider-neutral schedule recovery contract for authoritative persistent reattachment or predecessor-fenced reconstruction. Persist execution intent, cancellation intent and bounded occurrence deduplication; reconcile eligible records after Router readiness without a foreground message.\n- Require original owner/backend/directory admission, serialize recovery and retain ambiguous native receipts. Expired one-shots and crash-interrupted executions are not replayed. Legacy terminal records remain terminal.\n- Add an explicit provider-neutral skip-unadmitted handoff policy. Claude 2.1.311 on Linux x64 fences UserPromptSubmit admission, skips pending occurrences without replay or successful delivery, drains admitted work/background tasks, verifies owned native deletion and joins a no-escalation EOF exit. Persist stable ownership before CREATE and verify native inventory in the original session before reconstruction.\n\n### Changed\n- Use acknowledged native `set_model` for live Claude 2.1.311 sessions on Linux x64, retaining process/session/managed-tool registration and future jobs. Support native default and card/global reset semantics; cold selection does not spawn a host. Other live builds/platforms refuse the change without a destructive fallback.\n- Fence model-control uncertainty, bind receipts to the captured host/session, and keep timed-out preferences unsaved even on late acknowledgement. Allow only explicit same-host retries after settled internal errors; retain destructive context reset as an explicit recovery option. Refuse restart-based effort changes while managed native schedules exist.\n- Enable DSH orderly recovery through native serialized deletion, queued-turn drain, session flush and confirmed owned-host exit. Resume the original session automatically after Router readiness and reconstruct only future firings from a consumed durable clean checkpoint.\n- Prepare native handoff before automatic installation; restore suspended jobs after failed installation or manual install-only updates. Waiting eligible Claude and DSH jobs no longer block updates indefinitely; uncertain drain/exit/restoration retains admission and never silently force-stops work.\n\n### Fixed\n- Require a completed Claude scheduled lifecycle as well as a successful result before reporting occurrence success; cancelled, discarded or refused terminals cannot be overwritten by late success receipts.\n- Do not reconstruct a one-shot already absent at handoff, or block the next foreground turn when every cleanly suspended one-shot is skipped or expires.\n- Validate the exact model acknowledgement during Claude recovery, retain cleanup handles for post-create failures, and scope admission release to its restoration owner. Finalize terminal-only update handoffs and describe the negotiated recovery policy in creation responses.\n- Fence automatic updates while startup catalog inspection/reconciliation is unresolved, including malformed catalogs. Persist cancellation intent before native deletion so a failed receipt cannot authorize later recreation.\n- Distinguish clean native quiescence from deletion evidence when cancelling or expiring persistent schedules. Resume clean update restoration on Router reconnect only after installation finalization; reject update admission on destroyed handlers.\n\n### Limitations\n- Dirty-crash reconstruction remains unsupported. Claude orderly recovery is gated to Linux x64 Claude Code 2.1.311; isolated real-native acceptance uses a loopback fake API and native Cron timing, not authenticated provider traffic. No macOS/Windows native Claude recovery claim is made. DSH retains its stricter drain policy. Retained-process `/abort` and model switching remain supported."},{"version":"1.6.237","text":"### 取消当前任务并保留后续定时任务\n- Claude 启动中的请求也可取消,旧请求和输入等待不再影响下一轮;停止结果不确定时会阻止新任务,并提示重试 /abort。\n- 取消聊天时刚创建成功的定时任务会保留清理状态;无法安全清理时可通过 /schedule list 查看并重试取消,避免重复创建。\n- Linux x64 上已验证的 Claude 2.1.311 可在 /abort 后保留会话和后续定时任务;已触发的任务仍可能被一起打断,其他版本或平台继续使用停止进程的方式。\n- 清理未确认时可重试 /abort;若选择 /clear 或 /new 强制恢复,会停止进程并丢失其中的定时任务,不会悄悄重建任务。","changes":[{"topic":"session-handoff","title":"会话接续","text":"Claude 启动中的请求也可取消,旧请求和输入等待不再影响下一轮;停止结果不确定时会阻止新任务,并提示重试 /abort。"},{"topic":"native-schedules","title":"定时任务","text":"取消聊天时刚创建成功的定时任务会保留清理状态;无法安全清理时可通过 /schedule list 查看并重试取消,避免重复创建。"},{"topic":"native-schedules","title":"定时任务","text":"Linux x64 上已验证的 Claude 2.1.311 可在 /abort 后保留会话和后续定时任务;已触发的任务仍可能被一起打断,其他版本或平台继续使用停止进程的方式。"},{"topic":"session-handoff","title":"会话接续","text":"清理未确认时可重试 /abort;若选择 /clear 或 /new 强制恢复,会停止进程并丢失其中的定时任务,不会悄悄重建任务。"}],"details":"### Changed\n- On Linux x64 with Claude 2.1.311 and verified native capabilities/process identity, interrupt foreground work without restarting Claude or losing future native schedules. Join acknowledgement, input UUID results and lifecycle terminals, retire old interactive authority, and stop only background tasks with observed foreground tool lineage.\n- Reconcile interrupted native CREATE/DELETE mutations under a cancellation-owned lease on the same host. Keep unconfirmed cleanup fenced and retryable with `/abort`; `/clear` provides explicit destructive recovery that loses session-only schedules. Never recreate jobs or claim atomic cancellation of already-fired scheduled work or all external effects.\n\n### Fixed\n- Cancel Claude requests still queued during startup, fence late startup dispatch, and keep uncertain shutdowns blocked until explicit retry confirms process exit. Startup and unsupported native hosts retain the explicit process-stop fallback.\n- Retire interactive input waiters and detection timers on abort, context reset, and destruction so old callbacks cannot change a later turn's input state.\n- Give managed tool activations owner-checked retirement so an older finalizer cannot deactivate a newer turn; keep the Claude endpoint registered across a verified retained abort while preserving deliberate disposal on reset/destroy/backend changes.\n- Reconcile late accepted Claude schedule creation only under fresh owner authority on the existing idle host. Preserve the native handle and a retryable cleanup error when admission is unsafe, without recreating jobs or reviving an expired foreground scope."},{"version":"1.6.236","text":"### 定时与排队卡片更清晰\n- 定时和排队卡片突出任务内容,状态、时间和操作更易读,长任务编号改为次要信息。\n- 统一排队确认、取消和开始执行后的卡片样式,保留原有按钮操作。","changes":[{"topic":"task-cards","title":"任务卡片","text":"定时和排队卡片突出任务内容,状态、时间和操作更易读,长任务编号改为次要信息。"},{"topic":"task-cards","title":"任务卡片","text":"统一排队确认、取消和开始执行后的卡片样式,保留原有按钮操作。"}],"details":"### Changed\n- Refine scheduled-task and queue cards with task-first content, compact status and context, readable timestamps with explicit timezones, and consistent action and receipt layouts.\n- Keep full schedule identifiers in secondary details while preserving existing ownership, confirmation, pagination, and retry controls."},{"version":"1.6.235","text":"### 定时任务沿用当前聊天上下文\n- Claude 和 DSH 定时任务在原聊天会话中执行,可沿用之前的讨论、后续消息和前几次执行的上下文。\n- 取消任务停止后续触发,不结束聊天会话;已经开始的执行仍可返回结果,同时到点的任务可能返回标明来源的合并结果。\n- Claude 周期任务需使用原生会话时区;本机服务重启后仍需重新创建中断的任务。","changes":[{"topic":"native-schedules","title":"定时任务","text":"Claude 和 DSH 定时任务在原聊天会话中执行,可沿用之前的讨论、后续消息和前几次执行的上下文。"},{"topic":"native-schedules","title":"定时任务","text":"取消任务停止后续触发,不结束聊天会话;已经开始的执行仍可返回结果,同时到点的任务可能返回标明来源的合并结果。"},{"topic":"native-schedules","title":"定时任务","text":"Claude 周期任务需使用原生会话时区;本机服务重启后仍需重新创建中断的任务。"}],"details":"### Changed\n- Execute Claude and DSH managed schedules in their original foreground native conversation, preserving earlier discussion, subsequent messages, and recurring-turn history without copying transcripts.\n- Authorize Claude Cron actions in the active model turn, serialize card/slash management on that session, and use native DSH host CRUD with occurrence-aware output routing.\n- Cancel future firings without terminating the shared conversation; retain already-started results and label native combined answers. Process-restart job restoration remains unsupported.\n- Require recurring Claude timing to match the native session timezone and reject ambiguous one-shot clock-rollback times without changing session settings."},{"version":"1.6.234","text":"### 用自然语言创建并管理定时任务\n- 可用自然语言请求 Claude 或 DSH 创建、查看和取消定时任务,无需开启多代理委派;时间或时区不明确时会先澄清。\n- 自然语言操作会单独返回管理卡片,保留助手正常回复;创建较慢时可查询进度,重试同一操作不会重复创建。\n- 耗时操作失败后会补充明确结果;卡片发送失败时可通过 /schedule list 恢复查看,无需重复创建任务。","changes":[{"topic":"native-schedules","title":"定时任务","text":"可用自然语言请求 Claude 或 DSH 创建、查看和取消定时任务,无需开启多代理委派;时间或时区不明确时会先澄清。"},{"topic":"native-schedules","title":"定时任务","text":"自然语言操作会单独返回管理卡片,保留助手正常回复;创建较慢时可查询进度,重试同一操作不会重复创建。"},{"topic":"native-schedules","title":"定时任务","text":"耗时操作失败后会补充明确结果;卡片发送失败时可通过 /schedule list 恢复查看,无需重复创建任务。"}],"details":"### Added\n- Add backend-neutral managed scheduling tools for natural-language creation, listing, cancellation, and bounded operation receipts, independently of delegation settings. Retain Claude and DSH native-provider admission and reject unsupported execution backends explicitly.\n- Deliver model-requested management cards separately from foreground answers with negotiated compatibility, captured ownership, replay fencing, and cleanup of newly created jobs when their turn context retires.\n\n### Fixed\n- Surface terminal failures after pending scheduling receipts, preserve scoped tools across authorized Codex model recovery, and reclaim completed receipt capacity without dropping pending operations."},{"version":"1.6.233","text":"### 在卡片上管理定时任务\n- 创建或查看定时任务后,可直接在卡片上刷新状态、确认取消,无需手动输入任务编号。\n- 取消操作等待本机确认;超时会提示结果未知,避免把仍在运行的任务显示为已取消。\n- 旧版本仍可使用原有命令;未使用定时任务时保持原有聊天流程。","changes":[{"topic":"native-schedules","title":"定时任务","text":"创建或查看定时任务后,可直接在卡片上刷新状态、确认取消,无需手动输入任务编号。"},{"topic":"native-schedules","title":"定时任务","text":"取消操作等待本机确认;超时会提示结果未知,避免把仍在运行的任务显示为已取消。"},{"topic":"native-schedules","title":"定时任务","text":"旧版本仍可使用原有命令;未使用定时任务时保持原有聊天流程。"}],"details":"### Added\n- Add interactive native schedule management cards with on-demand status refresh and confirmed cancellation through the CLI, retaining the original task owner and thread.\n- Negotiate schedule card controls separately, preserve text commands for older peers, and keep scheduling dormant until used.\n\n### Fixed\n- Treat timed-out card operations as unknown outcomes and retain cancellation retry when native process cleanup is unconfirmed."},{"version":"1.6.232","text":"### 定时任务回到原线程\n- 可用 /schedule 创建一次性或周期任务、查看状态和取消;支持具备原生定时能力的 Claude Code 和 DSH。\n- 任务结果回到原线程,断线时保留待投递结果;需保持本机服务运行,重启后未完成任务会标为中断,不自动重建。\n- 可查看全部八个后端的支持情况;暂不支持的后端会说明具体原因,不会自动切换到其他后端执行。\n- 未使用定时任务时不会创建任务数据或启动定时服务,日常聊天和重连保持原有流程。","changes":[{"topic":"native-schedules","title":"定时任务","text":"可用 /schedule 创建一次性或周期任务、查看状态和取消;支持具备原生定时能力的 Claude Code 和 DSH。"},{"topic":"native-schedules","title":"定时任务","text":"任务结果回到原线程,断线时保留待投递结果;需保持本机服务运行,重启后未完成任务会标为中断,不自动重建。"},{"topic":"native-schedules","title":"定时任务","text":"可查看全部八个后端的支持情况;暂不支持的后端会说明具体原因,不会自动切换到其他后端执行。"},{"topic":"native-schedules","title":"定时任务","text":"未使用定时任务时不会创建任务数据或启动定时服务,日常聊天和重连保持原有流程。"}],"details":"### Added\n- Add capability-based `/schedule` commands for native one-shot and recurring Claude and DSH tasks, with an isolated native process per schedule, explicit timezone handling, native create/list/cancel receipts, and lifecycle-correlated completion.\n- Persist task ownership, interrupted state, and bounded pending results; deliver acknowledged result cards to the original thread and retry after reconnect without adding a Router scheduler or model polling.\n- Add DSH native scheduler composition and an ACP event adapter with private job storage, correlated native terminal outcomes, and explicit cleanup. Preserve backend identity through catalog recovery and result delivery.\n- Report explicit scheduling eligibility for all eight backends and return version-specific reasons when native timing or existing-transport result delivery is unavailable. Keep list/cancel available after backend switches, and reject unavailable native capabilities, restricted sandbox configurations, and incompatible Routers explicitly.\n\n### Fixed\n- Keep scheduling initialization and delivery subscriptions dormant when no catalog exists. Recover persisted results after reconnect without creating schedule state for ordinary chat users; serialize first-use and recovery initialization and guard shutdown races.\n- Preserve already completed pending results when native processes report shutdown; distinguish service shutdown from ownership invalidation so offline recurring results can be delivered after restart."},{"version":"1.6.231","text":"### 点取文件即可申请授权\n- 尚未开启文件权限时,也可点击原来的 Get file 按钮发起授权,无需寻找旧提示或另外操作按钮。\n- 授权并重新连接后,可在原回复继续取文件;待处理附件仅临时保留,重启或开始新任务后可能需要重新请求。","changes":[{"topic":"output-files","title":"文件取回","text":"尚未开启文件权限时,也可点击原来的 Get file 按钮发起授权,无需寻找旧提示或另外操作按钮。"},{"topic":"output-files","title":"文件取回","text":"授权并重新连接后,可在原回复继续取文件;待处理附件仅临时保留,重启或开始新任务后可能需要重新请求。"}],"details":"### Added\n- Let the existing inline Get file button request device file approval when approval is missing, without adding a second button. Keep automatic enrollment reminders separate from explicit user requests.\n- Carry only the explicitly selected unverified reply across first-key approval, and prepare bounded process-local attachment intent after authenticated reconnection. Keep stale contexts, unavailable proof, revoked keys, and unknown delivery outcomes held without widening file access."},{"version":"1.6.230","text":"### 附件信息更清爽\n- 附件区去掉重复标题,单页不再显示页码;文件名、大小、状态和有效期分层展示,更容易浏览。","changes":[{"topic":"output-files","title":"文件取回","text":"附件区去掉重复标题,单页不再显示页码;文件名、大小、状态和有效期分层展示,更容易浏览。"}],"details":"### Changed\n- Simplify the inline Files panel to a single heading, show page numbers only for multiple pages, and separate filenames from subdued size, status, and absolute UTC expiry details."},{"version":"1.6.229","text":"### 附件入口更显眼\n- 回复中的文件面板默认展开,显示文件总数,并移到回答下方、线程切换按钮上方,取回和查看进度更方便。\n- 修复同时确认文件授权、手动更换密钥或解绑设备时,较早的授权可能覆盖新状态的问题。\n- 修复前面的失败子任务暂时无法清理时,后面可清理的子任务一直得不到处理的问题。","changes":[{"topic":"output-files","title":"文件取回","text":"回复中的文件面板默认展开,显示文件总数,并移到回答下方、线程切换按钮上方,取回和查看进度更方便。"},{"topic":"output-files","title":"文件取回","text":"修复同时确认文件授权、手动更换密钥或解绑设备时,较早的授权可能覆盖新状态的问题。"},{"topic":"delegation","title":"委派任务","text":"修复前面的失败子任务暂时无法清理时,后面可清理的子任务一直得不到处理的问题。"}],"details":"### Changed\n- Open inline Files panels expanded by default, with a clear heading and total attachment count above completion details and thread controls. Preserve ordering through continuation cards, streaming and selection refreshes, pagination, late offers, and saved-body recovery without changing retrieval authorization or expiry.\n\n### Fixed\n- Serialize automatic file approval, manual key enrollment, and unbinding across binding managers sharing one store, preventing stale approvals from restoring revoked access or overwriting a newer manually approved key.\n- Rotate bounded failed-worker cleanup retries across candidates so persistent safety holds do not indefinitely block later eligible checkouts, while retaining all existing disposal guards."},{"version":"1.6.228","text":"### 后台结束通知不再刷屏\n- Claude Code 和 Codex 的后台任务结束后不再单独弹出通知卡片,主回复、后台执行和必要的授权与输入提示照常保留。","changes":[{"topic":"agent-activity","title":"运行进度","text":"Claude Code 和 Codex 的后台任务结束后不再单独弹出通知卡片,主回复、后台执行和必要的授权与输入提示照常保留。"}],"details":"### Changed\n- Retire standalone native background-task terminal notifications. The CLI stops forwarding Claude Code hooks and Codex completion callbacks, and the Router quietly drops legacy `task_notification` frames without cards, text fallback, reply associations, or task/recipient logging. Legacy notification options cannot restore this presentation.\n- Preserve native background execution, completion consumption and deduplication, main response/tool flow, actionable approvals and input prompts, managed worker progress and closeout, and inline file retrieval. Keep the generic card sender and legacy wire types for their remaining callers and compatibility."},{"version":"1.6.227","text":"### 文件取回留在原回复中\n- 新附件的取回按钮、传输状态和重试入口集中在原助手卡片中,多份文件可翻页查看,避免额外刷出文件卡片。\n- 未启用或尚未获批时显示灰色入口,不读取本地文件;内部导出失败不再单独弹出笼统计数提示。\n- 引导助手把交付文件放在已授权工作区的可见目录,减少因隐藏或未授权位置导致的附件准备失败。","changes":[{"topic":"output-files","title":"文件取回","text":"新附件的取回按钮、传输状态和重试入口集中在原助手卡片中,多份文件可翻页查看,避免额外刷出文件卡片。"},{"topic":"output-files","title":"文件取回","text":"未启用或尚未获批时显示灰色入口,不读取本地文件;内部导出失败不再单独弹出笼统计数提示。"},{"topic":"output-files","title":"文件取回","text":"引导助手把交付文件放在已授权工作区的可见目录,减少因隐藏或未授权位置导致的附件准备失败。"}],"details":"### Changed\n- Show new output files, manual retrieval, transfer state, and valid retries inside the original assistant execution card. Bind controls to its actual final continuation, preserve the full card body through serialized updates, and retain bounded private parent-body receipts for late offers and restart recovery. Paginate file rows without dropping selections.\n- Display negotiated, basename-only unavailable controls when file retrieval is disabled, unapproved, or unsupported, without reading or snapshotting candidate files. Existing approved offline references retain queueing and cached-copy delivery; hints never authorize bytes or prove file existence.\n- Suppress count-only preparation alerts, including legacy discovery frames. Keep bounded internal reason codes and hashed request/path correlations, and guide assistants to prepare visible deliverables in the approved workspace or an explicitly authorized export root. Preserve path guards, original device ownership, quotas, expiry, legacy published cards, and unknown-send protections."},{"version":"1.6.226","text":"### 只为交付附件显示取回按钮\n- 普通源码引用不再生成取回卡片或文件不可用提示,只有助手明确作为附件交付的文件才会显示按钮;源码文件也可作为附件交付。\n- 子任务文件仍可在临时目录清理后由主助手选为附件,已生成的取回卡片保持可用。","changes":[{"topic":"output-files","title":"文件取回","text":"普通源码引用不再生成取回卡片或文件不可用提示,只有助手明确作为附件交付的文件才会显示按钮;源码文件也可作为附件交付。"},{"topic":"output-files","title":"文件取回","text":"子任务文件仍可在临时目录清理后由主助手选为附件,已生成的取回卡片保持可用。"}],"details":"### Changed\n- Require the exact Markdown link title `attachment` for newly selected output files. Ordinary source citations no longer produce Get file cards or unavailable notices, while deliberate source-file attachments remain supported.\n- Discover public attachment intent only from trusted assistant text, including native final-only replies, rather than aggregate backend diagnostics. Teach the selection syntax on each capability-enabled coordinator request without changing saved configuration.\n- Keep ordinary worker links as private snapshots for explicit coordinator selection after workspace reclamation. Existing published receipts, transfer permissions, quotas, and expiry remain compatible."},{"version":"1.6.225","text":"### 子任务故障自动收尾\n- Linux 上无法生成产物的已结束子任务会自动清理临时工作区,避免后续对话反复报收尾错误;如需其中内容,可重新运行子任务。","changes":[{"topic":"delegation","title":"委派任务","text":"Linux 上无法生成产物的已结束子任务会自动清理临时工作区,避免后续对话反复报收尾错误;如需其中内容,可重新运行子任务。"}],"details":"### Fixed\n- Automatically dispose of verified, terminated worker checkouts when artifact capture fails, persist completion receipts, and stop repeating unavailable-artifact closeout errors. Pending deliverables and external symlink targets retain their existing protections."},{"version":"1.6.224","text":"### 文件授权更省事,取回卡片更清晰\n- 后台子任务的内部文件和导出失败提示不再刷屏,只展示主助手选定的交付文件;临时目录清理后仍可取回已保存的文件快照。\n- 旧设备升级后自动申请文件授权,在飞书确认一次即可启用;已完成授权的设备不会重复提示,无需再到终端执行启用命令。\n- 文件名、大小和有效期分层显示,取回及重试按钮更醒目,传输中、成功、失败和结果不明有清晰的状态提示。","changes":[{"topic":"output-files","title":"文件取回","text":"后台子任务的内部文件和导出失败提示不再刷屏,只展示主助手选定的交付文件;临时目录清理后仍可取回已保存的文件快照。"},{"topic":"output-files","title":"文件取回","text":"旧设备升级后自动申请文件授权,在飞书确认一次即可启用;已完成授权的设备不会重复提示,无需再到终端执行启用命令。"},{"topic":"output-files","title":"文件取回","text":"文件名、大小和有效期分层显示,取回及重试按钮更醒目,传输中、成功、失败和结果不明有清晰的状态提示。"}],"details":"### Added\n- Automatically request file-key approval for eligible initialized devices and let the existing bound owner approve from a Feishu card. Skip approved devices, retain manual enrollment, and persist an explicit CLI automatic-enrollment opt-out.\n\n### Changed\n- Keep worker file snapshots internal until explicit coordinator selection, suppress worker-only export notices, and preserve hidden publication state across reconnects and restarts.\n- Restyle output-file entries and standalone transfer cards with status-colored headers, primary actions, readable file sizes and absolute UTC expiry times, and clear delivery confirmations. Preserve callback payloads, transfer state, retry boundaries, and uncertain-send protection."},{"version":"1.6.223","text":"### 首次绑定时一并启用文件能力\n- 新设备直接运行 `remote-cli init` 即会申请文件授权,仍需在飞书确认后启动;`--with-files` 保持兼容,无需再单独执行启用命令。\n- 旧 Router 或非本机 HTTP 的纯文本初始化需明确添加 `--without-files`;文件授权仍需 HTTPS 和支持该能力的 Router,失败时不会自动降级。","changes":[{"topic":"output-files","title":"文件取回","text":"新设备直接运行 `remote-cli init` 即会申请文件授权,仍需在飞书确认后启动;`--with-files` 保持兼容,无需再单独执行启用命令。"},{"topic":"output-files","title":"文件取回","text":"旧 Router 或非本机 HTTP 的纯文本初始化需明确添加 `--without-files`;文件授权仍需 HTTPS 和支持该能力的 Router,失败时不会自动降级。"}],"details":"### Added\n- Make `remote-cli init` request device binding and file-key approval by default with one Feishu binding code. Keep `--with-files` as a compatibility alias and require explicit `--without-files` for legacy text-only initialization; conflicting flags are rejected before initialization.\n- Reuse locally persisted device identities for retries and forced initialization; require an explicit secure-enrollment response without redirect or credentialless fallback.\n\n### Fixed\n- Persist an authentication requirement before first-device key enrollment, retain failed approvals for owner retry, and reject credentialless connections during enrollment and after restart. Sync approved keys before clearing the requirement and exclude sockets whose authentication outlives their connection."},{"version":"1.6.222","text":"### 补齐 Linux ARM64 文件取回支持\n- 安装包补齐 Linux ARM64 组件,修复该架构因缺少组件而无法启用文件取回的问题;仍需完成 HTTPS 连接和设备授权。","changes":[{"topic":"output-files","title":"文件取回","text":"安装包补齐 Linux ARM64 组件,修复该架构因缺少组件而无法启用文件取回的问题;仍需完成 HTTPS 连接和设备授权。"}],"details":"### Fixed\n- Include Linux arm64 native helpers in the CLI package so output-file retrieval can create snapshots on that architecture.\n- Build and test Linux arm64 helpers on a native CI runner, retain the minimum Node.js compatibility check, and require all six platform/architecture artifacts with matching source and binary hashes before publication."},{"version":"1.6.221","text":"### 从回复中取回本地文件\n- 回复中的合规本地文件链接可生成取回按钮,点击后通过独立任务卡片查看传输状态,并接收飞书文件。\n- 文件快照最多 20 MiB、保留 24 小时;支持离线等待和可确认失败的重试,发送结果不明时避免重复发送。\n- macOS 清理遇到暂时无法确认的进程状态时,在原有期限内继续确认;仍无法确认退出时保留数据。","changes":[{"topic":"output-files","title":"文件取回","text":"回复中的合规本地文件链接可生成取回按钮,点击后通过独立任务卡片查看传输状态,并接收飞书文件。"},{"topic":"output-files","title":"文件取回","text":"文件快照最多 20 MiB、保留 24 小时;支持离线等待和可确认失败的重试,发送结果不明时避免重复发送。"},{"topic":"delegation","title":"委派任务","text":"macOS 清理遇到暂时无法确认的进程状态时,在原有期限内继续确认;仍无法确认退出时保留数据。"}],"details":"### Added\n- Capture bounded immutable output-file snapshots from explicit assistant Markdown links, with native handle-relative reads and managed worker disposal fencing.\n- Add authenticated CLI-to-Router HTTP streaming, durable original-device references and transfer receipts, separate file-entry and progress cards, and native Feishu file delivery.\n- Preserve retryable failures and uncertain external send outcomes across restarts without replaying delivered files; enforce fixed expiry, storage quotas, and transfer concurrency limits.\n\n### Fixed\n- Keep inconclusive macOS process-group permission probes pending within the existing exit-confirmation deadline; require kernel absence before cleanup and report only recognized error codes.\n- Give multi-operation delegation fixtures independent phase deadlines and drain timed-out work before teardown."},{"version":"1.6.220","text":"### 更清楚地追查消息发送和恢复问题\n- 增加卡片大小、发送结果和更新差异的诊断记录,不记录卡片正文或请求凭据。\n- 关联任务结果确认、恢复等待与连接关闭记录,帮助区分卡片发送失败和连接中断。","changes":[{"topic":"delivery-diagnostics","title":"消息诊断","text":"增加卡片大小、发送结果和更新差异的诊断记录,不记录卡片正文或请求凭据。"},{"topic":"delivery-diagnostics","title":"消息诊断","text":"关联任务结果确认、恢复等待与连接关闭记录,帮助区分卡片发送失败和连接中断。"}],"details":"### Changed\n- Add bounded, metadata-only diagnostics for Feishu card delivery, including serialized UTF-8 sizes, delivery outcomes, and changes since the last successful update.\n- Correlate task-result acknowledgements, recovery timers, and WebSocket closure events to distinguish card delivery failures from connection interruptions.\n- Redact SDK delivery error logging so diagnostic events do not include card contents or request credentials."},{"version":"1.6.219","text":"### Windows 和 macOS 子会话清理\n- 补充 Windows 和 macOS 的受管子会话自动清理,保留代码成果及导出文件。\n- 清理前确认子进程退出;遇到归属冲突或退出状态不明时保留历史和恢复记录。","changes":[{"topic":"delegation","title":"委派任务","text":"补充 Windows 和 macOS 的受管子会话自动清理,保留代码成果及导出文件。"},{"topic":"delegation","title":"委派任务","text":"清理前确认子进程退出;遇到归属冲突或退出状态不明时保留历史和恢复记录。"}],"details":"### Added\n- Add Windows Job containment and macOS native process identity checks for managed worker and cleanup-process shutdown.\n- Add handle-relative native history deletion and bounded artifact reads on Windows and macOS, preserving recorded ownership, generation, retry, and deliverable checks.\n- Build and test bundled Node-API helpers on native x64 and arm64 runners; package validation requires matching platform binaries without install-time compilation.\n\n### Fixed\n- Enable compatible managed history capture on Windows and macOS and honor the private AGY user profile on Windows.\n- Record confirmed managed-tree exit in the ownership journal while retaining interrupted launches whose native evidence was lost."},{"version":"1.6.218","text":"### 重启后保留线程卡片操作\n- 新版 Router 保存卡片关联,重启后仍可在原有七天有效期内点击线程切换或回复卡片。\n- 切换前确认目标线程仍存在;已过期、已失效或升级前丢失关联的卡片可通过 `/thread list` 重新获取。\n- 切换保存较慢时提示等待确认,避免先显示失败却在后台切换线程。","changes":[{"topic":"thread-selection","title":"线程选择","text":"新版 Router 保存卡片关联,重启后仍可在原有七天有效期内点击线程切换或回复卡片。"},{"topic":"thread-selection","title":"线程选择","text":"切换前确认目标线程仍存在;已过期、已失效或升级前丢失关联的卡片可通过 `/thread list` 重新获取。"},{"topic":"thread-selection","title":"线程选择","text":"切换保存较慢时提示等待确认,避免先显示失败却在后台切换线程。"}],"details":"### Fixed\n- Preserve bounded card-to-thread routing associations across Router restarts within their original seven-day lifetime.\n- Validate thread-switch destinations against the connected device's current catalog and retain ownership checks and durable invalidation.\n- Keep asynchronous thread validation cancellable through timeout and disconnect, and avoid invalidating fresh cards after delayed device-switch notifications.\n- Remove all active continuation-card routes on interruption, retry failed removals, and preserve queue confirmations when route persistence fails before dispatch.\n- Distinguish cancellation before selection-save admission from pending or uncertain persistence, and report late durable outcomes without replaying a switch.\n\n### Tests\n- Cover persisted Router recreation, card expiry, ownership changes, invalidation, and ordinary thread routing with isolated fixtures."},{"version":"1.6.217","text":"### 扩展子代理会话清理\n- Linux 上为新建的 OpenCode、AGY、DSH 和 ZCode 子会话增加清理支持,主会话 clear 或 new 后按归属和退出状态清理。\n- 保留子代理的代码和交付物,清理条件不足时保留记录并说明原因。\n- 修复清理维护进程退出状态和不同后端会话标识的持久化处理。\n- 旧 AGY 子会话即使暂时无法清理,也能继续正常执行任务。","changes":[{"topic":"delegation-sessions","title":"子代理会话","text":"Linux 上为新建的 OpenCode、AGY、DSH 和 ZCode 子会话增加清理支持,主会话 clear 或 new 后按归属和退出状态清理。"},{"topic":"delegation-sessions","title":"子代理会话","text":"保留子代理的代码和交付物,清理条件不足时保留记录并说明原因。"},{"topic":"delegation-sessions","title":"子代理会话","text":"修复清理维护进程退出状态和不同后端会话标识的持久化处理。"},{"topic":"delegation-sessions","title":"子代理会话","text":"旧 AGY 子会话即使暂时无法清理,也能继续正常执行任务。"}],"details":"### Added\n- Extend managed child-session retirement to OpenCode, AGY, DSH, and ZCode using recorded creation ownership and backend-specific history or protocol checks, without pinning installed package versions.\n- Preserve native deliverables independently before ZCode history deletion and isolate new managed DSH history storage while retaining normal authentication and configuration sources.\n\n### Fixed\n- Persist maintenance-writer fences for Codex cleanup and retain them when process-group shutdown cannot be confirmed.\n- Persist deletion preparations for backend-native session identifiers rather than requiring every backend to use UUIDs.\n- Preserve ordinary AGY execution in legacy shared-cache lanes while holding cleanup, and reject case-only aliases of adopted native identities.\n\n### Tests\n- Cover native creation, reused worker contexts, durable cleanup recovery, retained outputs, and synthetic filesystem boundaries."},{"version":"1.6.216","text":"### 修复子会话清理被无关记录阻塞\n- 修复无关的非原生 Codex 会话记录可能阻止正常子会话清理的问题,保留归属和退出状态保护。\n- 清理无法继续时提供更明确的失败阶段,便于定位原因。","changes":[{"topic":"delegation-sessions","title":"子代理会话","text":"修复无关的非原生 Codex 会话记录可能阻止正常子会话清理的问题,保留归属和退出状态保护。"},{"topic":"delegation-sessions","title":"子代理会话","text":"清理无法继续时提供更明确的失败阶段,便于定位原因。"}],"details":"### Fixed\n- Prevent provably unrelated non-native Codex pointer IDs from blocking eligible managed-worker cleanup while preserving target identity, alias, filesystem, shutdown, and retry checks.\n- Report bounded cleanup validation stages without exposing private paths or raw backend errors.\n\n### Tests\n- Isolate activity fixtures from real backend homes and cover unrelated pointers, ambiguous ownership, and cleanup recovery with synthetic data."},{"version":"1.6.215","text":"### 放宽子会话清理的版本要求\n- Kimi 和 Claude 子会话清理按实际接口能力和历史格式判断,不再绑定某一个安装版本。\n- 兼容升级前保存的清理记录,仍保留会话归属和退出状态检查。","changes":[{"topic":"delegation-sessions","title":"子代理会话","text":"Kimi 和 Claude 子会话清理按实际接口能力和历史格式判断,不再绑定某一个安装版本。"},{"topic":"delegation-sessions","title":"子代理会话","text":"兼容升级前保存的清理记录,仍保留会话归属和退出状态检查。"}],"details":"### Fixed\n- Determine managed Kimi and Claude session cleanup compatibility from deletion capabilities and validated history formats instead of exact installed backend versions.\n- Preserve existing owned-session identities and immutable deletion receipts across compatible backend upgrades; retain ownership, shutdown, path, and retry safeguards.\n\n### Tests\n- Cover compatible version labels, incompatible capabilities and history layouts, and recovery with legacy deletion records using isolated synthetic fixtures."},{"version":"1.6.214","text":"### 修复 Codex 子会话清理兼容性\n- 清理 Codex 子会话时按实际接口能力判断,不再限定必须使用某一个 Codex 版本。\n- 保留已有清理记录,归属不明确或尚未确认退出的会话仍不会被误删。","changes":[{"topic":"delegation-sessions","title":"子代理会话","text":"清理 Codex 子会话时按实际接口能力判断,不再限定必须使用某一个 Codex 版本。"},{"topic":"delegation-sessions","title":"子代理会话","text":"保留已有清理记录,归属不明确或尚未确认退出的会话仍不会被误删。"}],"details":"### Fixed\n- Determine managed Codex session cleanup compatibility from native protocol behavior and validated metadata instead of rejecting every server version except 0.166.0.\n- Preserve exact ownership and shutdown checks, and retain existing deletion preparations when retrying cleanup after an upgrade.\n\n### Tests\n- Cover compatible version labels, unavailable methods, invalid acknowledgements, legacy receipt recovery, and ambiguous deletion failures.\n- Verify Codex 0.165.0 list/read/delete and exact missing-target responses using isolated synthetic histories without model calls or real user history access."},{"version":"1.6.213","text":"### 修复 Windows 子代理运行\n- 修复 Windows 保存子代理状态时可能失败的问题,保留原有会话清理与恢复保护。","changes":[{"topic":"delegation-sessions","title":"子代理会话","text":"修复 Windows 保存子代理状态时可能失败的问题,保留原有会话清理与恢复保护。"}],"details":"### Fixed\n- Preserve managed worker metadata durability with file handles that support flushing on Windows, without suppressing write or synchronization failures.\n\n### Tests\n- Keep host-native storage and ownership behavior in cleanup fixtures, and verify quarantined initialization before any worker is constructed."},{"version":"1.6.212","text":"### 更多子代理会话可自动清理\n- 扩展 Kimi、Pi 和 Claude 子会话清理:清空或新建主会话后,清理归属明确且已退出的旧子会话。\n- 清空前仍可复用上下文;任务结果、代码产物和恢复记录继续保留,不改为归档。\n- 退出未确认、旧会话或暂不支持的情况保留待处理状态,不删除来源不明的会话。","changes":[{"topic":"delegation-sessions","title":"子代理会话","text":"扩展 Kimi、Pi 和 Claude 子会话清理:清空或新建主会话后,清理归属明确且已退出的旧子会话。"},{"topic":"delegation-sessions","title":"子代理会话","text":"清空前仍可复用上下文;任务结果、代码产物和恢复记录继续保留,不改为归档。"},{"topic":"delegation-sessions","title":"子代理会话","text":"退出未确认、旧会话或暂不支持的情况保留待处理状态,不删除来源不明的会话。"}],"details":"### Changed\n- Extend parent-reset cleanup to newly owned Kimi, Pi, and Claude delegated sessions, retaining context reuse until `/clear` or `/new` and preserving task artifacts and recovery records.\n- Use backend-specific native deletion or exact owned history paths, with durable ownership receipts and retry state instead of archiving or deleting shared session stores.\n- Keep unsupported platforms, unconfirmed shutdown, adopted sessions, and ambiguous ownership outside automatic deletion.\n\n### Tests\n- Cover managed creation receipts, parent-reset generations, adopted-history conflicts, partial deletion recovery, and maintenance exit fencing with isolated synthetic fixtures.\n- Reproduce parent-directory substitution and detached-pointer file conflicts; verify descriptor-anchored removal, procfs failure handling, and handle cleanup."},{"version":"1.6.211","text":"### 清空主会话时清理子代理\n- 清空或新建主会话时,请求清理旧子代理会话;清空前仍可复用子代理的上下文。\n- 首版支持 Linux 上新产生且校验通过的 Codex 0.166.0 子会话;旧会话、其他后端等暂不支持的情况会保留状态,不改为归档。\n- 任务结果、代码产物和恢复记录继续保留,不随会话历史删除。","changes":[{"topic":"delegation-sessions","title":"子代理会话","text":"清空或新建主会话时,请求清理旧子代理会话;清空前仍可复用子代理的上下文。"},{"topic":"delegation-sessions","title":"子代理会话","text":"首版支持 Linux 上新产生且校验通过的 Codex 0.166.0 子会话;旧会话、其他后端等暂不支持的情况会保留状态,不改为归档。"},{"topic":"delegation-sessions","title":"子代理会话","text":"任务结果、代码产物和恢复记录继续保留,不随会话历史删除。"}],"details":"### Changed\n- Initially support newly recorded Codex 0.166.0 sessions on Linux with confirmed process-group exit and no native descendants. Preserve explicit holds for legacy identities, unsupported versions/platforms/backends, and uncertain ownership.\n- Request permanent deletion of owned delegated-worker native sessions when the parent conversation is cleared with `/clear` or `/new`, while preserving context reuse before reset and retaining task artifacts and recovery records.\n- Track deferred cleanup separately from conversation reset; require confirmed shutdown and supported native deletion, and retain explicit failure or unsupported state instead of archiving or claiming pointer removal deleted native history.\n\n### Tests\n- Cover parent reset races, native ownership retained across worker resets, incomplete exit evidence, bounded recovery receipts, and lost deletion acknowledgements with realistic native metadata fixtures.\n- Verify Codex 0.166.0 deletion and missing-target retry against synthetic histories in an isolated native home without model calls or real user history access."},{"version":"1.6.210","text":"### 子代理提示更精简\n- 复用子代理会话时,不再重复发送已确认接收的固定说明,保留已有上下文。\n- 每项任务仍提供最新目标和工作目录等信息;新会话或初始化未确认时重新发送完整说明。","changes":[{"topic":"delegation-prompts","title":"子代理提示","text":"复用子代理会话时,不再重复发送已确认接收的固定说明,保留已有上下文。"},{"topic":"delegation-prompts","title":"子代理提示","text":"每项任务仍提供最新目标和工作目录等信息;新会话或初始化未确认时重新发送完整说明。"}],"details":"### Changed\n- Send fixed delegated-worker instructions once per confirmed native conversation while refreshing task objectives, workspace/checkpoint details, external-link warnings, and export requirements on every task.\n- Restore full instructions for fresh or unconfirmed contexts, including missing-history fallback and failed initialization, without disabling worker conversation reuse.\n\n### Tests\n- Cover prompt initialization across executor recreation, manager restart, context reset, missing pointers, native fallback, and refreshed Git task metadata."},{"version":"1.6.209","text":"### 外部软链接直接可用\n- 新子任务可直接使用普通外部软链接,无需逐条配置白名单;保留链接及原来的目标,不复制目标内容。\n- 保留自动回写和清理时的目录检查;外部目标中的修改仍不会进入任务产物或随任务回滚。","changes":[{"topic":"delegation-symlinks","title":"子任务软链接","text":"新子任务可直接使用普通外部软链接,无需逐条配置白名单;保留链接及原来的目标,不复制目标内容。"},{"topic":"delegation-symlinks","title":"子任务软链接","text":"保留自动回写和清理时的目录检查;外部目标中的修改仍不会进入任务产物或随任务回滚。"}],"details":"### Changed\n- Admit ordinary external symbolic links in new managed Git tasks without requiring per-link grants. Preserve original link text in checkpoints and the original external target in worker checkouts without copying target contents.\n- Keep external target edits outside artifact review, integration, and rollback. Retain link identity, protected-target, and automatic write and cleanup checks, including recorded policies for existing artifacts.\n\n### Tests\n- Cover automatic external-link admission, target-preserving checkout mapping, link-only artifacts, and guarded closeout and lane reuse."},{"version":"1.6.208","text":"### 授权无需重启\n- 新增或移除外部软链接授权后,新子任务直接读取最新配置,无需重启 CLI 或会话;已有任务继续按启动时的授权完成收尾。\n- 保存后端等其他设置时保留磁盘中的最新授权,避免丢失新授权或恢复已撤销的授权。\n- 延长上传后的版本确认等待时间,适应 npm 发布扫描延迟,避免误报失败;不会重复上传。","changes":[{"topic":"delegation-symlinks","title":"子任务软链接","text":"新增或移除外部软链接授权后,新子任务直接读取最新配置,无需重启 CLI 或会话;已有任务继续按启动时的授权完成收尾。"},{"topic":"delegation-symlinks","title":"子任务软链接","text":"保存后端等其他设置时保留磁盘中的最新授权,避免丢失新授权或恢复已撤销的授权。"},{"topic":"npm-publishing","title":"自动发布","text":"延长上传后的版本确认等待时间,适应 npm 发布扫描延迟,避免误报失败;不会重复上传。"}],"details":"### Fixed\n- Read shared-symlink grants from the current local configuration before each new managed Git task without requiring a CLI or conversation restart.\n- Keep running tasks and saved artifacts pinned to their recorded policy, and reject invalid or unreadable policy without falling back to stale grants or rewriting configuration.\n- Preserve current on-disk grants during unrelated configuration saves, including additions, revocations, and invalid policy, instead of restoring stale runtime grants.\n- Allow ten minutes of post-upload registry confirmation polling for npm publish-time scanning while retaining single uploads, integrity checks, and immediate failure on lookup errors.\n\n### Tests\n- Cover same-instance grant addition and removal, missing and malformed configuration, sanitized failures, and unchanged in-memory settings and configuration files."},{"version":"1.6.207","text":"### 兼容 Windows 软链接\n- 修复 Windows 下软链接文本转换导致子任务启动失败的问题,保留链接语义与目录边界检查。","changes":[{"topic":"delegation-symlinks","title":"子任务软链接","text":"修复 Windows 下软链接文本转换导致子任务启动失败的问题,保留链接语义与目录边界检查。"}],"details":"### Fixed\n- Preserve native symbolic-link semantics using Git-compatible Windows separators in checkpoint indexes and checkout verification, retaining alias components, canonical containment, and link-identity checks.\n\n### Tests\n- Cover native link-text conversion, replacement during opaque index insertion, and internal-link collection, reclamation, and lane reuse.\n- Bound each large-repository lifecycle test phase separately and drain unfinished work before removing its fixture."},{"version":"1.6.206","text":"### 保留子任务软链接\n- 修复目录改为仓库内软链接后子任务启动失败的问题,保留链接及主工作区的暂存状态。\n- 可按仓库和链接逐项授权外部共享目标,子任务保留链接而不复制内容;通过链接修改的共享内容不会进入任务产物或回滚。","changes":[{"topic":"delegation-symlinks","title":"子任务软链接","text":"修复目录改为仓库内软链接后子任务启动失败的问题,保留链接及主工作区的暂存状态。"},{"topic":"delegation-symlinks","title":"子任务软链接","text":"可按仓库和链接逐项授权外部共享目标,子任务保留链接而不复制内容;通过链接修改的共享内容不会进入任务产物或回滚。"}],"details":"### Added\n- Add exact local grants for shared external symbolic links, preserving original link text in artifacts and mapping owned worker links to their original targets without copying target contents.\n- Snapshot link policy with worker artifacts and disclose that shared-target edits occur directly outside artifact collection and rollback.\n\n### Fixed\n- Preserve repository-local symbolic links when a tracked directory is replaced, without traversing stale indexed child paths or modifying the source index.\n\n### Tests\n- Cover symbolic-link replacements, ignored tracked replacements, unchanged source state, and rejected external targets.\n- Verify explicit shared-link grants, direct content edits, logical artifact trees, restart and lane reuse, protected cleanup, bounded policy records, and typed configuration repair.\n- Reject shared-link directory races without staging payload blobs or enumerating shared paths, and keep unrelated project grants independent."},{"version":"1.6.205","text":"### 加固 Router 对外入口\n- 隐藏公开健康接口中的设备标识,卡片操作统一通过飞书长连接处理,并限制异常绑定请求和未注册连接;保留旧版 CLI 的正常注册方式。","changes":[{"topic":"router-security","title":"Router 安全","text":"隐藏公开健康接口中的设备标识,卡片操作统一通过飞书长连接处理,并限制异常绑定请求和未注册连接;保留旧版 CLI 的正常注册方式。"}],"details":"### Security\n- Remove device identifiers from public health responses and retire the unauthenticated HTTP card callback; Feishu card actions continue through the native long connection.\n- Bound binding requests and unregistered WebSocket admission while retaining legacy device registration and existing enrolled-device proofs.\n\n### Tests\n- Cover health redaction, rejected HTTP callback ingress, bounded admission, registration deadlines, resource release, and legacy reconnect compatibility."},{"version":"1.6.204","text":"### 看清 Claude 模型映射\n- 模型列表显示别名对应的实际模型标识并保留供应商前缀,方便区分同名选项;模型选择和调用方式不变。","changes":[{"topic":"claude-model-labels","title":"Claude 模型名称","text":"模型列表显示别名对应的实际模型标识并保留供应商前缀,方便区分同名选项;模型选择和调用方式不变。"}],"details":"### Changed\n- Show Claude Code model aliases alongside their native resolved model IDs, preserving provider prefixes and falling back to native names when resolution is unavailable. Keep direct/default labels, selection values, native metadata, and other backends unchanged.\n\n### Tests\n- Cover alias labels, provider preservation, fallback and bounds handling, and unchanged model selection and native metadata."},{"version":"1.6.203","text":"### 保留 Codex 原生请求标识\n- 使用 Codex 后端时保留原生 app-server 的 User-Agent,不再附加 remote-cli 标识;无需升级 Router。","changes":[{"topic":"codex-user-agent","title":"Codex 请求标识","text":"使用 Codex 后端时保留原生 app-server 的 User-Agent,不再附加 remote-cli 标识;无需升级 Router。"}],"details":"### Changed\n- Preserve native Codex app-server User-Agent construction during initialization instead of adding the remote-cli client identity. Keep product metadata and global Codex configuration unchanged.\n\n### Tests\n- Cover native-preserving initialization, inherited process settings, Codex version detection, and rejected-handshake cleanup/retry without model requests."},{"version":"1.6.202","text":"### 自动执行时减少提问打断\n- Kimi 默认启用原生 Never Ask,OpenCode 默认关闭提问工具;关闭自动批准后保留交互模式,无需升级 Router。","changes":[{"topic":"backend-automation","title":"后端自动执行","text":"Kimi 默认启用原生 Never Ask,OpenCode 默认关闭提问工具;关闭自动批准后保留交互模式,无需升级 Router。"}],"details":"### Changed\n- Apply Kimi native Never Ask mode before new and restored automatically approved sessions receive a task; preserve explicit manual approval behavior and reject unconfirmed mode setup.\n- Disable the OpenCode question tool for automatically approved managed processes without changing global backend configuration or other backends.\n\n### Tests\n- Cover native mode configuration, resumed sessions, initialization failures, and process-local question policies with synthetic ACP fixtures."},{"version":"1.6.201","text":"### 修复 Windows 路径与存储兼容性\n- 修复 Windows 下目录选择、子任务工作区和 Router 提示存储的兼容问题,保留 Linux 与 macOS 的路径和文件安全检查。","changes":[{"topic":"windows-compatibility","title":"Windows 兼容性","text":"修复 Windows 下目录选择、子任务工作区和 Router 提示存储的兼容问题,保留 Linux 与 macOS 的路径和文件安全检查。"}],"details":"### Fixed\n- Handle Windows filesystem and Git path representations without relaxing canonical-path, symbolic-link, or ownership validation on Linux and macOS.\n- Apply POSIX permission-bit checks only where those bits represent filesystem permissions, retaining structural validation of private Router storage.\n- Use Windows named pipes for approval IPC tests and short private Unix socket paths, with cleanup and retry after failed listener startup. Native Windows Claude sandboxing remains unsupported.\n\n### Tests\n- Use native temporary paths, explicit symbolic-link types, and platform-appropriate executable and permission fixtures across the CLI and Router suites.\n- Keep native Linux, macOS, and Windows build/test jobs as the release gate."},{"version":"1.6.200","text":"### 推送新版本后自动发布\n- 更新版本号并推送到 GitHub 主分支后,自动完成检查和两个 npm 包的发布,无需每次手动点击;保留手动重跑入口。\n- 发布后短暂查不到新版本时会等待确认,避免缓存延迟造成误报,不重复上传。","changes":[{"topic":"npm-publishing","title":"自动发布","text":"更新版本号并推送到 GitHub 主分支后,自动完成检查和两个 npm 包的发布,无需每次手动点击;保留手动重跑入口。"},{"topic":"npm-publishing","title":"自动发布","text":"发布后短暂查不到新版本时会等待确认,避免缓存延迟造成误报,不重复上传。"}],"details":"### Changed\n- Automatically publish both npm packages when a push to GitHub main increases the synchronized root package version. Compare against the push event's prior revision so multi-commit pushes are handled correctly.\n- Retain manual release recovery, skip unchanged versions, and reject invalid versions, downgrades, or unreadable prior revisions before publishing.\n- Bypass registry caches and poll for bounded post-publish visibility so a temporarily missing version does not immediately abort a successful upload; retain exact integrity matching and never automatically repeat the upload."},{"version":"1.6.199","text":"### 通过 GitHub 发布 npm 包\n- 支持在 GitHub Actions 手动触发两个包的发布;完成一次可信发布配置后,无需每次在本机登录 npm。\n- 发布前检查版本并运行构建和测试;部分发布成功后,可从原记录重跑,核对内容一致后继续发布剩余包。","changes":[{"topic":"npm-publishing","title":"自动发布","text":"支持在 GitHub Actions 手动触发两个包的发布;完成一次可信发布配置后,无需每次在本机登录 npm。"},{"topic":"npm-publishing","title":"自动发布","text":"发布前检查版本并运行构建和测试;部分发布成功后,可从原记录重跑,核对内容一致后继续发布剩余包。"}],"details":"### Added\n- Add a manually triggered GitHub Actions workflow for npm trusted publishing of both public packages, with locked dependencies, build/test gates, synchronized release-version checks, and exact package-integrity checks before skipping an already published version.\n- Reconcile uncertain publish outcomes against the registry without automatically repeating a publish request; reject conflicting versions and ambiguous registry failures.\n\n### Changed\n- Correct package repository attribution to the public GitHub repository and document one-time trusted-publisher setup and partial-release recovery."},{"version":"1.6.198","text":"### 旧子任务记录不再阻塞新委派\n- 个别旧记录损坏、无法读取或格式不兼容时,仍可启动新子任务;保留旧记录和历史,不自动复用异常记录,无需离线迁移。\n- 修复删除默认线程时报错前已清理会话数据的问题;现在会先拒绝操作,保留默认线程的会话和子任务。","changes":[{"topic":"delegation-runtime","title":"子任务委派","text":"个别旧记录损坏、无法读取或格式不兼容时,仍可启动新子任务;保留旧记录和历史,不自动复用异常记录,无需离线迁移。"},{"topic":"thread-controls","title":"线程切换","text":"修复删除默认线程时报错前已清理会话数据的问题;现在会先拒绝操作,保留默认线程的会话和子任务。"}],"details":"### Fixed\n- Allow fresh worker allocation despite unreadable or incompatible individual historical lane records. Preserve excluded records and native history, report incomplete inventory, and retain ownership, live-writer, and destructive-cleanup safeguards.\n- Reject attempts to delete the default thread before cancelling work, closing bridges, removing worker records, or deleting native session data.\n\n### Tests\n- Cover fresh allocation beside incompatible history, preservation and reuse boundaries, and default-thread deletion rejection through the command entry point without cleanup side effects."},{"version":"1.6.197","text":"### 修复取消回执、线程隔离和旧记录委派\n- 旧子任务记录缺少新版字段时可直接启动新委派,无需离线迁移;保留旧文件和会话,不复用异常旧任务,实际运行中的任务仍受冲突保护。\n- 委派启动失败时显示具体原因,便于定位问题。\n- 修复请求准备期间取消后没有回执的问题;单个线程的恢复记录损坏不再把其他线程已成功的请求报成失败。","changes":[{"topic":"delegation-runtime","title":"子任务委派","text":"旧子任务记录缺少新版字段时可直接启动新委派,无需离线迁移;保留旧文件和会话,不复用异常旧任务,实际运行中的任务仍受冲突保护。"},{"topic":"delegation-runtime","title":"子任务委派","text":"委派启动失败时显示具体原因,便于定位问题。"},{"topic":"thread-controls","title":"线程切换","text":"修复请求准备期间取消后没有回执的问题;单个线程的恢复记录损坏不再把其他线程已成功的请求报成失败。"}],"details":"### Fixed\n- Complete requests cancelled during admission exactly once, without waiting for attachment initialization or leaving a late attachment claim behind.\n- Isolate unreadable thread-generation metadata in thread listings and result summaries. Healthy threads keep working, while affected threads remain unavailable for execution and global backend changes.\n- Allow fresh delegation when historical dirty lanes lack newer shutdown fields. Keep native ownership and live-writer checks, preserve dirty metadata, files and sessions, and never reuse those lanes automatically. No offline migration is required.\n- Include the underlying ownership failure in managed-delegation errors.\n\n### Tests\n- Cover admission cancellation, sibling and default-thread recovery failures, unchanged historical records across restarts, and fresh-worker admission without relaxing native ownership checks."},{"version":"1.6.196","text":"### 旧子任务记录不再阻塞普通聊天\n- 修复升级后因旧子任务记录导致正常会话无法聊天、`/clear` 和 `/new` 后仍无法继续的问题,需升级本机 CLI。\n- 保留旧任务文件、成果和恢复记录;实际运行中的任务仍受冲突保护,子任务存储和成果处理继续检查所有权。","changes":[{"topic":"delegation-runtime","title":"子任务委派","text":"修复升级后因旧子任务记录导致正常会话无法聊天、`/clear` 和 `/new` 后仍无法继续的问题,需升级本机 CLI。"},{"topic":"delegation-runtime","title":"子任务委派","text":"保留旧任务文件、成果和恢复记录;实际运行中的任务仍受冲突保护,子任务存储和成果处理继续检查所有权。"}],"details":"### Fixed\n- Separate ordinary execution admission from historical managed-worker storage recovery. Legacy or unavailable metadata no longer blocks existing chats, unrelated threads, supported native commands, or compaction after `/clear` and `/new`.\n- Preserve live-worker conflict checks and strict ownership requirements for managed-worker storage, artifact integration, lane reuse, and cleanup. Preserve historical records and files without claiming uncertain workers have exited.\n\n### Tests\n- Cover conversation recovery with retained legacy metadata, sibling threads, delegation enabled and disabled, native commands, and active worker conflicts using isolated temporary homes."},{"version":"1.6.195","text":"### 子任务中断后可重新开始对话\n- 将清空会话与旧子任务收尾分开;`/clear` 和 `/new` 开始新的对话,旧任务的待处理成果不再拖住新请求,恢复文件与历史记录继续保留。\n- 中止主会话不再排在子任务收尾之后等待;旧任务迟到的结果不会干扰新请求,需升级本机 CLI。\n- 仍可能运行的任务继续接受停止和清理处理;与其冲突的代码执行仍受限制,不会把退出未确认的任务当作已安全结束。\n- 关闭 CLI 时,正在处理的请求会收到一次取消通知,迟到的完成结果不会再覆盖它。\n- 不支持的后端命令会正常提示原因,不再被旧子任务状态的报错掩盖;实际执行仍保留冲突检查。","changes":[{"topic":"delegation-runtime","title":"子任务委派","text":"将清空会话与旧子任务收尾分开;`/clear` 和 `/new` 开始新的对话,旧任务的待处理成果不再拖住新请求,恢复文件与历史记录继续保留。"},{"topic":"delegation-runtime","title":"子任务委派","text":"中止主会话不再排在子任务收尾之后等待;旧任务迟到的结果不会干扰新请求,需升级本机 CLI。"},{"topic":"delegation-runtime","title":"子任务委派","text":"仍可能运行的任务继续接受停止和清理处理;与其冲突的代码执行仍受限制,不会把退出未确认的任务当作已安全结束。"},{"topic":"delegation-runtime","title":"子任务委派","text":"关闭 CLI 时,正在处理的请求会收到一次取消通知,迟到的完成结果不会再覆盖它。"},{"topic":"delegation-runtime","title":"子任务委派","text":"不支持的后端命令会正常提示原因,不再被旧子任务状态的报错掩盖;实际执行仍保留冲突检查。"}],"details":"### Fixed\n- Separate managed-worker conversation recovery from process shutdown and artifact cleanup. `/clear` and `/new` detach historical worker context and closeout obligations while preserving recovery files, archives, ownership evidence, and unfinished cleanup.\n- Interrupt the coordinator independently of worker finalization, bound conversation-facing cancellation waits, and fence late output and completion against newer requests. Preserve direct-backend shutdown checks and restrictions on execution that conflicts with uncertain workers, including when delegation is disabled.\n- Keep recovery commands available without requiring healthy historical worker inventory. Upgrade the local CLI; native provider-resume behavior and the Router protocol are unchanged.\n\n- Restore one terminal cancellation response when the CLI shuts down an active request, while fencing late completions and retaining worker shutdown checks.\n- Return unsupported native-command errors before checking worker ownership; retain execution checks for supported native commands and compaction.\n\n### Tests\n- Cover interrupted worker cleanup, durable reset and restart, historical context separation, late callbacks, resource conflicts, failed persistence, and direct-executor shutdown safeguards with isolated fixtures.\n- Isolate backend and message-flow fixtures from real home directories and worker state; cover recovery, shutdown responses, and directory/session reset semantics in the full CLI suite."},{"version":"1.6.194","text":"### 修复含大文件仓库的子任务收尾\n- 修复仓库包含 Git LFS 文件时,子任务执行成功却在成果收尾时报错的问题;本地文件内容完整且可恢复时正常完成,需升级本机 CLI。\n- 文件缺失、内容不匹配或存储路径不安全时仍保留工作目录;不会自动下载大文件或清理此前失败的任务目录。","changes":[{"topic":"delegation-runtime","title":"子任务委派","text":"修复仓库包含 Git LFS 文件时,子任务执行成功却在成果收尾时报错的问题;本地文件内容完整且可恢复时正常完成,需升级本机 CLI。"},{"topic":"delegation-storage","title":"委派目录清理","text":"文件缺失、内容不匹配或存储路径不安全时仍保留工作目录;不会自动下载大文件或清理此前失败的任务目录。"}],"details":"### Fixed\n- Verify supported Git LFS pointers and local payloads during disposable worker finalization instead of rejecting every LFS-managed path. Preserve checkout recovery holds for missing or mismatched payloads, unsafe object storage and unsupported transformations; keep child-exit and artifact-disposition requirements unchanged.\n- Keep LFS verification local and leave historical failed worker records untouched. Upgrade the local CLI; Router protocol and native backend configuration are unchanged.\n\n### Tests\n- Exercise real local Git LFS payloads, unchanged and changed output, empty files, pointer-only checkouts, conservative reclamation, custom storage, corrupted or missing objects, unsafe paths, file replacement, and successful manager closeout. Keep the new fixture suite in the bounded real-Git process pool."},{"version":"1.6.193","text":"### 修复子任务传输超时后卡住\n- 修复嵌套 Git 仓库传输失败或超时后,子进程已退出但委派仍卡住的问题;仍确认两个子进程退出后才清理本次临时数据,不影响其他任务目录。需升级本机 CLI。","changes":[{"topic":"delegation-runtime","title":"子任务委派","text":"修复嵌套 Git 仓库传输失败或超时后,子进程已退出但委派仍卡住的问题;仍确认两个子进程退出后才清理本次临时数据,不影响其他任务目录。需升级本机 CLI。"}],"details":"### Fixed\n- Disconnect and drain failed nested Git transfer pipes before waiting for child closure. Preserve the original failure, SIGTERM/SIGKILL escalation, and the requirement that both children close before removing this transfer's quarantine; leave unrelated temporary directories intact.\n\n### Tests\n- Reproduce backpressure with real subprocesses, including a producer that exits before a receiver ignoring SIGTERM. Verify deadline rejection, forced receiver exit, both-close cleanup ordering, and isolation of another quarantine. Bound fixture cleanup waits with process and stream diagnostics."},{"version":"1.6.192","text":"### 恢复子任务委派\n- 使用系统级锁并记录子进程:空闲进程崩溃或本机重启后可自动恢复,仍在运行的子进程和无法确认的旧锁继续保护;恢复锁不会直接删除目录或会话。\n- 修复 1.6.191 发布包中无法列出后端或启动子任务的问题;需升级本机 CLI,单独升级 Router 不生效。\n- 正常停止服务或按 Ctrl+C 时,先等待子任务和会话退出再释放存储锁,避免重启后因旧锁阻塞聊天;无法确认退出时继续保留恢复状态。","changes":[{"topic":"delegation-runtime","title":"子任务委派","text":"使用系统级锁并记录子进程:空闲进程崩溃或本机重启后可自动恢复,仍在运行的子进程和无法确认的旧锁继续保护;恢复锁不会直接删除目录或会话。"},{"topic":"delegation-runtime","title":"子任务委派","text":"修复 1.6.191 发布包中无法列出后端或启动子任务的问题;需升级本机 CLI,单独升级 Router 不生效。"},{"topic":"delegation-runtime","title":"子任务委派","text":"正常停止服务或按 Ctrl+C 时,先等待子任务和会话退出再释放存储锁,避免重启后因旧锁阻塞聊天;无法确认退出时继续保留恢复状态。"}],"details":"### Fixed\n- Replace existence-only delegation exclusion with persistent native kernel gates for storage and shared repositories. Record hashed host, boot, PID namespace and owner process identity, and durably journal managed backend and Git child launches before spawn. Recover dead idle owners and same-host rebooted owners without unlink races or PID-age heuristics; retain live or uncertain child groups and legacy ownership metadata. Keep normal execution outside ownership scopes unchanged and preserve disposal checks independently of lock recovery.\n- Restore delegation backend discovery and task admission in the published CommonJS runtime by avoiding a local name collision with module exports. Preserve required artifact-export validation and task closeout behavior.\n- Handle SIGTERM and SIGINT through a shared asynchronous shutdown path registered before worker inventory initialization. Await client, executor, and delegation teardown before exiting; release storage ownership only after verified cleanup. Clean up partial startup failures, preserve uncertain-exit recovery state, and share teardown with automatic updates.\n- Canonicalize worker-context reset test roots, isolate their home directories, and cover temporary-directory aliases without weakening runtime path checks. Surface reset initialization failures directly rather than leaving a test waiting for a callback that cannot run.\n\n### Tests\n- Exercise real process contention, SIGKILL and concurrent recovery, surviving child groups, interrupted metadata publication, legacy locks, PID reuse, reboot/namespace identity, durable launch failures and ordinary spawn compatibility. Native Linux execution does not establish native macOS/Windows acceptance.\n- Compile the CLI with its shipping TypeScript configuration and run backend discovery, export validation, and a complete synthetic delegated task in a separate Node process. Cover worker reset and reuse through a filesystem alias while retaining rejection of noncanonical storage paths."},{"version":"1.6.191","text":"### 子任务结束后自动释放临时目录\n- Linux 上的新委派任务确认进程组退出并完成成果处理后自动清理临时工作目录和依赖;失败任务保存可恢复代码后也能清理,已有成果和原生会话保留。\n- 重启后继续发现待处理成果和未完成清理;无法确认进程退出或内容安全时明确保留原因。\n- 增加本地存量目录检查和显式离线清理流程,离线删除目前仅支持 Linux;升级不会直接删除旧目录,需要升级本机 CLI。","changes":[{"topic":"delegation-storage","title":"委派目录清理","text":"Linux 上的新委派任务确认进程组退出并完成成果处理后自动清理临时工作目录和依赖;失败任务保存可恢复代码后也能清理,已有成果和原生会话保留。"},{"topic":"delegation-storage","title":"委派目录清理","text":"重启后继续发现待处理成果和未完成清理;无法确认进程退出或内容安全时明确保留原因。"},{"topic":"delegation-storage","title":"委派目录清理","text":"增加本地存量目录检查和显式离线清理流程,离线删除目前仅支持 Linux;升级不会直接删除旧目录,需要升级本机 CLI。"}],"details":"### Changed\n- Treat new Linux managed Git worktrees as disposable execution storage after confirmed managed process-group exit and durable artifact closeout. Reclaim delivered and retained output, including recoverable failed tasks and temporary dependencies, while preserving native conversations and Git artifact references.\n- Coordinate storage ownership and shared repository operations, resume eligible cleanup, and rediscover pending artifacts independently of expiring task diagnostics. Preserve explicit recovery holds for uncertain exit, unsafe identity, uncaptured content and unresolved parent application.\n- Add explicit offline delegation storage inventory and historical disposal with frozen identity checks, including receipt-backed integration scratch. Preserve lane/native recovery metadata when reclamation fails, and fence shutdown admission while allowing teardown retries. Bind completed offline discard to its original obligation and keep bounded inventory diagnostics separate from task closeout. Keep macOS/Windows on conservative checkout policy. Existing worktrees are never swept or silently opted into disposal on reuse after upgrade; Router protocol and native backend settings are unchanged.\n\n### Tests\n- Cover disposable success/failure closeout, pending delivery after restart, failed/retained recreation, ownership exclusion and scoped historical cleanup with isolated filesystem/Git fixtures. Require kernel-confirmed group absence across fork races and preserve group obligations during missing-session retries; retain imported disposable receipts on unsupported platforms."},{"version":"1.6.190","text":"### 工具授权结果正确传达给后端\n- 修复 Kimi 和 OpenCode 无法正确识别工具批准、拒绝或取消结果的问题;需升级本机 CLI,单独升级 Router 不生效。\n- 保留原有授权设置和对话:自动批准关闭时仍需确认,模型提出的问题仍等待回答,不会自动启用“从不询问”模式。","changes":[{"topic":"acp-approval","title":"工具授权","text":"修复 Kimi 和 OpenCode 无法正确识别工具批准、拒绝或取消结果的问题;需升级本机 CLI,单独升级 Router 不生效。"},{"topic":"acp-approval","title":"工具授权","text":"保留原有授权设置和对话:自动批准关闭时仍需确认,模型提出的问题仍等待回答,不会自动启用“从不询问”模式。"}],"details":"### Fixed\n- Serialize shared Kimi and OpenCode permission decisions with the nested ACP v1 outcome for approvals, rejections, cancellations, and error paths. Preserve fail-closed validation, manual approval settings, interactive questions, and existing backend session bindings; native permission modes and the Router protocol are unchanged.\n\n### Tests\n- Exercise real Kimi/OpenCode executors and ACP NDJSON transport against a schema-validating synthetic agent, covering automatic approval, manual allow-once/allow-always, denial/cancellation, and interactive question selection/skip. Retain DSH interoperability checks and malformed-selection regression coverage."},{"version":"1.6.189","text":"### 重启后记住每台设备的线程\n- Router 现在按用户和设备保存所选线程,重启或在设备间来回切换都能恢复;旧版 CLI 也可使用,不会重置原有对话。\n- 已失效的卡片回复会明确报错,不会误发到默认线程;确认线程已删除后会通知并恢复默认,失败消息不会自动重发。偏好记录损坏时,可用 `/thread list` 获取新的线程选择按钮。\n- 修复续卡上的线程按钮和回复无法使用的问题;新建线程只有在完整清单确认后才会被选中,异常清单不会覆盖原选择。","changes":[{"topic":"thread-selection","title":"线程选择","text":"Router 现在按用户和设备保存所选线程,重启或在设备间来回切换都能恢复;旧版 CLI 也可使用,不会重置原有对话。"},{"topic":"thread-selection","title":"线程选择","text":"已失效的卡片回复会明确报错,不会误发到默认线程;确认线程已删除后会通知并恢复默认,失败消息不会自动重发。偏好记录损坏时,可用 `/thread list` 获取新的线程选择按钮。"},{"topic":"thread-selection","title":"线程选择","text":"修复续卡上的线程按钮和回复无法使用的问题;新建线程只有在完整清单确认后才会被选中,异常清单不会覆盖原选择。"}],"details":"### Fixed\n- Persist each Feishu user's selected thread per bound device with prompt FIFO durable writes, so Router restarts and A→B→A device switches restore selection without changing native sessions or the protocol-v1 CLI contract. Keep known replies independent, reject expired parent routes and stale card controls, and fence selection intents against late New Thread responses and ownership changes. Bind thread controls on actual delivered continuation cards and require a validated complete catalog before adopting a New Thread selection.\n- Reset a deleted selection only after a fresh authoritative catalog or an exactly correlated legacy missing-thread response; notify the user and never replay the failed message. Quarantine malformed optional preferences without disabling valid bindings or silently overwriting raw data, and preserve the previous selection when persistence fails. A narrow `/thread list` recovery path uses the existing legacy status response to refresh selection controls without executing a prompt.\n\n### Tests\n- Cover real Router/store reconstruction with legacy registration, per-user/device isolation and A→B→A restoration, `/clear` and reconnects, unbind/rebind, FIFO preference commits, stale intents and catalogs, card provenance, exact deletion handling without replay, durable uncertainty, malformed preferences, actual continuation finalization and replies, and New Thread creation versus selection persistence failures."},{"version":"1.6.188","text":"### 解绑设备不再留下归属异常\n- 修复解绑保存失败时设备仍显示已绑定却无法连接的问题;现在解绑记录与设备归属一起更新,失败时保持原状。","changes":[{"topic":"binding-storage","title":"设备绑定","text":"修复解绑保存失败时设备仍显示已绑定却无法连接的问题;现在解绑记录与设备归属一起更新,失败时保持原状。"}],"details":"### Fixed\n- Apply each device unbind in one durable snapshot, covering the user record, reverse ownership mapping, active-device fallback, and last-device deletion. A failed replacement now preserves both ownership representations instead of leaving a listed device without its mapping.\n\n### Tests\n- Cover active, inactive, and last-device unbinds, pre-replacement failure coherence in memory and after reload, and queued storage mutations that must not resurrect removed ownership."},{"version":"1.6.187","text":"### 绑定文件异常时保留原始数据\n- 修复绑定文件结构异常时可能被重置为空的问题:现在保留原文件并明确报错,修正或恢复文件后再启动 Router;合法旧格式和旧版 CLI 继续兼容。","changes":[{"topic":"binding-storage","title":"设备绑定","text":"修复绑定文件结构异常时可能被重置为空的问题:现在保留原文件并明确报错,修正或恢复文件后再启动 Router;合法旧格式和旧版 CLI 继续兼容。"}],"details":"### Fixed\n- Validate binding-file structure and supported versions before adopting data, migrating legacy records, or removing expired codes. Preserve malformed files without replacement and block reads and writes on the rejected instance instead of silently publishing empty bindings.\n- Retain valid version-1 records and versionless single-device migrations, including empty legacy stores and opaque dictionary keys. Keep parser input out of reported errors and preserve protocol-v1 CLI compatibility.\n\n### Tests\n- Cover malformed roots, collections, nested records, timestamps and versions, byte-preserving failure, blocked post-failure access, valid legacy/current reloads, private parser diagnostics, and recovery through a fresh instance after repair."},{"version":"1.6.186","text":"### Pi 长任务不再中途失败\n- 修复 Pi 后端在任务进行到 10 分钟时被强制中断:只要连续 10 分钟内不断有事件(输出、工具执行、扩展 UI 的提示与回复都算),任务就会继续;单个工具长时间没有任何事件时仍会按超时结束。等待用户回答扩展 UI 问题期间不计入无活动超时(调用方设置的硬上限仍生效),但需要回复或 /abort 才会继续。\n- 超时和 `/abort` 不再显示成 “Request aborted”,而是给出明确的原因说明。","changes":[{"topic":"pi-turn-timeout","title":"Pi 长任务","text":"修复 Pi 后端在任务进行到 10 分钟时被强制中断:只要连续 10 分钟内不断有事件(输出、工具执行、扩展 UI 的提示与回复都算),任务就会继续;单个工具长时间没有任何事件时仍会按超时结束。等待用户回答扩展 UI 问题期间不计入无活动超时(调用方设置的硬上限仍生效),但需要回复或 /abort 才会继续。"},{"topic":"pi-turn-timeout","title":"Pi 长任务","text":"超时和 `/abort` 不再显示成 “Request aborted”,而是给出明确的原因说明。"}],"details":"### Fixed\n- Make the Pi inactivity watchdog the `ExecuteOptions.inactivityTimeout` window (10 minutes by default), re-armed by every Pi event so a long tool chain no longer fails exactly 10 minutes after the prompt. An extension-UI prompt suspends the watchdog until the user answers while a positive hard limit stays armed, and a dialog that Pi resolves on its own timer re-arms the watchdog. A positive `ExecuteOptions.timeout` is a one-shot hard limit and a non-finite one arms nothing, while `inactivityTimeout: 0` / `timeout: 0` each disable only their own deadline, matching the Agy and Codex executors.\n- Claim remote-cli's own failure reason before Pi settles its aborted turn, so a deadline or an explicit `/abort` no longer surfaces Pi's raw `Request aborted`. A turn already failing is never failed twice, overlapping deadline and `/abort` paths send a single `abort`, `/abort` waits for the in-flight cleanup instead of releasing the turn early, and cleanup of a settled turn no longer aborts, recycles, or cancels the input dialog of a turn started afterwards.\n\n### Tests\n- Cover the deadline-versus-abort ordering, continuous tool activity that outlasts the watchdog window, the hard limit that events cannot extend, a single abort while the failure is in flight, a waiting input dialog that suspends the watchdog without cancelling the hard limit, a dialog that Pi resolves itself, a dialog still open when the turn settles, concurrent `/abort` cleanup, an `/abort` still clearing the queue when a successor starts, the cleared watchdog after a settled turn, the disabled, non-finite and default deadlines, and cleanup ownership after settlement."},{"version":"1.6.185","text":"### 修复消息归属、设备绑定与执行异常\n- 加强任务结果与通知的用户归属校验,继续支持旧版 CLI 的正常连接和结果回传。\n- 修复并发绑定和保存顺序问题,避免设备重复绑定或解绑后状态恢复;保存失败时明确报错。\n- 修复权限确认异常时可能自动放行工具的问题,此项需要升级 CLI 生效。\n- 修复 Codex 启动异常后任务状态过早释放的问题;停止失败可用 `/abort` 重试,确认停止后再接新任务,此项需要升级 CLI 生效。","changes":[{"topic":"router-security","title":"Router 安全","text":"加强任务结果与通知的用户归属校验,继续支持旧版 CLI 的正常连接和结果回传。"},{"topic":"binding-storage","title":"设备绑定","text":"修复并发绑定和保存顺序问题,避免设备重复绑定或解绑后状态恢复;保存失败时明确报错。"},{"topic":"cli-permissions","title":"权限确认","text":"修复权限确认异常时可能自动放行工具的问题,此项需要升级 CLI 生效。"},{"topic":"codex-runtime","title":"Codex 执行","text":"修复 Codex 启动异常后任务状态过早释放的问题;停止失败可用 `/abort` 重试,确认停止后再接新任务,此项需要升级 CLI 生效。"}],"details":"### Fixed\n- Validate Router task-output recipients against current device ownership while retaining protocol-v1 registration, legacy response shapes, background notifications, and owner-validated result recovery.\n- Serialize competing device binding operations and binding-code consumption to prevent one device from being assigned to different users concurrently.\n- Publish binding changes only after serialized atomic persistence succeeds; reject failed drafts, block uncertain replacements, preserve damaged input, and drain accepted writes early during shutdown while propagating failures after resource cleanup.\n- Cancel ACP permission requests when the approval callback fails or returns an invalid selection instead of selecting the first option.\n- Keep Codex execution fenced after an ambiguous turn-start failure until transport termination is confirmed, without automatically replaying uncertain work; allow an explicit `/abort` retry to recover after an unconfirmed stop.\n\n### Tests\n- Add regressions for recipient ownership, bound legacy clients, binding and storage races, failed approvals, and ambiguous native-turn cleanup."},{"version":"1.6.184","text":"### 修复 Docker 重建后的启动失败\n- 修复容器重建后因残留 PID 文件反复提示服务已运行的问题,保留真正重复启动的检查。\n- 完善启动失败和停止时的清理,避免停止请求后继续启动服务,并保护后续实例的运行记录。","changes":[{"topic":"router-lifecycle","title":"Router 启停","text":"修复容器重建后因残留 PID 文件反复提示服务已运行的问题,保留真正重复启动的检查。"},{"topic":"router-lifecycle","title":"Router 启停","text":"完善启动失败和停止时的清理,避免停止请求后继续启动服务,并保护后续实例的运行记录。"}],"details":"### Fixed\n- Recover from a persisted Router PID equal to the new startup process, including Docker PID 1 after container recreation, while retaining ordinary stop/status process checks and rejecting another live PID.\n- Register shutdown handling before asynchronous startup and use bounded cleanup for initialization failures and termination. Preserve replacement PID records and prevent interrupted initialization from continuing into a new server start.\n\n### Tests\n- Cover self-PID recovery, duplicate-process refusal, initialization failures, early signals, bounded shutdown, and ownership-safe cleanup with isolated fixtures."},{"version":"1.6.183","text":"### 两个 Codex 提醒彩蛋\n- 新增周额度状态和重置卡张数增加提醒的彩蛋图解,小贴士共 27 条;明确卡片只是检测快照,不会自动发放、领取或消耗重置卡。","changes":[{"topic":"tips","title":"使用技巧","text":"新增周额度状态和重置卡张数增加提醒的彩蛋图解,小贴士共 27 条;明确卡片只是检测快照,不会自动发放、领取或消耗重置卡。"}],"details":"### Added\n- Add two Easter-egg Tips explaining the passive Codex weekly-quota and banked-reset-credit increase notices, including their sampling limits and the distinction from resetting context or granting, claiming, or consuming credits.\n- Expand the bundled catalog, native-card-based SVG/PNG illustrations, preview gallery, contact sheet, and download archive to 27 tutorials while preserving existing content and progress.\n\n### Tests\n- Cover passive notification copy and artwork, complete packaging, and preserved reading progress and opt-outs when upgrading from the 25-tip catalog."},{"version":"1.6.182","text":"### 新增八个工具操作图解\n- 小贴士扩充至 25 条,新增目录选择、独立线程、工具详情、委派开关和会话清理、Codex 速度与目标、命令沙箱的操作说明和配图。\n- 原有阅读记录继续保留,图册与下载包同步补齐全部新图。","changes":[{"topic":"tips","title":"使用技巧","text":"小贴士扩充至 25 条,新增目录选择、独立线程、工具详情、委派开关和会话清理、Codex 速度与目标、命令沙箱的操作说明和配图。"},{"topic":"tips","title":"使用技巧","text":"原有阅读记录继续保留,图册与下载包同步补齐全部新图。"}],"details":"### Added\n- Add eight illustrated tool-operation Tips for directory selection, named project threads, tool details, delegation controls and targeted worker resets, Codex speed and native goals, and backend-specific command sandboxing. Preserve the existing 17 topic IDs and reading progress.\n- Expand the bundled catalog and editable SVG/PNG gallery to 25 tutorials, with a complete dynamically sized contact sheet and downloadable bundle.\n\n### Tests\n- Cover the expanded catalog, operation-specific prerequisites and illustrations, complete gallery coverage, and byte-identical packaged assets."},{"version":"1.6.181","text":"### 小贴士直接显示示例\n- 移除“看个例子”按钮,可复制的示例直接显示在使用方式下方,卡片仅保留下一条、我学会了和推送设置。","changes":[{"topic":"tips","title":"使用技巧","text":"移除“看个例子”按钮,可复制的示例直接显示在使用方式下方,卡片仅保留下一条、我学会了和推送设置。"}],"details":"### Changed\n- Remove the separate example button from illustrated Tips. Show copyable example instructions directly below usage, alongside the illustration and inline usage notes, with only Next, Mastered, and Settings controls.\n- Refresh previously delivered example and detail controls into the current card after normal ownership and expiry checks.\n\n### Tests\n- Cover inline examples, the three passive controls, and safe handling of both legacy callbacks without changing progress or preferences."},{"version":"1.6.180","text":"### 小贴士直接显示使用提示\n- 移除“展开讲讲”按钮,必要的使用限制直接显示在正文中,保留示例、下一条、已掌握和推送设置。","changes":[{"topic":"tips","title":"使用技巧","text":"移除“展开讲讲”按钮,必要的使用限制直接显示在正文中,保留示例、下一条、已掌握和推送设置。"}],"details":"### Changed\n- Remove the extra detail button from illustrated Tips and show concise usage notes directly in the card body. Keep examples, next-tip navigation, progress marking, and subscription settings available.\n- Refresh previously delivered detail controls into the simplified card after normal ownership and expiry validation.\n\n### Tests\n- Verify inline notes, the four remaining controls, example rendering, and safe handling of legacy detail callbacks."},{"version":"1.6.179","text":"### 默认每天收到一个小技巧\n- 小贴士默认每天推送一条,无需手动开启;可随时暂停、停止推送,或改为每周二、四。\n- 已主动停止推送的账号保持关闭,已有静音期限和阅读进度继续保留。","changes":[{"topic":"tips","title":"使用技巧","text":"小贴士默认每天推送一条,无需手动开启;可随时暂停、停止推送,或改为每周二、四。"},{"topic":"tips","title":"使用技巧","text":"已主动停止推送的账号保持关闭,已有静音期限和阅读进度继续保留。"}],"details":"### Changed\n- Enable daily illustrated Tips by default for new users and legacy default-off records, without requiring manual subscription. Preserve explicit opt-outs, mute deadlines, chosen frequencies, reading progress, and delivery timing protections.\n- Update Tips settings and documentation to explain the default cadence and pause or stop controls.\n\n### Tests\n- Cover automatic delivery without enrollment, legacy preference migration, and preservation of explicit stops, pauses, progress, and restart behavior."},{"version":"1.6.178","text":"### 每次学会一个实用技巧\n- 新增 17 个中文图解小技巧,按实际面板和任务卡重绘配图,并提供 SVG 源图与可复制示例,发送 `/tips` 即可浏览。\n- 可主动订阅每日或每周两次推送,支持按天静音、恢复和关闭;按用户去重,避开近期操作及 Router 可观察到的任务时段,默认不自动推送。","changes":[{"topic":"tips","title":"使用技巧","text":"新增 17 个中文图解小技巧,按实际面板和任务卡重绘配图,并提供 SVG 源图与可复制示例,发送 `/tips` 即可浏览。"},{"topic":"tips","title":"使用技巧","text":"可主动订阅每日或每周两次推送,支持按天静音、恢复和关闭;按用户去重,避开近期操作及 Router 可观察到的任务时段,默认不自动推送。"}],"details":"### Added\n- Bundle 17 illustrated Chinese scenario tips with deterministic manual browsing and passive Feishu cards. Each tip includes a distinct packaged PNG redrawn from the real settings or task-card UI, an editable SVG, and a copyable example that is never executed by a card action. All examples use synthetic content.\n- Add Router-owned explicit daily or twice-weekly subscriptions, timezone settings, permanent opt-out, and timed mute controls. Deduplicate per user across devices; skip recent activity, observed tasks, offline users, and exhausted catalogs.\n- Persist private preferences and pre-dispatch delivery intent. Suppress ambiguous sends after failures or restarts, validate card ownership and expiry, and stop scheduling before Router shutdown.\n\n### Tests\n- Cover content and packaging, subscription and delivery state transitions, failure recovery, action validation, transport isolation, and Router integration with mocked Feishu APIs."},{"version":"1.6.177","text":"### 清空对话同时重置子 Agent\n- `/clear` 和 `/new` 同时重置当前线程在各后端的主会话及全部委派 Worker 会话,避免旧上下文在后续委派或切回后端时重新带入。\n- 保留项目文件、工作产物、历史存档和配置;清理失败或中断会明确提示并阻止继续使用旧会话,可修复后重试,其他线程不受影响。\n- 服务重启前等待未完成的清理并确认后端退出,失败时明确报告,避免把未完成的关闭当作成功。","changes":[{"topic":"delegation","title":"委派任务","text":"`/clear` 和 `/new` 同时重置当前线程在各后端的主会话及全部委派 Worker 会话,避免旧上下文在后续委派或切回后端时重新带入。"},{"topic":"delegation","title":"委派任务","text":"保留项目文件、工作产物、历史存档和配置;清理失败或中断会明确提示并阻止继续使用旧会话,可修复后重试,其他线程不受影响。"},{"topic":"delegation","title":"委派任务","text":"服务重启前等待未完成的清理并确认后端退出,失败时明确报告,避免把未完成的关闭当作成功。"}],"details":"### Changed\n- Make `/clear` and `/new` reset every direct backend session binding and managed worker continuation owned by the current thread, including inactive backends and parallel worker lanes. Preserve files, artifacts, archived transcripts, settings, and other threads.\n- Persist reset intent before clearing native pointers. After intent is saved, failed or interrupted resets remain retryable and prevent old context from resuming, including after CLI restarts; running, queued, and uncertain worker activity refuses an unsafe reset.\n- Reject incomplete worker inventories and unconfirmed native exits. Bound shutdown waits while preserving reset intent and process ownership for safe retries.\n- Join retained reset cleanup during service shutdown, preserve conversation data and reset intent, and propagate shutdown failures before automatic restart.\n- Keep single-worker card clearing and explicit `/delegation reset [backend]` available with their existing scopes. This CLI change uses the existing Router protocol.\n\n### Tests\n- Add regressions for both aliases, all-backend and multiple-worker isolation, reset failure/retry/restart handling, admission guards, and preservation of artifacts and settings. Verify that Pi workers start with a fresh native identity after pointer-only clearing while their archived transcripts remain available."},{"version":"1.6.176","text":"### 在模型设置中选择 Codex 速度\n- 支持原生速度选项的 Codex 模型可在模型卡片中单独选择速度,也可明确选择标准速度或跟随原生配置。\n- 速度按线程和后端保存,后续任务及委派工作使用对应设置;未选择速度的线程和其他后端保持原有行为。\n- 已选速度不再可用时仍可恢复原生配置;降级 Codex 后,旧会话可能需要升级或清空后才能安全继续。","changes":[{"topic":"model-speed","title":"模型速度","text":"支持原生速度选项的 Codex 模型可在模型卡片中单独选择速度,也可明确选择标准速度或跟随原生配置。"},{"topic":"model-speed","title":"模型速度","text":"速度按线程和后端保存,后续任务及委派工作使用对应设置;未选择速度的线程和其他后端保持原有行为。"},{"topic":"model-speed","title":"模型速度","text":"已选速度不再可用时仍可恢复原生配置;降级 Codex 后,旧会话可能需要升级或清空后才能安全继续。"}],"details":"### Added\n- Add a separate Speed section to model settings when the selected Codex model exposes native service tiers. Preserve native tier names and descriptions, with explicit Standard and Follow native config choices.\n- Persist speed independently per thread and backend, including future delegated workers, and apply sticky speed policy before activating native goals.\n- Negotiate model speed settings independently so older peers and backends without native speed controls retain their existing model behavior.\n\n### Safety\n- Validate speed against the selected model, reject incompatible model changes, and restore native configured speed explicitly instead of retaining a previous sticky override. Untouched threads send no new speed parameters or settings requests.\n- Keep speed reset available after tier removal. Require an upgrade or explicit conversation reset when a downgraded Codex protocol cannot safely clear a saved tier."},{"version":"1.6.175","text":"### 自动刷新 Kimi 模型列表\n- 查看或刷新 Kimi 模型列表时自动更新原生模型目录,无需先去电脑终端手动刷新或重新登录。\n- 刷新失败或超时会明确提示,可稍后重试;实际可用模型仍以 Kimi 账号返回的目录和权限为准。","changes":[{"topic":"kimi-models","title":"Kimi 模型","text":"查看或刷新 Kimi 模型列表时自动更新原生模型目录,无需先去电脑终端手动刷新或重新登录。"},{"topic":"kimi-models","title":"Kimi 模型","text":"刷新失败或超时会明确提示,可稍后重试;实际可用模型仍以 Kimi 账号返回的目录和权限为准。"}],"details":"### Fixed\n- Refresh Kimi Code's native managed model catalog automatically when listing models, so newly available models can appear without opening the native terminal or signing in again.\n- Bound refresh requests and local server cleanup, coalesce concurrent refreshes, and report discovery failures instead of silently presenting stale metadata as refreshed.\n- Reload an idle Kimi ACP process before applying discovered aliases while preserving its conversation binding, including choices discovered by temporary settings previews.\n\n### Tests\n- Cover native refresh ordering, new model discovery, failure and timeout handling, concurrent requests, and preservation of ordinary backend execution."},{"version":"1.6.174","text":"### 直接显示线程切换按钮\n- 恢复直接显示线程按钮和新建按钮,切换线程不再需要先点击展开。\n- 卡片元素上限从 150 提高到 180,减少因元素数量触发的拆卡,同时保留正文和完成信息的容量保护。","changes":[{"topic":"thread-controls","title":"线程切换","text":"恢复直接显示线程按钮和新建按钮,切换线程不再需要先点击展开。"},{"topic":"thread-controls","title":"线程切换","text":"卡片元素上限从 150 提高到 180,减少因元素数量触发的拆卡,同时保留正文和完成信息的容量保护。"}],"details":"### Changed\n- Restore directly visible thread-switch buttons and the new-thread button on completed cards, removing the thread folding panel while preserving reply attribution and routing behavior.\n- Increase the recursive card element budget from 150 to 180 tagged nodes, retaining completion reserves and the existing size and table limits.\n\n### Tests\n- Cover visible thread controls through finalization and refresh, switching callbacks, and recursive pagination boundaries at the new limit."},{"version":"1.6.173","text":"### 生成图片直接显示在回复中\n- Codex 返回受支持的原生或工具图片时会自动显示到卡片,无需再要求模型补写 Markdown 图片链接。\n- 修复回复结束时图片尚未上传完成而漏显的问题,同一回复中的相同图片只展示一次。\n- 图片读取和上传设有数量、大小与等待限制;异常时提示省略原因,正常文字回复仍可完成。完整改进需要同时升级 CLI 和 Router。","changes":[{"topic":"image-output","title":"图片输出","text":"Codex 返回受支持的原生或工具图片时会自动显示到卡片,无需再要求模型补写 Markdown 图片链接。"},{"topic":"image-output","title":"图片输出","text":"修复回复结束时图片尚未上传完成而漏显的问题,同一回复中的相同图片只展示一次。"},{"topic":"image-output","title":"图片输出","text":"图片读取和上传设有数量、大小与等待限制;异常时提示省略原因,正常文字回复仍可完成。完整改进需要同时升级 CLI 和 Router。"}],"details":"### Fixed\n- Forward recognized Codex native, MCP, and dynamic-tool image results directly to response cards without requiring Markdown. Prefer inline bytes and allow explicit native saved paths only through the local directory policy; omit image bytes from tool diagnostics.\n- Drain admitted image uploads before Router response finalization, including ordinary replies. Bound image work and fence late results after timeout, cancellation, disconnect, or stream replacement.\n- Deduplicate images by decoded content within a reply, retain changed content at the same path, and harden local reads with canonical-path checks, regular-file verification, bounded reads, and format validation. Keep image failures separate from task success.\n\n### Tests\n- Cover structured image variants, inline/file/Markdown deduplication, read and upload limits, finalization ordering, late results, filesystem boundaries, and unchanged text and goal behavior."},{"version":"1.6.172","text":"### 在 Codex 线程中持续推进目标\n- 支持 /goal 创建和查看原生目标,使用 pause、resume、clear 暂停、恢复或清除,并可通过 --budget 显式设置 token 预算。\n- 连续执行期间保留输出和审批入口;首版启动目标前需关闭当前线程的 managed delegation 并清空队列,进程恢复后需显式继续目标。","changes":[{"topic":"codex-goal","title":"Codex 目标","text":"支持 /goal 创建和查看原生目标,使用 pause、resume、clear 暂停、恢复或清除,并可通过 --budget 显式设置 token 预算。"},{"topic":"codex-goal","title":"Codex 目标","text":"连续执行期间保留输出和审批入口;首版启动目标前需关闭当前线程的 managed delegation 并清空队列,进程恢复后需显式继续目标。"}],"details":"### Added\n- Support Codex native `/goal`, `/goal <objective>`, `/goal pause`, `/goal resume`, and `/goal clear`, with optional explicit token budgets on activation or resume. Goal state and continuation remain owned by Codex's thread-goal APIs, without prompt-based continuation loops.\n- Keep goal output, approvals, activity, and thread admission attached across native continuation turns. Status and stop controls remain available during execution; unsupported backends fail without forwarding goal text to a model.\n\n### Changed\n- Initially require managed delegation disabled and an empty queue before activating a goal. Preserve native goal state on process loss and require explicit recovery; avoid accidentally resuming goals through status queries. Threads that never use native goals retain their existing execution path.\n\n### Tests\n- Cover command parsing, explicit budgets, native lifecycle transitions, multi-turn output ownership, stop and recovery behavior, unsupported versions, queue/settings exclusion, and unchanged ordinary execution."},{"version":"1.6.171","text":"### 稳定展开线程列表\n- 线程按钮改用飞书原生折叠面板,点击标题即可展开或收起,避免旧交互更新方式导致展开后立即复原;回复所属线程信息保持可见。","changes":[{"topic":"thread-controls","title":"线程切换","text":"线程按钮改用飞书原生折叠面板,点击标题即可展开或收起,避免旧交互更新方式导致展开后立即复原;回复所属线程信息保持可见。"}],"details":"### Fixed\n- Use the native Feishu Card 2.0 collapsible panel for completed-card thread controls. Expanding or collapsing the list requires no application callback or message PATCH, avoiding the previous PATCH-before-callback-response path that could immediately revert the expansion.\n- Keep thread selection and New controls inside the panel, with reply-source information outside it. Hidden controls remain included in recursive card budgets; existing backend execution, thread routing, and protocol behavior are preserved.\n\n### Tests\n- Cover native panel payloads, generated non-default thread selections, reply-source preservation, recursive budgets, and existing card fallback and Worker controls."},{"version":"1.6.170","text":"### 回滚线程卡片改动\n- 撤销今日的线程卡片折叠改动,恢复 1.6.168 的线程按钮显示和卡片拆分行为。","changes":[{"topic":"thread-controls","title":"线程切换","text":"撤销今日的线程卡片折叠改动,恢复 1.6.168 的线程按钮显示和卡片拆分行为。"}],"details":"### Reverted\n- Revert the 1.6.169 thread-card presentation change, restoring the always-visible thread controls and 150-node recursive card budget from 1.6.168."},{"version":"1.6.168","text":"### 用卡片浏览和切换目录\n- 输入 /cd 即可在卡片中浏览上一级、下一级和允许的根目录,只显示目录;点击“使用此目录”才切换当前线程,浏览本身不会清空会话。\n- 切换前检查目录权限和任务状态,拒绝过期或已变化的选择;大目录会明确提示列表限制,原有 /cd 路径命令仍可使用。","changes":[{"topic":"directory-browser","title":"目录浏览","text":"输入 /cd 即可在卡片中浏览上一级、下一级和允许的根目录,只显示目录;点击“使用此目录”才切换当前线程,浏览本身不会清空会话。"},{"topic":"directory-browser","title":"目录浏览","text":"切换前检查目录权限和任务状态,拒绝过期或已变化的选择;大目录会明确提示列表限制,原有 /cd 路径命令仍可使用。"}],"details":"### Added\n- Open bare `/cd` as a directory-only browser when both peers negotiate `directoryCards` and `settingsCards`. Navigate child/parent/root directories without executing a backend; apply only with Use this directory and preserve text `/cd <path>` for all peers.\n- Bind bounded local listings to owner, thread/configuration, allowlist, expiry, canonical roots, directory and ancestor identities. Omit symbolic-link directories, stop at the nearest allowed root, explicitly report partial listings, and reuse budgeted card rendering and exact-request receipts.\n\n### Changed\n- Serialize card and text directory changes through shared settings admission, reject active/queued/delegated work, and preserve existing all-backend context reset, same-directory no-op, and delegation workspace-generation cleanup. External filesystem races and bind mounts remain outside the application-level isolation guarantee.\n\n### Tests\n- Cover directory-only browsing, roots, busy navigation, changed identities/ancestors, symlinks, stale/forged/expired selections, duplicate Apply, text compatibility, card budgets, and optional capability negotiation."},{"version":"1.6.167","text":"### 子任务结果展示更完整\n- 子任务完成卡片的结果摘要上限提高至 4 KiB,减少过早截断,保留长结果的开头和结论。\n- 带省略标记的结果片段改用安全纯文本展示,避免截断代码块、表格或链接导致排版错乱;完整结果仍保留 Markdown 格式。","changes":[{"topic":"delegation","title":"委派任务","text":"子任务完成卡片的结果摘要上限提高至 4 KiB,减少过早截断,保留长结果的开头和结论。"},{"topic":"delegation","title":"委派任务","text":"带省略标记的结果片段改用安全纯文本展示,避免截断代码块、表格或链接导致排版错乱;完整结果仍保留 Markdown 格式。"}],"details":"### Fixed\n- Expand terminal Worker card summaries from 1000 bytes to 4 KiB for Router 1.6.167 or newer, retain UTF-8-safe beginning/end excerpts, and accept the full summary through Router validation and rendering. Older or unknown Routers retain the legacy budget; strict version precedence excludes 1.6.167 prereleases, and current registration metadata is rechecked after reconnect. Full delegated results and continuations retain their existing 32 KiB and 64 KiB limits.\n- Render worker result excerpts containing standalone omission markers as escaped literal text with a separate explanation, preventing head/tail splices from reinterpreting orphaned Markdown fences, links, tables, or card markup. Intact result Markdown and streaming activity formatting remain unchanged.\n\n### Tests\n- Cover larger ASCII/Unicode summaries, retained conclusions, legacy omission markers, Markdown and card-tag safety, Router boundary validation, and atomic Worker pagination under node, size, and table budgets."},{"version":"1.6.166","text":"### 工具结果不再导致客户端退出\n- 修复 Claude Code 返回多块工具结果时客户端崩溃的问题;仅提取文本,不把图片等非文本内容当作文件路径处理。\n- 本地图片检测或转发失败时保留正常任务回复,不再中断客户端或影响后续任务。","changes":[{"topic":"image-output","title":"图片输出","text":"修复 Claude Code 返回多块工具结果时客户端崩溃的问题;仅提取文本,不把图片等非文本内容当作文件路径处理。"},{"topic":"image-output","title":"图片输出","text":"本地图片检测或转发失败时保留正常任务回复,不再中断客户端或影响后续任务。"}],"details":"### Fixed\n- Normalize Claude native tool-result content blocks to text before forwarding; ignore embedded media and unknown payloads instead of passing them to string-only consumers.\n- Exclude native tool-result payloads from raw stdout logging before normalization.\n- Ignore non-string input in local-image detection and contain optional image-forwarding failures without terminating the CLI or failing an otherwise successful task. Preserve web-result exclusions and directory/size checks.\n\n### Tests\n- Cover mixed Claude content blocks, malformed image-detector input, asynchronous tool-result scan failures, final-output failures, and subsequent task execution."},{"version":"1.6.165","text":"### Pi 会话连接更可靠\n- 同一客户端内,不同线程不能同时连接同一个 Pi 会话;连接或断开写盘失败会明确提示失败,不再误报成功。\n- Pi 会话切换与模型等设置修改互斥,后台任务未结束或自动升级时不会切换上下文;Claude Code、Codex 仍仅提供只读列表。\n- 修正 Pi 自定义目录下的会话发现,并让本机重开命令正确处理含空格的会话路径;仍需避免本机与远程同时执行。","changes":[{"topic":"session-handoff","title":"会话接续","text":"同一客户端内,不同线程不能同时连接同一个 Pi 会话;连接或断开写盘失败会明确提示失败,不再误报成功。"},{"topic":"session-handoff","title":"会话接续","text":"Pi 会话切换与模型等设置修改互斥,后台任务未结束或自动升级时不会切换上下文;Claude Code、Codex 仍仅提供只读列表。"},{"topic":"session-handoff","title":"会话接续","text":"修正 Pi 自定义目录下的会话发现,并让本机重开命令正确处理含空格的会话路径;仍需避免本机与远程同时执行。"}],"details":"### Fixed\n- Reserve a selected Pi session file before asynchronous startup across threads in one daemon. Failed or unknown cleanup keeps the file quarantined until recovery; this is not an OS or cross-process writer lock.\n- Require successful pointer persistence before acknowledging Pi connection or detach. Failed writes retain the previous association; cancelled startup cannot commit a new connection.\n- Serialize Pi session confirmations with settings admission and reject context changes during queued work, active delegated tasks, or automatic updates. Claude Code and Codex remain read-only catalogs with unchanged executor and history behavior.\n- Discover default Pi sessions under `PI_CODING_AGENT_DIR`, fail closed for unresolved agent roots, and shell-quote Pi-only local reopen guidance.\n\n### Tests\n- Add concurrent-confirmation, persistence-failure, restart, cancellation, settings-conflict, custom-directory, and non-Pi read-only regressions."},{"version":"1.6.164","text":"### Pi 会话名称可区分\n- 新建 Pi 会话的默认名称使用独立的 session ID,不再重复使用线程 ID;重新打开已保存会话不会覆盖本机设置的名称。已有重名历史不自动改写。","changes":[{"topic":"session-handoff","title":"会话接续","text":"新建 Pi 会话的默认名称使用独立的 session ID,不再重复使用线程 ID;重新打开已保存会话不会覆盖本机设置的名称。已有重名历史不自动改写。"}],"details":"### Fixed\n- Give newly created Pi foreground sessions a default name based on their independent native session ID, not the reusable remote thread ID. `/new` sessions are distinguishable in `/resume`, and reopening a persisted file no longer appends `--name` or overwrites names assigned locally. Adopted sessions and synthetic runtime naming remain unchanged. Existing duplicate names are not rewritten automatically."},{"version":"1.6.163","text":"### Pi 新建对话保留旧会话\n- Pi 前台 `/new` 和 `/clear` 保留旧 session 的历史,为新对话使用独立 ID;旧会话可以通过 `/resume` 再次连接,不会把旧上下文带入新对话。\n- Pi 删除线程也保留原生历史;选择已有会话后、确认成功前,普通消息仍进入当前会话。委派 Worker 和临时元数据会话的清理规则不变。","changes":[{"topic":"session-handoff","title":"会话接续","text":"Pi 前台 `/new` 和 `/clear` 保留旧 session 的历史,为新对话使用独立 ID;旧会话可以通过 `/resume` 再次连接,不会把旧上下文带入新对话。"},{"topic":"session-handoff","title":"会话接续","text":"Pi 删除线程也保留原生历史;选择已有会话后、确认成功前,普通消息仍进入当前会话。委派 Worker 和临时元数据会话的清理规则不变。"}],"details":"### Changed\n- Pi foreground `/new` and `/clear` now remove only the current association and preserve native session history for `/resume`. Fresh conversations use independent random IDs rather than the stable remote thread ID, so retained files cannot resurrect cleared context, including after restart before the next prompt.\n- Pi foreground thread-data deletion also preserves native history. Delegated-worker and temporary metadata runtimes retain their disposable cleanup and thread-ID behavior.\n\n### Tests\n- Cover foreground A to `/new` to independent B, ordinary messages remaining in B during an unconfirmed resume draft, and confirmed native switching back to A. Cover reset/restart identity separation and unchanged synthetic-runtime cleanup."},{"version":"1.6.162","text":"### Pi 会话无需释放即可顺序切换\n- 移除 `/session release`:接管的 Pi 会话每轮飞书任务前会重新加载并校验,同一会话在本机新增的历史会被读入,不需要重新在飞书选择会话;`/session detach` 仍用于解除绑定。\n- 两侧 Pi 可以保持打开,但请保证不同时执行任务;切回本机窗口时仍需原生 `/resume` 重新加载。当前不提供自动本机刷新或并发互斥。","changes":[{"topic":"session-handoff","title":"会话接续","text":"移除 `/session release`:接管的 Pi 会话每轮飞书任务前会重新加载并校验,同一会话在本机新增的历史会被读入,不需要重新在飞书选择会话;`/session detach` 仍用于解除绑定。"},{"topic":"session-handoff","title":"会话接续","text":"两侧 Pi 可以保持打开,但请保证不同时执行任务;切回本机窗口时仍需原生 `/resume` 重新加载。当前不提供自动本机刷新或并发互斥。"}],"details":"### Changed\n- Remove `/session release`, the executor release operation and the persisted released-state gate. Existing adopted pointers with an old released flag remain usable; `/session detach` still confirms association removal without deleting native history.\n- Reload and verify the exact adopted Pi session before every remote prompt, including native slash prompts, so sequential local writes are visible without another remote resume or release step. Idle local Pi windows may remain open, but must resume the same file before their next turn. Simultaneous writing is unsupported and can create separate native branches; no automatic local refresh or writer exclusion is claimed.\n- Reserve remote turn preparation against overlapping execution/context changes and cancel preparation before prompt dispatch on abort/reset/shutdown. Keep legacy private sessions and worker execution unchanged.\n\n### Fixed\n- Synchronize the lockfile package versions with all package manifests."},{"version":"1.6.161","text":"### 会话接续\n- 一个线程现在可以连接并继续一个已有的 Pi 会话:`/resume` 列出当前工作目录的会话,`/resume select` 或 `id` 选中后显示确认,`/resume confirm` 连接;连接不发送任务。\n- 连接时会校验 Pi 实际打开的会话:不一致、已被其他线程占用、或选中后被本机修改都会被拒绝并保留原会话;接管的历史不会被 `/clear` 或 `/thread delete` 删除。\n- `/session` 查看连接状态,`/session release` 停止后端进程并锁定远程使用以方便本机继续,`/session detach` 确认后解除连接。\n- `/resume` 也支持翻页与搜索,令牌 5 分钟内有效且只对发起人、当前线程和工作目录生效。\n- 在本机运行 `remote-cli session show` 可查看重新打开会话的命令;Codex、Claude Code 等其他后端目前只能列出,还不能连接。","changes":[{"topic":"session-handoff","title":"会话接续","text":"一个线程现在可以连接并继续一个已有的 Pi 会话:`/resume` 列出当前工作目录的会话,`/resume select` 或 `id` 选中后显示确认,`/resume confirm` 连接;连接不发送任务。"},{"topic":"session-handoff","title":"会话接续","text":"连接时会校验 Pi 实际打开的会话:不一致、已被其他线程占用、或选中后被本机修改都会被拒绝并保留原会话;接管的历史不会被 `/clear` 或 `/thread delete` 删除。"},{"topic":"session-handoff","title":"会话接续","text":"`/session` 查看连接状态,`/session release` 停止后端进程并锁定远程使用以方便本机继续,`/session detach` 确认后解除连接。"},{"topic":"session-handoff","title":"会话接续","text":"`/resume` 也支持翻页与搜索,令牌 5 分钟内有效且只对发起人、当前线程和工作目录生效。"},{"topic":"session-handoff","title":"会话接续","text":"在本机运行 `remote-cli session show` 可查看重新打开会话的命令;Codex、Claude Code 等其他后端目前只能列出,还不能连接。"}],"details":"### Added\n- Reserve `/resume`, `/r` and `/session` as program-owned native session controls before executor construction, working-directory changes, queue admission or backend slash passthrough, and remove the misleading natural-language resume shortcut. Local session sharing stays disabled by default; enabling it never makes an unverified adapter available.\n- Add read-only native session discovery for Pi, Codex and Claude Code: `/resume` lists the current workspace's sessions (bounded reads, no backend process, no transcript text, no symlink following), hiding synthetic, delegated-worker, sidechain and ambiguous duplicate entries and reporting incomplete coverage. Message counts stay unavailable where they cannot be read safely.\n- Add paging and search to the read-only list: each list is a snapshot with an unguessable 12-character token, eight rows per page and a five-minute lifetime, bound to the requesting user, thread and workspace; `/resume page` and `/resume search` never reread native stores.\n- Connect a thread to an existing Pi session and continue its history. `/resume select` or `/resume id` shows a confirmation naming the session and any binding it replaces, and `/resume confirm` connects it. The loaded identity is verified through Pi RPC state without sending a prompt, so a silently substituted session is refused and the previous conversation is restored.\n- Add `/session` binding status, `/session release` (stop the owned Pi process and block remote work so a local Pi can take over) and `/session detach` (forget the association after confirmation). Adopted native history is user-owned: `/clear`, detach and `/thread delete` never delete it. A session held by another remote-cli thread, or changed locally after selection, is refused.\n- Add `remote-cli session show --thread <name> --backend <key>`: a read-only, daemon-free helper printing exact native reopen guidance."},{"version":"1.6.160","text":"### 切换后端不再需要确认按钮\n- 后端选择仍在卡片上方,点击后端直接切换,默认只影响当前线程,不再需要点击 Confirm;收到成功确认后才更新选中状态。\n- 下方范围按钮只设置下一次切换的目标,不会单独切换后端;同一卡片保留所选范围,重新打开默认当前线程,跟随全局只作用于当前线程。","changes":[{"topic":"settings-cards","title":"设置卡片","text":"后端选择仍在卡片上方,点击后端直接切换,默认只影响当前线程,不再需要点击 Confirm;收到成功确认后才更新选中状态。"},{"topic":"settings-cards","title":"设置卡片","text":"下方范围按钮只设置下一次切换的目标,不会单独切换后端;同一卡片保留所选范围,重新打开默认当前线程,跟随全局只作用于当前线程。"}],"details":"### Changed\n- Remove the backend card's Confirm section. Backend choices submit immediately using the selected scope, defaulting to Current thread, while Choose backend remains above Apply to. Scope buttons only change the next backend click's target; keep that scope within the same card after acknowledgement. Show only the acknowledged backend as selected, disable further changes while pending, and preserve exact-request retries and stale-revision validation. Follow global applies immediately to the original thread and restores the local scope to Current thread after acknowledgement. Existing CLI settings actions and text commands remain compatible."},{"version":"1.6.159","text":"### 大项目委派准备允许更长等待\n- 创建 Worker 工作目录和切换检出内容的超时从 15 秒提高到 120 秒,减少大项目在子 Agent 启动前超时;其他 Git 操作保持原有时限。\n- Git 超时提示显示具体操作、耗时和时限,方便定位准备阶段的问题。","changes":[{"topic":"delegation","title":"委派任务","text":"创建 Worker 工作目录和切换检出内容的超时从 15 秒提高到 120 秒,减少大项目在子 Agent 启动前超时;其他 Git 操作保持原有时限。"},{"topic":"delegation","title":"委派任务","text":"Git 超时提示显示具体操作、耗时和时限,方便定位准备阶段的问题。"}],"details":"### Fixed\n- Allow delegated `git worktree add` and `git checkout` commands up to 120 seconds so larger working trees can finish preparing. Other Git commands and nested object transfers retain their 15-second deadlines. Timeout messages identify the worktree subcommand and report elapsed time and the deadline without including paths or checkout references. Preserve child-exit waiting, kill escalation, output limits, task reservations and cancellation ordering."},{"version":"1.6.158","text":"### 减少空正文的完成续卡\n- 收尾时在容量允许的情况下,将最后一段正文和完成信息、线程按钮放在同一张卡片,避免单独多出一张只有完成区的续卡;保留 Worker 分组和卡片容量限制。","changes":[{"topic":"tool-cards","title":"工具卡片","text":"收尾时在容量允许的情况下,将最后一段正文和完成信息、线程按钮放在同一张卡片,避免单独多出一张只有完成区的续卡;保留 Worker 分组和卡片容量限制。"}],"details":"### Fixed\n- Keep the completion note, optional execution metadata and thread controls with the final body item or complete worker group when they fit together within continuation-card node, size and table budgets. Avoid a preventable footer-only continuation, including replies without execution metadata; retain the body when refreshing thread controls. Oversized indivisible groups still respect capacity limits. Streaming, queue confirmations and bare settings cards retain their existing behavior."},{"version":"1.6.157","text":"### 委派后端状态恢复彩色标签\n- 后端可用性恢复彩色状态标签:主 Agent 蓝色、已安装绿色、受限橙色、不可用红色,未知状态灰色;On/Off 操作保持不变。","changes":[{"topic":"delegation","title":"委派任务","text":"后端可用性恢复彩色状态标签:主 Agent 蓝色、已安装绿色、受限橙色、不可用红色,未知状态灰色;On/Off 操作保持不变。"}],"details":"### Changed\n- Restore colored status badges in the `/delegation` card's backend-availability section: blue for the coordinator, green for installed workers, orange for blocked workers, red for unavailable backends and neutral for unknown worker availability. Preserve literal detail escaping, card capacity accounting and acknowledged On/Off controls."},{"version":"1.6.156","text":"### 委派开关支持卡片操作\n- /delegation 新增当前线程的 On/Off 开关卡片,选中项蓝色高亮;点击后收到成功确认才更新状态。\n- 后端可用性单独展示,明确提示未安装和沙箱限制;运行中仍可查看,切换需等待任务完成,旧版本继续使用文字命令。","changes":[{"topic":"delegation","title":"委派任务","text":"/delegation 新增当前线程的 On/Off 开关卡片,选中项蓝色高亮;点击后收到成功确认才更新状态。"},{"topic":"delegation","title":"委派任务","text":"后端可用性单独展示,明确提示未安装和沙箱限制;运行中仍可查看,切换需等待任务完成,旧版本继续使用文字命令。"}],"details":"### Added\n- Add a thread-scoped `/delegation` settings card with blue checked On/Off controls and a separate backend-availability section. Clicks submit immediately, update selection only after durable CLI acknowledgement, and preserve pending/unknown states and exact-request retries. Running work and queued commands block mutation, not inspection or refresh; reset remains a separate text command.\n- Negotiate `delegationCards` in addition to `settingsCards` on protocol v1. Older peers retain the existing delegation status text and parameterized commands. Reuse immutable snapshots, ownership checks, admission barriers and native cleanup for card/text toggles; distinguish the enabled preference from sandbox restrictions, installation, authentication and quota."},{"version":"1.6.155","text":"### 设置卡片减少翻页,选中与后端分区更清晰\n- 模型和思考等级能放下一张卡片时全部展示,只有实际超出容量才分页,不再每八项强制翻页。\n- 后端卡片中选中的影响范围用蓝色高亮,选择当前线程或全部线程后仍需确认才生效。\n- 模型和思考等级卡片将当前主后端与其他后端分区展示,查看其他后端不会切换主后端。","changes":[{"topic":"settings-cards","title":"设置卡片","text":"模型和思考等级能放下一张卡片时全部展示,只有实际超出容量才分页,不再每八项强制翻页。"},{"topic":"settings-cards","title":"设置卡片","text":"后端卡片中选中的影响范围用蓝色高亮,选择当前线程或全部线程后仍需确认才生效。"},{"topic":"settings-cards","title":"设置卡片","text":"模型和思考等级卡片将当前主后端与其他后端分区展示,查看其他后端不会切换主后端。"}],"details":"### Changed\n- Show all model and effort choices when the complete settings card fits its recursive node and UTF-8 JSON budgets. Paginate only oversized catalogs, packing each page by actual capacity instead of a fixed eight-choice limit. Count headers, sections, backend groups, navigation, notices and pending/retry controls, preserve every opaque choice and retain existing callback validation and single-card delivery.\n- Highlight the drafted backend application scope in blue. Separate the current thread's main backend from other backends' worker preferences in model/effort cards, keeping the main role tied to the coordinator while viewing other targets. Preserve same-backend preference sharing, explicit backend confirmation and immediate acknowledged model/effort changes; no native request or protocol capability is added."},{"version":"1.6.154","text":"### 设置选择更清晰,减少测试等待\n- 后端、模型和思考等级按功能分区,补充小标题和选中标记,后端选择、影响范围与确认按钮不再混在一起。\n- 兼容 AGY 模型列表的两种列格式,空结果或无法识别的列表会明确提示,不再无说明地显示空菜单。\n- 减少大仓库检查和测试样本准备的串行开销,移除模拟进程测试中的真实等待,八核以上机器可并行运行更多 Git 测试;发布仍执行全量测试,不降低安全检查或缩小压力样本。","changes":[{"topic":"settings-cards","title":"设置卡片","text":"后端、模型和思考等级按功能分区,补充小标题和选中标记,后端选择、影响范围与确认按钮不再混在一起。"},{"topic":"settings-cards","title":"设置卡片","text":"兼容 AGY 模型列表的两种列格式,空结果或无法识别的列表会明确提示,不再无说明地显示空菜单。"},{"topic":"delegation","title":"委派任务","text":"减少大仓库检查和测试样本准备的串行开销,移除模拟进程测试中的真实等待,八核以上机器可并行运行更多 Git 测试;发布仍执行全量测试,不降低安全检查或缩小压力样本。"}],"details":"### Changed\n- Separate backend, model and effort cards into numbered functional sections with subtitles and dividers. Mark the drafted backend, applied backend and selected scope explicitly; keep Confirm separate. Model/effort cards separate the target backend, native choices and secondary actions, checking configured or known effective selections without guessing defaults. Include all new section elements in recursive node and byte accounting; retain existing validation, acknowledgements and old-peer behavior.\n- Accept both tab-delimited and formatted multi-space AGY model catalogs, preserving opaque native IDs and exact current-model matching. Reject empty, unusable and oversized responses explicitly instead of silently producing an empty or truncated menu. Query native metadata only; never prompt a model to invent catalog entries.\n- Bound filesystem verification to eight concurrent checks and drain all started work before propagating failure. Share complete ancestor-validation promises within each checkpoint pass, and give checkout byte readers independent buffers up to 1 MiB each. Preserve every file hash, symlink/mode check, HEAD/index recheck, both working-file passes and both reclamation audits; do not cache state across captures or relax production deadlines.\n- Replace real startup/stop waits in mocked Claude executor tests with controlled clocks. Advance the nested transfer timeout only after real producer/receiver startup and a nonempty partial pack, retaining process-exit and quarantine-cleanup assertions. Generate document ZIP fixture CRCs with a lookup table while preserving identical archive bytes, full expansion-bomb payloads and the full publish test suite. Use at most four isolated Git test processes only on hosts with at least eight available CPUs; lower-core limits and ordinary test deadlines are unchanged."},{"version":"1.6.153","text":"### 测试提速,Codex 命令说明更完整\n- 调整真实 Git 测试的并行资源并减少重复建仓开销,发布仍执行完整测试,不放宽委派文件安全检查或普通测试超时。\n- Codex 命令在没有原生动作摘要时也能显示简短操作标签,无法可靠识别时显示通用说明,不展示命令参数或把阶段思考套到工具上。\n- 晚到的原生动作信息可补充原来的工具栏,成功和失败结果仍更新原行,不新增卡片元素。","changes":[{"topic":"delegation","title":"委派任务","text":"调整真实 Git 测试的并行资源并减少重复建仓开销,发布仍执行完整测试,不放宽委派文件安全检查或普通测试超时。"},{"topic":"tool-cards","title":"工具卡片","text":"Codex 命令在没有原生动作摘要时也能显示简短操作标签,无法可靠识别时显示通用说明,不展示命令参数或把阶段思考套到工具上。"},{"topic":"tool-cards","title":"工具卡片","text":"晚到的原生动作信息可补充原来的工具栏,成功和失败结果仍更新原行,不新增卡片元素。"}],"details":"### Changed\n- Keep real Git suites in isolated processes while allowing up to two Git forks on hosts with at least four available CPUs and one to four lightweight threads. Reuse only pristine test fixture templates, copying repository metadata and files into independent owned directories for every test. The publish lifecycle still runs the entire suite without changing production Git checks or ordinary deadlines.\n- Fill Codex shell-call labels for absent and native unknown command actions with bounded fixed operation descriptions. Simple allowlisted programs receive labels such as Run npm command; compound or unrecognized commands stay generic. Preserve native read/search/list descriptions and every operation in compound action sets. Never copy shell arguments, complete paths, execution output, or turn-level reasoning into fallback headings, and do not claim model-authored purpose summaries.\n- Forward optional public native titles and allow later action metadata to enrich a pending tool row before its first result. Suppress duplicate starts after a result so repeated completion updates retain the original invocation. Reuse existing tool metadata, compact heading limits, asynchronous status updates, and card-element accounting without a wire-version change or extra model call."},{"version":"1.6.152","text":"### 后端、模型与思考等级可点击选择\n- `/backend` 打开选择卡片,默认只改当前线程;选择后端和影响范围后点击确认才生效,未安装的后端会明确标为不可选。\n- `/model`、`/effort` 可以直接点击原生选项,也能为其他后端设置模型和思考等级,不必先切换主 Agent;没有原生选项时会说明原因,不猜测支持情况。\n- 设置成功后才显示已应用;旧卡片、重复点击和忙碌线程会受到保护,旧版仍可使用文字命令。","changes":[{"topic":"settings-cards","title":"设置卡片","text":"`/backend` 打开选择卡片,默认只改当前线程;选择后端和影响范围后点击确认才生效,未安装的后端会明确标为不可选。"},{"topic":"settings-cards","title":"设置卡片","text":"`/model`、`/effort` 可以直接点击原生选项,也能为其他后端设置模型和思考等级,不必先切换主 Agent;没有原生选项时会说明原因,不猜测支持情况。"},{"topic":"settings-cards","title":"设置卡片","text":"设置成功后才显示已应用;旧卡片、重复点击和忙碌线程会受到保护,旧版仍可使用文字命令。"}],"details":"### Added\n- Negotiate standalone backend, model, and effort settings cards on protocol version 1. Backend selection defaults to the original current thread; selecting a backend or device-wide scope only edits a draft until Confirm. Model and effort choices submit immediately, including preferences for an inactive target backend without switching the coordinator. Missing backends remain disabled; unavailable native catalogs and model-specific effort controls are explicit rather than generated from prompts.\n- Bind immutable choices to the original owner, device, thread, working context and configuration revision. Serialize native changes and persistence with affected command admission, invalidate stale menus, and acknowledge only confirmed changes. Bound snapshot and retry receipts, paginate choices with recursive card-node and byte accounting, and preserve parameterized text-command semantics and older-peer fallbacks. No backend installation, credential mutation, live deployment or inference is performed to build menus.\n\n### Changed\n- Use native structured model and effort metadata, including grouped ACP choices, model-specific Pi thinking levels, bounded AGY model rows, and capability-gated Claude control initialization. Keep configured selections distinct from native reports and defaults. Isolated metadata identities inherit policy resolved under the real thread ID, never share coordinator/Worker pointers, and clean up only their own confirmed-exited data. Claude model updates also maintain its legacy preference field.\n- Bound ACP control requests without timing out normal inference, preserve opaque native IDs, refresh Claude capabilities per process, and reject incompatible model/effort changes rather than silently changing a second preference. Release known temporary ACP sessions before transport shutdown and defer own-pointer cleanup after a timed-out query until settlement and confirmed exit."},{"version":"1.6.151","text":"### 委派快照与测试更稳\n- 减少普通仓库和子模块委派快照的重复 Git 查询,继续检查文件变化、仓库边界和成果回收安全,不跨任务复用旧文件状态。\n- 限制真实 Git 测试同时占用的资源,并修复断言失败后收尾卡住的问题;不改变 Worker 的启动、退出和 Git 命令超时。","changes":[{"topic":"delegation","title":"委派任务","text":"减少普通仓库和子模块委派快照的重复 Git 查询,继续检查文件变化、仓库边界和成果回收安全,不跨任务复用旧文件状态。"},{"topic":"delegation","title":"委派任务","text":"限制真实 Git 测试同时占用的资源,并修复断言失败后收尾卡住的问题;不改变 Worker 的启动、退出和 Git 命令超时。"}],"details":"### Changed\n- Reduce delegated Git checkpoint subprocesses by reading paths, conflict stages, and hidden-entry flags together from each private index. Resolve the source index path once per pass and audit identical content-addressed trees once per capture; retain both full working-file passes, source HEAD/index rechecks, copied-index timestamps, nested-repository validation, and independent checkout byte audits. Reject existing zero-byte indexes instead of treating corrupt metadata as missing; legitimate missing and serialized zero-entry indexes remain supported. No state is cached across captures and Git deadlines are unchanged.\n- Bound real Git integration suites to one isolated process alongside at most two lightweight test threads. Keep ordinary test and hook deadlines unchanged; give historical delivery the same explicit 30-second budget as other Git suites. Release controlled lifecycle gates in finally blocks, cover slow collection and early assertion failure, and guard subprocess counts against regressions."},{"version":"1.6.150","text":"### Codex Banked Reset 增加提醒\n- Codex 的 Banked Reset 数量比上一次有效检查增加时发送提醒,显示前后数量及增加量;减少或不变不提醒,减少后再增长也能正常提醒。\n- 复用启动及每小时的额度检查,首次检查、重启或切换账号只建立基线;读不到数量不会当成零,也不会自动使用重置次数,旧版仍保持原有提醒。\n- 提醒已送达但确认消息丢失时,CLI 重连会确认原来的卡片,不会为同一次增长重复发送提醒。","changes":[{"topic":"maintenance-notices","title":"更新与额度提醒","text":"Codex 的 Banked Reset 数量比上一次有效检查增加时发送提醒,显示前后数量及增加量;减少或不变不提醒,减少后再增长也能正常提醒。"},{"topic":"maintenance-notices","title":"更新与额度提醒","text":"复用启动及每小时的额度检查,首次检查、重启或切换账号只建立基线;读不到数量不会当成零,也不会自动使用重置次数,旧版仍保持原有提醒。"},{"topic":"maintenance-notices","title":"更新与额度提醒","text":"提醒已送达但确认消息丢失时,CLI 重连会确认原来的卡片,不会为同一次增长重复发送提醒。"}],"details":"### Added\n- Notify about Codex Banked Reset balance increases using the existing independent startup/hourly status read and native `rateLimitResetCredits.availableCount`. First observations and account switches are silent; compare each valid count with the previous valid count for that account, not a historical maximum. Decreases update the baseline without notifying, and missing or invalid fields remain unknown rather than zero.\n- Reuse standalone, notification-only quota cards and delivery acknowledgements, with previous/current balances and the increase. Keep banked-credit events separate from weekly quota delivery suppression, cancel pending notices on observed consumption/account changes, and retry only the latest pending event. Retain up to 1,000 banked delivery receipts in Router memory until notice expiry, including in-flight reservations, so lost-ACK retries across CLI reconnects revalidate ownership and acknowledge the existing card instead of sending duplicates; action bindings remain connection-scoped. A new additive `bankedResetReminder` capability prevents old Routers from mislabeling banked-credit notices. No extra native read, model request, credit consumption, expiry warning, or persisted balance is introduced."},{"version":"1.6.149","text":"### 更多工具调用有简短说明\n- AGY 的工具调用显示它自带的本次调用摘要;Codex 的读取文件、搜索和列目录命令也能显示简短动作说明,无法识别时仍保持简洁,不把整个任务的阶段摘要套到工具上。\n- 说明复用原有工具栏,不增加卡片元素或额外模型调用;晚到的成功、失败结果仍更新原行的状态颜色。\n- Codex 网页工具的展开详情可以查看搜索、打开网页和页内查找的结果标题、来源链接和摘要;预览最多五条,省略数量会明确提示,不再把缺少结果字段误显示为空结果。\n- 修复 AGY 部分搜索调用丢失搜索词,以及非文本工具输出被忽略的问题;网页结果复用原有详情区域,不增加卡片元素。\n- 网页摘要不会因提到本地图片路径而自动上传图片,兼容旧版的文本预览也保持为纯文本;AGY 工具失败时保留错误原因和结构化输出。","changes":[{"topic":"tool-cards","title":"工具卡片","text":"AGY 的工具调用显示它自带的本次调用摘要;Codex 的读取文件、搜索和列目录命令也能显示简短动作说明,无法识别时仍保持简洁,不把整个任务的阶段摘要套到工具上。"},{"topic":"tool-cards","title":"工具卡片","text":"说明复用原有工具栏,不增加卡片元素或额外模型调用;晚到的成功、失败结果仍更新原行的状态颜色。"},{"topic":"tool-cards","title":"工具卡片","text":"Codex 网页工具的展开详情可以查看搜索、打开网页和页内查找的结果标题、来源链接和摘要;预览最多五条,省略数量会明确提示,不再把缺少结果字段误显示为空结果。"},{"topic":"tool-cards","title":"工具卡片","text":"修复 AGY 部分搜索调用丢失搜索词,以及非文本工具输出被忽略的问题;网页结果复用原有详情区域,不增加卡片元素。"},{"topic":"tool-cards","title":"工具卡片","text":"网页摘要不会因提到本地图片路径而自动上传图片,兼容旧版的文本预览也保持为纯文本;AGY 工具失败时保留错误原因和结构化输出。"}],"details":"### Changed\n- Forward AGY's native per-call `toolSummary` and fallback `toolAction` as tool descriptions while preserving explicit descriptions and titles. Terminal results keep the original invocation identity and do not synthesize new calls or copy execution-wide activity into labels.\n- Describe Codex's structured `commandActions` as file reads, searches, and directory listings. Use file basenames only, omit raw commands and search arguments, and leave absent, unknown, or partly unknown action sets unlabeled. Reserve omitted-label counts within the existing 60-character heading budget. Reuse existing description fields and compact headings without additional model calls, protocol changes, or card elements.\n- Preserve Codex's native web search, open-page, and find-in-page actions and result entries instead of reporting empty output. Foreground tools show up to five bounded titles, source links, and snippets in the existing output node, with explicit omitted-entry counts and distinct missing, unsupported, and empty-result notices. An additive optional result preview retains a plaintext fallback for older Routers; source links are revalidated and result text is rendered literally. Delayed result updates keep the original invocation slot and recursive pagination limits.\n- Accept AGY's native lowercase `query` as well as legacy `Query`, and preserve non-string tool outputs as JSON alongside any supplied failure explanation instead of discarding either. Add web-result passthrough regressions for Claude, shared ACP backends (OpenCode, Kimi, ZCode, DSH), and Pi without assuming unavailable native samples were verified.\n- Treat structured web previews and recognized web-tool results as display data, not local-image instructions; repeated results retain their origin until an explicit new call reuses the ID. Ordinary local-tool image forwarding remains available. Prefix every native fallback field so untrusted snippets cannot close older Routers' fixed code fences."},{"version":"1.6.148","text":"### 工具状态颜色更直观\n- 工具调用统一使用小圆点:成功绿色、执行中蓝色、失败红色,去掉沙漏和叉号;结果晚到仍在原行更新颜色,不增加卡片元素。","changes":[{"topic":"tool-cards","title":"工具卡片","text":"工具调用统一使用小圆点:成功绿色、执行中蓝色、失败红色,去掉沙漏和叉号;结果晚到仍在原行更新颜色,不增加卡片元素。"}],"details":"### Changed\n- Use a consistent dot in every foreground tool heading: green after success, blue while awaiting a result, and red after failure. Preserve per-call labels, explicit expanded status text, fixed-slot asynchronous updates, and recursive card-node counts without adding elements."},{"version":"1.6.147","text":"### 工具调用说明更清楚\n- 工具名后优先显示后端提供的本次调用说明或标题,没有说明时显示文件名等明确标签;不重复工具名,也不把整个任务的阶段摘要套到每条工具上。\n- 调用说明和晚到的成功、失败结果仍更新原来的工具栏,不增加卡片元素;没有说明的后端保持简洁显示。","changes":[{"topic":"tool-cards","title":"工具卡片","text":"工具名后优先显示后端提供的本次调用说明或标题,没有说明时显示文件名等明确标签;不重复工具名,也不把整个任务的阶段摘要套到每条工具上。"},{"topic":"tool-cards","title":"工具卡片","text":"调用说明和晚到的成功、失败结果仍更新原来的工具栏,不增加卡片元素;没有说明的后端保持简洁显示。"}],"details":"### Changed\n- Prefer meaningful backend-provided per-call descriptions and titles in foreground tool headings, falling back to file basenames and omitting redundant tool-name labels. Preserve ACP call/update titles and explicit AGY/Pi parameter labels that tool mapping previously discarded; never synthesize a call to refresh a terminal-result title.\n- Carry optional tool labels over the existing version-1 stream without new capabilities or model calls. Keep execution-wide activity separate, retain fixed-slot asynchronous result updates, and verify unchanged recursive card-node budgets through pagination and shrink."},{"version":"1.6.146","text":"### 工具栏样式更统一清爽\n- Bash 和文件工具统一显示状态符号、工具名和简短说明:成功用浅灰小点,失败用浅灰普通叉,等待结果用沙漏,不再堆叠彩色状态标签。\n- 完整工具编号、参数、输出和修改预览保留在展开详情里;长回复继续自动分片,结果晚到也会更新原来的工具栏。","changes":[{"topic":"tool-cards","title":"工具卡片","text":"Bash 和文件工具统一显示状态符号、工具名和简短说明:成功用浅灰小点,失败用浅灰普通叉,等待结果用沙漏,不再堆叠彩色状态标签。"},{"topic":"tool-cards","title":"工具卡片","text":"完整工具编号、参数、输出和修改预览保留在展开详情里;长回复继续自动分片,结果晚到也会更新原来的工具栏。"}],"details":"### Changed\n- Use one compact foreground tool heading for Bash and other tools: a gray success dot, pending hourglass, or gray failure cross, followed by the tool name and an optional bounded public description or file basename. Keep raw commands out of headings and move full tool IDs and explicit status labels into the existing expanded details.\n- Preserve input, result, diff previews, stable call identities, and existing cross-card cleanup. Verify recursive tagged-node counts at the card boundary through delayed results, activity tails, and completion controls; no multi-call aggregation, execution, or wire-protocol change."},{"version":"1.6.145","text":"### 工具调用反馈更紧凑\n- 同一次工具调用和结果合为一条折叠栏,完成后直接更新成功或失败状态,减少长回复中的滚动。\n- 展开仍可查看参数、输出和代码修改预览;不同工具调用继续分开显示,错误状态保持醒目。","changes":[{"topic":"tool-cards","title":"工具卡片","text":"同一次工具调用和结果合为一条折叠栏,完成后直接更新成功或失败状态,减少长回复中的滚动。"},{"topic":"tool-cards","title":"工具卡片","text":"展开仍可查看参数、输出和代码修改预览;不同工具调用继续分开显示,错误状态保持醒目。"}],"details":"### Changed\n- Render each foreground tool call and its matching result as one collapsed row, updating its status in place while retaining bounded input, output, and per-file diff previews. Keep later text and worker slots stable; preserve unmatched results without guessing a pairing.\n- Keep independent calls separate, including adapter ID reuse after a completed invocation. Remove previous tool copies before cross-card moves, including still-active and surplus pages, preserving worker context controls and retryable updates. Backend execution, protocol version, and approval flows are unchanged."},{"version":"1.6.144","text":"### 随时看清 Agent 正在做什么\n- 主 Agent 在最新回复卡片底部显示当前活动,子 Agent 在自己的标题下显示;长回复翻页后仍能看到最新进度。\n- 显示后端提供的公开进度、计划步骤和工具说明,等待输入或任务结束时切换状态;不展示原始思考,也不猜测完成百分比。","changes":[{"topic":"agent-activity","title":"运行进度","text":"主 Agent 在最新回复卡片底部显示当前活动,子 Agent 在自己的标题下显示;长回复翻页后仍能看到最新进度。"},{"topic":"agent-activity","title":"运行进度","text":"显示后端提供的公开进度、计划步骤和工具说明,等待输入或任务结束时切换状态;不展示原始思考,也不猜测完成百分比。"}],"details":"### Added\n- Show bounded public activity at the tail of the latest active coordinator card and below each managed worker's identity. Separate explicit Codex commentary and public reasoning summaries, public assistant updates, plan steps, and safe tool descriptions from answer text; never promote raw thinking or estimate completion percentages.\n- Negotiate optional activity progress without a protocol-version change. Coalesce snapshots, preserve worker-result publication barriers, prioritize input and terminal states, discard late events, and leave older peers on their existing presentation."},{"version":"1.6.143","text":"### Codex 用量查询等待时间延长\n- 将 `/status` 查询 Codex 用量的等待时间从 5 秒延长至 10 秒,减少响应较慢时缺少用量信息的情况。","changes":[{"topic":"codex-usage","title":"Codex 用量","text":"将 `/status` 查询 Codex 用量的等待时间从 5 秒延长至 10 秒,减少响应较慢时缺少用量信息的情况。"}],"details":"### Fixed\n- Increase the Codex account-usage RPC timeout from five to ten seconds for `/status`, without adding retries or changing failure handling."},{"version":"1.6.142","text":"### 同一后端也能分工协作\n- 主 Agent 现在也可调用同一后端的独立 Worker,不共用主会话;Git 项目仍可并行分工,成果仍需明确合并或保留。","changes":[{"topic":"delegation","title":"委派任务","text":"主 Agent 现在也可调用同一后端的独立 Worker,不共用主会话;Git 项目仍可并行分工,成果仍需明确合并或保留。"}],"details":"### Added\n- Allow unrestricted coordinators to delegate to their own backend through independent managed worker sessions. Preserve synthetic lane identities, isolated Git checkouts, shared-directory FIFO scheduling, explicit artifact integration, context-reset ownership, and existing task/concurrency budgets.\n\n### Changed\n- Report the coordinator backend's worker eligibility in discovery and status using the same admission policy, and align injected tool instructions. Do not advertise sandbox-restricted workers as eligible in the delegation menu. Keep restricted coordinators and read_only requests ineligible; native backend subagents and the Router wire protocol remain unchanged."},{"version":"1.6.141","text":"### 含子仓库的项目也能委派\n- 已初始化的 Git 子模块和嵌套仓库现在可以参与委派,包含未提交修改;应用成果时保留原有会话、仓库提交和暂存状态。\n- 文件与目录互换不再误报;未初始化的子模块不阻止审阅其他代码,真正不支持的文件会显示具体路径和类型。","changes":[{"topic":"delegation","title":"委派任务","text":"已初始化的 Git 子模块和嵌套仓库现在可以参与委派,包含未提交修改;应用成果时保留原有会话、仓库提交和暂存状态。"},{"topic":"delegation","title":"委派任务","text":"文件与目录互换不再误报;未初始化的子模块不阻止审阅其他代码,真正不支持的文件会显示具体路径和类型。"}],"details":"### Fixed\n- Include initialized local submodules and embedded repositories in private delegated snapshots, with staged, unstaged, and nonignored files captured through their own temporary indexes. Stream local Git objects without remote fetching or a repository-size cap; workers receive ordinary files rather than nested Git metadata or histories.\n- Apply nested working-file changes through explicit artifact integration while preserving all source HEADs, indexes, and gitlinks. Include nested state in delivery revisions, reject changed repository identities and boundary replacements, preserve uncertain worker-created Git metadata for manual recovery, and keep uninitialized submodules empty without blocking unrelated work.\n- Allow ordinary file/directory replacements and identify unsupported filesystem entries by repository-relative path and type. Cover nested snapshots, conflicts, state preservation, streamed transfer, artifact delivery, and guarded checkout reclamation/reuse with real temporary Git repositories.\n- Preserve warm index stat caches and the original index timestamp so racy-clean detection still catches same-size edits; reuse completed local object transfers within each stable capture. Reject ancestor worktrees, external nested Git metadata, nested-local command filters, and partial-clone hydration. Keep unsupported no-change metadata pending until explicit retention, and wait for deterministic Git lifecycle signals in cancellation tests.\n- Receive nested packs in a per-transfer quarantine and publish complete packs with indexes last. Clean failed and timed-out transfers after both processes exit without sweeping other operations. Discover embedded repositories exposed by gitlink replacements and support initialized submodules owned by linked-worktree metadata stores."},{"version":"1.6.140","text":"### 大项目委派与异常恢复更稳妥\n- 准备工作区或收集成果较慢时,不再误判后台进程异常、锁住整个项目;取消任务后也不会偷偷启动 Worker。\n- 无法完整读取被 Git 标记隐藏的修改时,会明确提示并保留文件,不再把遗漏的修改当成已完整交付。","changes":[{"topic":"delegation","title":"委派任务","text":"准备工作区或收集成果较慢时,不再误判后台进程异常、锁住整个项目;取消任务后也不会偷偷启动 Worker。"},{"topic":"delegation","title":"委派任务","text":"无法完整读取被 Git 标记隐藏的修改时,会明确提示并保留文件,不再把遗漏的修改当成已完整交付。"}],"details":"### Fixed\n- Reject assume-unchanged and skip-worktree index entries before capturing delegated Git checkpoints. Do not silently omit hidden edits, reinterpret absent sparse files as deletions, or modify the source index; preserve unresolved worker files for manual recovery.\n- Keep managed Git baseline capture, checkout preparation, and repository-lock waits outside the native worker startup deadline. Await owned mutations before releasing execution capacity, and prevent late worker startup after cancellation.\n- Bound accepted Git delegation and cancellation response waits below the tool adapter's timeout. Return the existing task ID and explicit pending status for later polling without aborting owned operations, pretending cleanup finished, or encouraging duplicate submission.\n- Separate confirmed process shutdown from artifact collection. Slow collection no longer quarantines the source workspace or leaks global worker slots; collection and lane-persistence failures retain the affected lane while releasing unrelated capacity after Git operations settle. Preserve native-exit quarantine, individual Git command deadlines, non-Git FIFO scheduling, and old-peer compatibility."},{"version":"1.6.139","text":"### 大仓库也能正常委派任务\n- 取消按仓库总大小和文件数量拒绝子任务的限制,大型项目也可执行委派、合并成果并再次使用工作目录。","changes":[{"topic":"delegation","title":"委派任务","text":"取消按仓库总大小和文件数量拒绝子任务的限制,大型项目也可执行委派、合并成果并再次使用工作目录。"}],"details":"### Fixed\n- Remove the fixed 128 MiB repository-size and 10,000-file limits from delegated Git input snapshots, filtered trees, artifact collection, and checkout reclamation verification. Large repositories keep their complete staged, unstaged, and nonignored untracked input without a replacement size configuration.\n- Preserve path and entry validation, artifact ownership and reference checks, streamed byte hashing before reclamation, parent index and branch isolation, and existing Git command deadlines and output-buffer limits. Add regression coverage for large committed and untracked files and complete artifact integration, reclamation, and reuse beyond the former limits."},{"version":"1.6.138","text":"### 委派收尾与会话恢复更可靠\n- 子任务成果已处理完时,不再因为其他会话忙碌而误报收尾失败或反复要求处理。\n- 重试旧卡片的上下文清理时,不再影响后来创建的 Worker 会话;状态不明的旧会话仍会保留。\n- 子任务在准备工作区之前启动失败时,可继续复用原 Worker;工作区状态不确定时仍保留安全保护。","changes":[{"topic":"delegation","title":"委派任务","text":"子任务成果已处理完时,不再因为其他会话忙碌而误报收尾失败或反复要求处理。"},{"topic":"delegation","title":"委派任务","text":"重试旧卡片的上下文清理时,不再影响后来创建的 Worker 会话;状态不明的旧会话仍会保留。"},{"topic":"delegation","title":"委派任务","text":"子任务在准备工作区之前启动失败时,可继续复用原 Worker;工作区状态不确定时仍保留安全保护。"}],"details":"### Fixed\n- Validate settled worker artifact receipts independently of source-workspace contention, avoiding spurious closeout failures and extra coordinator turns. Keep ownership, reference, recovery, cancellation, and receipt-integrity checks; history reconciliation still requires the source lease.\n- Keep a superseded shared-directory lane non-reusable after a context-clear retry, without deleting another worker's conversation. Persist pooling mode for independent Git lanes and preserve ambiguous legacy duplicate contexts instead of scheduling automatic deletion.\n- Return reused Git lanes to ready after failures before checkout preparation starts. Continue preserving uncertain prepared lanes, and distinguish executor setup failures from checkout failures in recovery diagnostics."},{"version":"1.6.137","text":"### 单独清理子任务上下文\n- 子任务结束后,无论成功还是失败,都可在卡片上点击 Clear context,让该 Worker 下次从新会话开始,不影响主 Agent、其他 Worker 或代码成果。\n- 清理收到本机确认后才显示成功;运行中的任务和过期卡片不会误清新会话,失败可重试,不会自动重跑任务。","changes":[{"topic":"delegation","title":"委派任务","text":"子任务结束后,无论成功还是失败,都可在卡片上点击 Clear context,让该 Worker 下次从新会话开始,不影响主 Agent、其他 Worker 或代码成果。"},{"topic":"delegation","title":"委派任务","text":"清理收到本机确认后才显示成功;运行中的任务和过期卡片不会误清新会话,失败可重试,不会自动重跑任务。"}],"details":"### Added\n- Add an owner-bound Clear context control outside delegated Worker card details after successful or failed execution. Reset only the exact idle lane's native continuation, retaining workspaces, artifacts, archived transcripts, authentication, and settings without replaying the task or resetting the coordinator.\n- Negotiate optional workerContextReset support and require CLI acknowledgement before confirming success. Persist reset intents and context epochs, serialize reset with lane acquisition, reject stale or unsafe targets, and permit explicit retries after interrupted resets. Keep controls consistent across streaming, continuation cards, and thread-footer refreshes with a bounded ephemeral Router cache; legacy peers remain compatible."},{"version":"1.6.136","text":"### 委派成果自动收尾\n- 主 Agent 回复完成前,自动检查子任务成果是否已交付或明确保留;有遗漏会继续处理,最多补两轮。\n- 仍无法处理的成果会明确列出并保留,不再把“任务执行完了”当作“代码已交付”,也不会自动丢弃文件。","changes":[{"topic":"delegation","title":"委派任务","text":"主 Agent 回复完成前,自动检查子任务成果是否已交付或明确保留;有遗漏会继续处理,最多补两轮。"},{"topic":"delegation","title":"委派任务","text":"仍无法处理的成果会明确列出并保留,不再把“任务执行完了”当作“代码已交付”,也不会自动丢弃文件。"}],"details":"### Added\n- Enforce artifact closeout before successful coordinator completion. Drain accepted tasks and tool calls, reconcile historical delivery under existing ownership guards, then inspect durable receipts rather than cached results. Pending changes, missing or invalid receipts, failed collection, and unretained recovery state prevent success; verified no-change, applied, and deliberately retained outcomes need no further decision.\n- Resume the same coordinator session for at most two artifact-closeout rounds per request, combining unread worker results when available. Preserve attachments, result acknowledgement, approval/input, model recovery, and cancellation boundaries; new workers do not reset the budget. An unresolved final check returns bounded task IDs and artifact references as a failure, pausing queued execution while preserving recoverable output. No new wire messages, implicit merging, automatic cross-request replay, or non-Git lifecycle changes."},{"version":"1.6.135","text":"### 工作区自动回收\n- 无文件改动的成功任务,以及已确认合并的成果,会自动回收安全的 Worker 工作目录;保留上下文,下次在原路径重建并读取最新代码。\n- 有未交付成果、遗留文件或状态不明的工作目录继续保留;清理失败不影响任务结果,也不会强删文件。\n- 成果提交已进入主工作分支历史时,会自动确认交付;之后主分支撤回改动也不会重新挂起旧任务,遗留文件仍受安全检查保护。","changes":[{"topic":"delegation","title":"委派任务","text":"无文件改动的成功任务,以及已确认合并的成果,会自动回收安全的 Worker 工作目录;保留上下文,下次在原路径重建并读取最新代码。"},{"topic":"delegation","title":"委派任务","text":"有未交付成果、遗留文件或状态不明的工作目录继续保留;清理失败不影响任务结果,也不会强删文件。"},{"topic":"delegation","title":"委派任务","text":"成果提交已进入主工作分支历史时,会自动确认交付;之后主分支撤回改动也不会重新挂起旧任务,遗留文件仍受安全检查保护。"}],"details":"### Added\n- Automatically reclaim verified delegated Git checkout directories after successful no-change tasks or durable artifact application. Preserve native conversation pointers, stable lane paths, immutable artifacts, and private input/output/history references; recreate absent, unregistered owned paths from fresh delivery input when the lane is reused.\n- Persist present/reclaiming/reclaimed checkout state and exact output receipts. Resolve interrupted intents only from verified intact checkouts or confirmed absent/unregistered paths; never infer ownership from a missing legacy directory, overwrite occupied reclaimed paths, prune registrations, or sweep historical workspaces.\n- Recognize successful pending worker outcomes as historically delivered when their recorded artifact snapshot commit is an ancestor of delivery HEAD, including after a later revert. Persist the observed HEAD and repair interrupted pending-marker clears; reconcile guarded inspection, ready-lane admission, and idle turn closure without content-subset heuristics, automatic merges, staging, commits, or changes to patch-only apply. Keep replacement-object bypass, owner/ref checks, fail-soft errors, and independent safe-reclamation verification.\n\n### Changed\n- Independently bound and hash actual tracked bytes, modes, and symlink targets before checkout deletion, accounting for ignored files, extra directories, unknown entries, and Git index flags. Preserve pending, retained, failed/cancelled, locked, or unresolved recovery workspaces. Transformed bytes that cannot be proven equivalent fail closed.\n- Serialize lane lifecycle and Git worktree metadata operations within the CLI process. Await optional reclamation outside the worker-stop deadline before marking a lane ready; cleanup failure does not change a successful task or artifact application. Native backend execution, non-Git FIFO scheduling, and Router protocol remain unchanged.\n- Keep full byte verification outside the shared repository guard so independent lanes can start during a slow audit. Isolate a reused Git lane whose checkout preparation fails without discarding its existing native context; preserve lazy recovery of valid interrupted-removal receipts."},{"version":"1.6.134","text":"### 本阶段更新汇总(1.6.90~1.6.133)\n- 默认开启多 Agent 委派;Git 项目最多 5 个 Worker 隔离并行,成果由主 Agent 确认合并,非 Git 目录仍串行。\n- 新增 DSH 后端,支持模型与 effort 切换、上下文续接,以及在 /status 中查询余额。\n- 支持接收最大 20 MiB 的文件,提取文本文件、文字型 PDF、DOCX 和 XLSX 内容;设备授权后,上传文件再发送处理指令即可。\n- 优化手机端的进度和结果展示,支持 Markdown 富文本;Worker 活动详情和后台任务结果默认折叠。\n- 主 Agent 和子 Agent 卡片底部都用小号灰字显示各自的模型与 effort,方便了解本次任务的执行配置。\n- 新增中文升级摘要与 Codex Reset 额度提醒;跨版本升级时按功能汇总变化,重启和升级后保留已确认送达的提醒记录。","changes":[{"topic":"delegation","title":"委派任务","text":"默认开启多 Agent 委派;Git 项目最多 5 个 Worker 隔离并行,成果由主 Agent 确认合并,非 Git 目录仍串行。"},{"topic":"dsh-backend","title":"DSH 后端","text":"新增 DSH 后端,支持模型与 effort 切换、上下文续接,以及在 /status 中查询余额。"},{"topic":"file-attachments","title":"文件附件","text":"支持接收最大 20 MiB 的文件,提取文本文件、文字型 PDF、DOCX 和 XLSX 内容;设备授权后,上传文件再发送处理指令即可。"},{"topic":"worker-cards","title":"任务卡片","text":"优化手机端的进度和结果展示,支持 Markdown 富文本;Worker 活动详情和后台任务结果默认折叠。"},{"topic":"execution-metadata","title":"执行信息","text":"主 Agent 和子 Agent 卡片底部都用小号灰字显示各自的模型与 effort,方便了解本次任务的执行配置。"},{"topic":"maintenance-notices","title":"更新与额度提醒","text":"新增中文升级摘要与 Codex Reset 额度提醒;跨版本升级时按功能汇总变化,重启和升级后保留已确认送达的提醒记录。"}],"details":"This stage summary consolidates confirmed source changes from 1.6.90 through 1.6.133, including Git-confirmed changes whose per-version notes were missing. It replaces the available entries in that range, not Git history, and is not a complete npm publication ledger. Version 1.6.134 reorganizes release documents, synchronizes package versions, and permits up to six summary bullets in build-time and bundled-artifact validation; backend execution and Router behavior are unchanged.\n\n### Added\n- Integrate DeepSeek Harness (DSH) through its native persistent ACP server, with model and reasoning-effort controls, cancellation, permission prompts, context reporting when available, and isolated coordinator/worker sessions. Keep native capability boundaries: images require advertised support, and unsupported interactive slash commands, plan mode, and elicitation do not fall back to another backend.\n- Preserve DSH session pointers across backend switches and restarts. Recover explicitly non-resumable sessions with an honest fresh-session notice; retain pointers on authentication, provider, network, rate-limit, timeout, or directory-mismatch failures. Summarize-then-reset compaction uses a private, durable handoff rather than claiming native transcript compaction, and refuses to summarize unavailable original context.\n- Show DSH official recharge and bonus wallet balances in `/status` when native account authentication makes them available. Retain native precision and currency, distinguish balances from token usage or plan quota, and use a short-lived account-query process without creating a model turn or changing the ACP conversation.\n- Receive file attachments up to 20 MiB through explicit device enrollment and a same-Router HTTPS download path. Transfer file bytes from Feishu to a private Router spool and CLI staging area; WebSocket messages contain only bounded references, hashes, sizes, and authorization metadata. Enforce authenticated device ownership, actual byte limits, hashes, deadlines, storage quotas, and explicit failure feedback without weakening legacy text/image support.\n- Extract bounded previews from text/code, CSV, JSON, YAML, textual PDF, DOCX main-body text, and XLSX cells, retaining page/sheet/cell provenance. Keep parsing off the control event loop, bound expanded archives and output, and never execute macros or formulas. OCR, protected documents, legacy Office formats, and general archive extraction remain unsupported; saved, parsed, partial, and unsupported outcomes stay distinct.\n- Stage files for a subsequent instruction or a reply to their status card, including instructions with images, rather than starting a model task on file upload alone. Pin queued attachments, bind references to the admitted device/thread/directory, expose `/files` and `/files clear`, and preserve active references during cleanup. Backend tools retain their normal permissions when reading original or preview paths outside the project.\n- Persist isolated delegated-worker lanes separately from direct backend sessions, retaining only each lane's own earlier delegated context. Reuse requires confirmed process exit and valid session state; directory changes invalidate the old workspace generation, and failed lane cleanup remains retryable rather than silently freeing uncertain ownership.\n- Accept multiple independent delegated tasks in one coordinator request, with individual cancellation, queued status, bounded queue waits, cumulative admission limits, and automatic collection of all results. Retain source-workspace ownership while the queue drains; queued work has no execution timestamp or progress card before it starts.\n- Run Git workers in reusable per-lane worktrees with bounded snapshots of staged, unstaged, and nonignored untracked input. Refresh every detached task checkout to an explicit baseline while preserving native lane identity. Non-Git directories use code-enforced FIFO serial scheduling and are never initialized as Git repositories implicitly; worktrees are not process sandboxes.\n- Preserve immutable worker artifacts under private Git references and expose revision-guarded inspection, integration, or retention. Preflight conflicts in a separate recovery worktree; applying changes never stages, commits, or pushes the delivery workspace. Pending artifacts or unknown dirty files block lane reuse. File application is not atomic: preserve before/target snapshots and a durable pending receipt for manual recovery after an incomplete apply, and validate captured tree limits after Git filters and both rename endpoints against the selected-directory scope.\n- Attach bounded execution-scoped model and reasoning-effort metadata to AI responses, terminal recovery, and each delegated worker's progress/results. Distinguish backend reports, configured selections, defaults, and unavailable values without extra model requests. Keep launch preferences stable, retain final worker snapshots before cleanup, and never substitute coordinator settings or attribute a model to an unstarted queued task.\n- Show compact gray model/effort notes below Completed on main replies and outside collapsed worker details. Preserve metadata through long-output splitting, thread-button refresh, and optional protocol-v1 fields, while legacy peers and local control commands retain their existing display.\n- Add standalone CLI upgrade notices with cumulative bundled notes, offline delivery, negotiated capabilities, and a silent baseline on first adoption. Advance notification progress only after acknowledged delivery, retain skipped-upgrade ranges, and keep maintenance cards separate from thread selection and task routing.\n- Add hourly, status-only Codex weekly-quota inspection and notification-only reminders using existing file-backed ChatGPT credentials. Do not send model prompts, create user threads, refresh credentials, or probe other backends. Missing/expired credentials, unsupported native APIs, and failed samples remain unavailable evidence; the experimental native token-handoff API is not a compatibility guarantee.\n\n### Changed\n- Enable managed delegation by default for new and existing threads with no saved preference; explicit off remains off through upgrades, context resets, backend switches, and restarts. Exposing delegation tools does not automatically launch workers.\n- Restrict managed delegation to a different backend without changing native backend subagent tools. Unrestricted coordinators launch unrestricted workers; sandboxed coordinators have no eligible cross-backend targets until policy translation is supported. Discovery and launch enforce the same policy.\n- Raise the shared starting/running worker limit from three to five. Git-backed requests can occupy five isolated execution slots; additional accepted tasks remain queued, non-Git requests still run one worker at a time, and the cumulative 12-task limit spans coordinator continuations without refunds for failures or cancellation.\n- Use real worker tool activity for liveness timeouts, with separate idle and tool-idle deadlines, rather than treating a quiet stdout stream as proof that a worker stalled. UI text and card heartbeats do not extend execution liveness.\n- Enrich the local CLI's Linux/macOS startup PATH with verified runtime and conventional installation directories, preserving inherited precedence. Use the same command resolution for startup checks, backend menus, delegation, and auxiliary queries, honor explicit executable overrides, and preserve ZCode's native empty-command discovery without falling back from a nonempty invalid override. Valid existing services do not need reinstallation; startup does not source shell profiles, install tools, or rewrite their service files.\n- Render nested/live worker activity and results as rich Markdown, with independent per-worker text, elapsed/tool activity, consistent icons, and compact mobile layouts. Keep detailed activity collapsed, separate result labels from worker Markdown, preserve stable update slots and card-wide table limits, and make the delegation status menu easier to scan.\n- Label standalone task notifications as Background task, retain their originating thread and task identity, collapse result/output-path details by default, and keep short failures visible. This presentation is separate from foreground replies and managed-worker cards.\n- Show thread/workspace headers on initial streaming and continuation cards before final completion, preserving reply provenance rather than waiting for the terminal card update.\n- Bundle concise Chinese user summaries alongside English technical details at build time. Validate matching nonempty current-version entries, one short heading and one to six single-line user bullets, stable feature tags/titles, and bounded package payloads; never fetch, translate, or summarize release notes with a model at runtime. Version 1.6.134 raises the per-release bullet limit from three to six while retaining the 2 KiB summary budget.\n- Aggregate the entire pending device-upgrade range by feature, removing exact duplicate items only. Keep available summaries and technical details collapsed and paged, report bounded-overview omissions, and preserve legacy-peer fallback, first-adoption silence, and protocol version 1. This release represents the consolidated 1.6.90-1.6.133 range with the 1.6.134 stage summary rather than reconstructing a per-device subset of those changes.\n- Use the title \"Codex Reset\" with a target emoji and \"Weekly quota reset: 100%\". Explain why to send Codex a normal task without verification or activation steps, remove the sampling-disclaimer footer and redundant Dismiss button, and retain passive validated legacy callbacks. Eligibility requires two roughly hourly zero-usage observations with approximately seven days remaining and a deadline that advances with the sampling interval; it is a snapshot heuristic, not confirmation of a provider reset or a guarantee that one request starts a usage window.\n\n### Fixed\n- Validate incomplete or incompatible tool parameters before specialized card formatting, using bounded text or no-parameters fallbacks without interrupting later tool events or task completion.\n- Retry confirmed Feishu Markdown-parser failures as literal text, preserve that mode on later updates and thread-button refreshes, and retain table-limit fallback without treating unrelated failures as parse errors.\n- Require successful recovery-notice delivery before acknowledging reuse of a surviving card, avoid duplicate notices within a recovery round, and retain originating thread information through recovery and continuation cards.\n- Reset every backend's remote-cli session binding when a thread changes to a different normalized working directory, preserve backend-native history and thread preferences, and keep a same-directory selection a no-op.\n- Distinguish a deleted or inaccessible selected working directory from a missing backend executable, refuse fallback execution in another directory, and cover remaining executor and passthrough startup paths with actionable errors.\n- Refresh Codex's model catalog and idle app-server after a native CLI version change while preserving the conversation binding, and improve model-recovery card delivery without replaying accepted worker launches.\n- Retain bounded worker results through coordinator continuations and terminal failures without replaying the original request, attachments, or completed workers. Keep execution-scoped result acknowledgement separate from worker completion, suppress premature coordinator output while results are pending, and prevent stale worker progress from overwriting unrelated cards.\n- Deduplicate ACP tool updates and keep reasoning/thought chunks out of answer text, final output, and delegated summaries for Kimi, OpenCode, ZCode, and DSH, while preserving separate native reasoning handling. Generate unique, paired Pi fallback tool IDs so concurrent tool calls cannot collide or report an unrelated result.\n- Filter bounded standalone Claude Code model-recognition stderr diagnostics for SDK queries and session-title generation, including delegated-worker streaming/results and slash-command error details. Preserve actual API/authentication errors, nonzero exits, assistant text, unknown sources, malformed records, and other backends; raw local stderr and telemetry behavior are unchanged.\n- Refuse ambiguous plain-text input when multiple workers are waiting, retain request-specific approval routing, and require confirmed cleanup before releasing occupied slots or workspace ownership.\n- Keep queued diagnostic records out of live terminal pruning, reconcile unfinished records as interrupted after restart without replaying tasks, and make retained worker-lane cleanup retryable.\n- Persist acknowledged Codex reminder suppression across CLI upgrades, restarts, reconnects, and credential refreshes using a private account/bucket fingerprint ledger. Only valid non-candidate observations rearm reminders; unavailable probes do not. Wait for accepted acknowledgement writes on shutdown, preserve corrupt/unavailable storage without affecting normal messaging, and do not claim exactly-once delivery across crashes.\n\n### Security\n- Disable DSH's official extra session-log attachment and OTel telemetry paths independently with a private temporary configuration overlay and the native telemetry-disable flag. Leave existing profiles, credentials, and other backends untouched and remove the overlay after process exit. Normal model requests still send task context to the selected provider and native local history remains; this is not an offline mode or a guarantee about third-party plugins.\n\n### Maintenance\n- Require staged-change and outgoing-commit privacy checks before publication, and sanitize documentation references without changing functional behavior.\n- Remove redundant presentation/fixture assertions while retaining behavioral regression coverage, clean temporary test fixtures reliably, and make ZCode discovery assertions portable across aliased filesystem paths."}]}
|