dsh-delete-session

DeepSeek Harness 会话删除插件 —— 在侧边栏会话菜单里直接删除会话。 给 DeepSeek Harness (dsh) Web 侧边栏的会话 ... 菜单（重命名 / 分叉 / 归档）补上「删除会话」：确认一次后可直接删除，真正删除会话日志、工作区记账与宿主内存中的会话状态。

中文 · English

中文

为什么需要它

DSH 侧边栏的会话菜单只有重命名 / 分叉 / 归档——归档只是把会话藏起来，不删数据；而插件dsh-web里的全家桶里的「会话归档管理」在设置深处，删一个会话要跳好几个界面。

这个插件把「删除」放回你最常点的位置：会话行的 ... 菜单。

特性

• 菜单内删除 —— 侧边栏会话 ... 菜单直接多出「删除会话」；会话 ID 从菜单的 React fiber 读取，永远作用于你点的那一行，不会切换当前会话
• 风险确认 —— 首次删除弹出确认对话框：显示会话标题与 ID，勾选「我已了解，永久删除」后确认按钮才可用
• 确认一次后可跳过 —— 对话框里勾选「不再询问，以后直接删除」，之后点菜单项直接删除（左下角 toast 提示）；按住 Shift 点击可临时恢复弹窗；清除 localStorage['dsh-delete-session:skip-confirm'] 可永久恢复
• 多选批量删除 —— 会话菜单里的「多选」进入选择模式：每行左侧出现勾选圈，点整行即勾选（不会打开会话），底部操作条显示「已选 N 个 / 取消 / 删除」；点删除立即批量执行（无确认弹窗、无全选、所有行都可选）：被选中的行乐观隐藏、操作条实时显示「正在删除 x/N…」、客户端以 6 路并发请求宿主（不同会话并行、工作区记账串行），完成后 toast 汇总并刷新列表；失败的行立即恢复显示并保持选中，方便直接重试；Esc 或「取消」退出
• 真正的删除 —— 停止运行中的 agent（cancel + 等待空闲）→ flush / detach 活跃会话 → 删除磁盘会话目录（原始 ID 与 session- 前缀两种写法）→ 持久化服务复核 → 清理工作区记账，侧栏不会残留「未分组」孤儿，并连带清理项目缓存行（$DSH_HOME/storages/*/sessions/<id>.json），不留无法再显示的幽灵记录
• 删除后回到新会话 —— 若删除的正是当前打开的会话，自动切到一个全新会话（不再落到已不可用的邻居页——那种页面 composer 会被禁用、侧栏也列不出来，看起来像「没删掉」）
• 默认安全 —— 宿主路由仅限本机回环（回环 socket + 回环 Host 头 + 同源校验）；被 DSH 打开占用的会话会被明确拒绝（409），绝不与活跃写者竞争
• 中英双语 —— 菜单项与对话框跟随 DSH 界面语言（zh / en）
• 零依赖 —— 不引入任何 DSH SDK，所有服务（sessions / sessionPersistence / agents / workspaceRegistry / webServer）都在调用时通过 cordis 上下文获取

安装

npm（推荐）：

dsh plugin --profile web add dsh-delete-session

或从 GitHub 仓库直接安装：

dsh plugin --profile web add github:DDDMUC/dsh-delete-session

重启 dsh web 后生效。

使用

1. 把鼠标移到侧边栏的会话行，点 ...（会话操作）
2. 选择底部的「删除会话」
3. 首次：勾选「我已了解，永久删除」（想省事可同时勾选「不再询问，以后直接删除」）→ 点「删除」
4. 之后：直接删除，左下角出现 toast 提示
5. 批量删除：会话菜单 →「多选」→ 勾选多个会话 → 底部「删除」；Esc 或「取消」退出选择模式

工作原理

• src/index.js（宿主）：注册一条仅限回环的路由 POST /dsh-delete-session/delete { sessionId }，执行删除链路
• src/client.js（浏览器）：经典客户端 bundle——监听 portal 到 body 的会话菜单（body > [role="menu"]），沿 React fiber 链读取会话节点（props.node.id），克隆原生菜单行保持样式，弹出确认对话框
• 删除链路：停 agent → flush / detach 活跃会话 → 写所有权探测（被占用 → 409）→ 删除目录（两种 ID 写法 + 复核）→ 清理工作区记账

测试

• test/checkbox.dom.test.js —— 勾选框回归测试（node --test，零依赖）：把真实的 src/client.js 跑在一个可读的 DOM 实现上，只经由用户真正会碰的入口（注入的会话菜单项、插件自己生成的 DOM）驱动，断言 「存在 .dsdel-check ⟺ 多选模式开启」
• 覆盖的回归：单条删除（deleteNow / 对话框确认）会调用 scheduleDecorate()，而 v0.1.8 之前 decorateRows() 无条件给每一行插入勾选框，于是删掉一个会话后所有行都长出了圆勾选框、底部操作条却仍然隐藏——一个「半开」的多选状态
• 这个测试是有意义的，不是空跑：把 decorateRows() 改回旧写法时其中 5 项会失败；改成「永不插入勾选框」时另有 4 项会失败
• 运行：npm test
• 尚未验证的一环（诚实说明）：与真实 DSH 界面的耦合——真实 DOM 结构、真实 CSS 布局、以及 React 调和器在重渲染会话行时是否会丢弃注入的勾选框——只能由真实浏览器验证。上述测试覆盖的是插件的点击与装饰状态机本身

已知限制

• 被 DSH 当前打开占用的会话：删除会自动等待写所有权释放（通常几秒）后完成；极少数仍被占用的情况会提示稍后重试或重启 DSH
• 菜单注入是 DOM shim：核心 UI 若调整菜单结构或行 fiber 形状，可能不再注入菜单项（不影响其他功能）
• 删除不可恢复：没有回收站，也没有撤销
• 批量删除为客户端 6 路并发 + 乐观隐藏：不同会话并行删除，宿主端写所有权等待缩短为 200ms × 12（单条最长约 2.2s），多个被占用的会话也并行等待；同一工作区记账变更仍串行，避免并发写交错

兼容性

• DSH 0.1.5-rc.1 / 0.1.7-alpha.2 实测通过（0.1.7 起不再导出 SettingsProvider；本插件不依赖 DSH SDK，无需改动）
• 宿主链路对缺少服务的旧版本会退化为纯文件系统清理

如果这个插件帮到了你，欢迎给仓库点个 ⭐（GitHub）——星标是开发者继续维护的最大动力，感谢支持！

License

MIT

English

Why you need it

The DSH sidebar session menu only offers Rename / Fork / Archive — archive merely hides a session and keeps every byte on disk, while the session archive manager inside the dsh-web plugin suite lives deep in Settings and takes several screens to reach.

This plugin puts Delete back where you already click: the session row's ... menu.

Features

• Delete from the menu — a "Delete session" row appears in the sidebar session ... menu; the session id is read from the menu's React fiber, so the action always targets the row you clicked and never switches the active conversation
• Risk consent — the first delete opens a confirmation dialog with the session title and id; the confirm button unlocks only after ticking "I understand"
• Confirm once, then skip — tick "Don't ask again" and later deletes run directly from the menu (a toast reports the result); hold Shift while clicking to force the dialog back, or clear localStorage['dsh-delete-session:skip-confirm'] to restore it permanently
• Multi-select batch delete — "Select multiple" in the session menu enters selection mode: every row gets a round checkbox, clicking a row toggles it (it never opens the conversation), and a bottom bar shows "N selected / Cancel / Delete". Delete runs immediately (no confirm dialog, no select-all, every row selectable): selected rows are hidden optimistically, the bar shows live progress ("Deleting x/N..."), and the client runs 6 concurrent requests (independent sessions in parallel, workspace accounting serialized), then reports a toast summary; failed rows reappear immediately and stay selected for a quick retry; Esc or Cancel exits
• Real deletion — stops a running agent (cancel + quiescence), flushes and detaches the live session, removes the on-disk session directories (both the raw and session- prefixed id), verifies through the persistence service, then cleans workspace accounting so no orphan shows up under "Ungrouped", and removes the session's projection-cache rows ($DSH_HOME/storages/*/sessions/<id>.json) so no ghost the sidebar can no longer show is left behind
• Leaves a fresh session behind — when the deleted session is the one the main view is showing, the app switches to a brand-new session instead of a stale neighbour (an unavailable row with a disabled composer that the sidebar cannot even list, which reads as "the delete did not work")
• Safe by default — the host route is loopback-only (loopback socket, loopback Host header, same-origin check); a session still held open by DSH is refused with 409 instead of racing the active writer
• Bilingual — the menu item and dialog follow the DSH interface language (zh / en)
• Zero dependencies — no DSH SDK imports; every service (sessions, sessionPersistence, agents, workspaceRegistry, webServer) is resolved through the cordis context at call time

