DSH Plugin HubDSH 插件市场

Lzcdebear/dsh-delete-session

Desktop桌面端 Native原生 ⭐ 6 MIT Sessions & Context会话与上下文

Delete sessions, not archive them

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

dsh-session-delete is a native plugin built exclusively for DeepSeek Harness (DSH) desktop, packaged as a bundle-manifest bundle with no other agent platform in scope. It addresses a documented gap in DSH: the platform only archives conversations and ships no deletion API, leaving logs to accumulate under root indefinitely. The plugin injects a new "Delete conversation" entry into each session's ⋯ menu and splits into a Host half (host.js) plus a Client half (client.js), inserted through cordis.patch.yml into the profile layer stack. Styles use only --dsw-alias-* theme tokens, so light and dark both render correctly, and the UI is localized in English and Simplified Chinese.

The intended user is any long-lived DSH profile holder who wants true removal instead of hidden archive rows, including those running subagents, forks, or Agent Teams rosters. The workflow opens the ⋯ menu on a session row, picks Delete conversation, and receives a dialog that lists the whole family — one collapsible group per relation (subagent conversations, forked conversations) with per-descendant checkboxes carrying title, id tail, depth and an open/running badge — plus a "delete all" checkbox with an indeterminate state. On confirm, the Host removes the artifact directory, walks descendants breadth-first via SessionHeader.parentSession and subagentCatalog, detaches the workspace account, drops the projection checkpoint, closes owned terminals, and fires api-session/removed, so the rows disappear from the sidebar at once.

Dependencies rely entirely on DSH context services — ctx.sessionPersistence, ctx.subagents, ctx.terminals, ctx.webServer, and the workspace/session-activity waterfall gate — and the two same-origin exact routes reuse the dshmarket transport because a plain JavaScript bundle cannot declare a typed ctx.remote namespace. Hard limits are explicit: attachment blobs in ~/.dsh/attachments/v1/objects/<hash> survive because the content-addressed store has no reference counting, descendant deletes cap at 200 per request, and a name outside the family is refused with 400 unknown-descendant. Install via plugin_manager { action: "install_bundle" }; tests run with node --test test/host.test.mjs; license is MIT.

dsh-session-delete 是面向 DeepSeek Harness（DSH）桌面的原生插件，以 bundle-manifest 形式打包，仅针对 DSH 这一目标平台。它在每个会话的 ⋯ 菜单里新增"删除会话 / Delete conversation"项，弥补 DSH 仅支持归档、缺少真正删除 API 的缺口。安装通过 plugin_manager { action: "install_bundle" }，卸载则用同名 action；插件拆为 Host 半（host.js）与 Client 半（client.js），通过 cordis.patch.yml 挂入配置栈，UI 仅使用 --dsw-alias-* 主题令牌，深浅色皆可。

典型工作流：在侧栏任意会话上点开 ⋯ 菜单、选择 Delete conversation，弹层会列出整个会话家族——子代理会话、分叉会话各占一个可折叠分组，每行带标题、id 尾段与运行状态徽标，并有"delete all"半选复选框。确认后端到端移除：会话制品目录、子代日志、工作区账号记录、投影 checkpoint、关联终端，并向页面派发 api-session/removed，侧栏立即更新。运行中的工作会被阻止，并提供 Stop and delete，先触发 workspace/session-stop 再删除。

依赖上，插件依赖 DSH 的 ctx.sessionPersistence、ctx.subagents、ctx.terminals、ctx.webServer 及 workspace/session-activity 闸门；其 HTTP 路由采用 dshmarket 同款跨域闸门，强制回环 Host、同源 Origin 与 sec-fetch-site 限制。限制包括：附件 blob 因内容寻址共享、无引用计数而不会被清理；删除上限每请求 200 个后代。许可为 MIT。

View on GitHub在 GitHub 查看

Recommended强烈推荐 Send to your DSH发给你的 DSH 安装 
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-delete-session（Lzcdebear/dsh-delete-session）
仓库：https://github.com/Lzcdebear/dsh-delete-session
本站详情页：https://www.yhbd.top/plugins/lzcdebear-dsh-delete-session/
本站登记：类型 client · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 6 · 最近提交 2026-10-02 · 主语言 JavaScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 2 warnings2 项注意
  • Only 6 stars - very few users, little community feedback星标只有 6，几乎没人在用，遇到问题缺少社区反馈
  • Desktop client: installation downloads an executable - verify the publisher and checksums桌面客户端：安装会下载可执行文件，请核对发布者与校验和
DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

  • DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
  • External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
  • Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

  • Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
  • Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
  • curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
  • Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
  • Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
  • Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装 

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

把 Lzcdebear/dsh-delete-session 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

10.3 KB · 缓存于 2026-10-02 22:09:17 · 10.3 KB

dsh-session-delete

Delete a conversation from DeepSeek Harness — DSH ships archive only.

中文说明

Why this exists

DSH can only archive a conversation. Archiving hides the row from the sidebar and keeps every artifact: the log, the workspace account, the projection checkpoint all stay on disk, and the conversation can be restored at any time. The persistence seam has no deletion API at all — @deepseek-ai/dsh-session-persistence-jsonl states it plainly:

Nothing deletes session files — logs accumulate under root until removed externally; the seam has no deletion API.

So a long-lived profile accumulates conversations forever. This plugin adds the missing step: a Delete conversation row in each session's ⋯ menu that really removes the data.

What it deletes

For the chosen session, the Host half:

  1. removes the session's artifact directory — the current log, every retained historical format generation, and any session-local file in it (ctx.sessionPersistence.locate(header) gives the path);
  2. removes the descendants you selected — child sessions are sessions of their own with their own logs. DSH records every child in its parent's header (SessionHeader.parentSession), and writes that field for every relation it creates: the Subagent runtime sets it with origin: 'subagent', a fork sets it with isSeeded, and Agent Teams resolves its roster through the same field. The plugin walks that lineage breadth-first and unions it with the durable subagentCatalog projection (ctx.subagents.listDescendants), so a child whose own header no longer reads is still named. Descendants are deleted deepest first, gathered before anything is removed, and only the ticked ones go — up to 200 per request;
  3. drops the workspace account — the id leaves every Workspace record's sessionIds (Workspace.detachSession) and the registry-global archive and pin sets;
  4. drops the projection checkpoint — the session_projcache domain record and its <id>.json file;
  5. closes the shells the session owned — ctx.terminals are part of no admission family, and the service only reaps them when the Agent is released, which can be long after the log is gone;
  6. tells connected pages — one api-session/removed per removed id, the same event the shipped Session controller emits when a Session is disposed, so the rows leave the sidebar immediately.

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 Lzcdebear/dsh-delete-session 的 README.md。 在 GitHub 查看原文 →

Related相关推荐

← 上一个 Prev whale-notify 下一个 Next dsh-opencode-go-monitor →