Install

From npm (recommended):

dsh plugin --profile web add dsh-delete-session

Or straight from the GitHub repository:

dsh plugin --profile web add github:DDDMUC/dsh-delete-session

Restart dsh web to apply.

Usage

1. Hover a session row in the sidebar and click ... (session actions)
2. Pick "Delete session" at the bottom
3. First time: tick "I understand - delete permanently" (tick "Don't ask again" too if you like) and confirm
4. Afterwards: the session is deleted directly, with a toast
5. Batch delete: session menu -> "Select multiple" -> tick rows -> "Delete" in the bottom bar; Esc or Cancel exits

How it works

• src/index.js (host): one loopback-only route POST /dsh-delete-session/delete { sessionId } runs the deletion pipeline
• src/client.js (browser): a classic client bundle — watches for the portalled session menu (body > [role="menu"]), walks the React fiber chain to the session node (props.node.id), clones a native menu row for styling, and opens the confirmation dialog
• Pipeline: stop agent → flush / detach live session → write-lease probe (busy → 409) → remove directories (both id spellings + verification) → clean workspace accounting

Tests

• test/checkbox.dom.test.js — the multi-select checkbox regression test (node --test, zero dependencies): it runs the real src/client.js against a readable DOM implementation and drives it only through surfaces a user touches (the injected session-menu items and the DOM the plugin builds), asserting that a .dsdel-check exists if and only if multi-select is on
• The regression it covers: a plain single delete (deleteNow / the dialog's confirm handler) calls scheduleDecorate(), and before v0.1.8 decorateRows() planted a checkbox on every row unconditionally — so after deleting one session every row grew a round checkbox while the batch bar stayed hidden, a "half-on" multi-select state
• The test earns its keep: reverting decorateRows() to the old shape fails 5 of its cases, and a fix that never plants checkboxes fails 4
• Run it with npm test
• Not verified (honest note): the coupling to the real DSH UI — real DOM structure, real CSS layout, and whether React's reconciler drops injected checkboxes when it re-renders a session row — can only be checked in a real browser. What these tests cover is the plugin's own click and decoration state machine

Known limitations

• A session DSH currently holds open: the delete waits for the write lease to be released (usually a few seconds) and then completes; in the rare case it stays busy, the dialog asks you to retry later or restart DSH
• The menu injection is a DOM shim: core UI changes to the menu markup or row fiber shape may stop the item from being injected (nothing else breaks)
• Deletion is permanent: there is no trash bin and no undo
• Batch delete uses 6-way client concurrency with optimistic hiding: independent sessions delete in parallel and the host write-lease wait is shortened to 200ms x 12 (max ~2.2s per item), so busy sessions wait in parallel too; workspace accounting stays serialized so concurrent deletions never interleave on the same store

Compatibility

• Tested on DSH 0.1.5-rc.1 and 0.1.7-alpha.2
• On older versions without the services, the host pipeline degrades to filesystem cleanup

If this plugin has been helpful, a ⭐ on GitHub would mean a lot — it is the biggest motivation for the developer to keep maintaining it. Thank you!

License

MIT