dsh-archive-favorites-forge
为 DSH 对话增加收藏、复制 ID+路径、按会话删除、闲置批量归档和收藏筛选——在现有归档功能之上通过扩展槽实现，不修改任何官方文件。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-archive-favorites-forge@0.24.3
Archive Favorites Forge 以 dsh-archive-favorites-forge 发布，当前版本为 0.24.3。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Favourites, copy id+path, per-session delete, idle batch archive and a favourites filter for DeepSeek Harness conversations — additive slot extensions over the shipped archive feature. It edits no official file.
给 DSH 的对话加上收藏、复制 ID+路径、单条删除、超时批量归档和收藏筛选 —— 全部挂在官方插槽上，不改官方一行代码。
English | 简体中文
1. The conversation menu — favourite, copy id + path, and a guarded permanent delete, added as three rows to the shipped 「…」 menu:
2. The favourites filter — two extra rows in the official 筛选会话 group, narrowing the sidebar to favourites that are archived and to favourites that are not:
3. The settings panel — idle batch archive, the favourites list with archive state, and batch delete of archived conversations that are not favourites:
DSH already ships an archive feature: the Workspace registry keeps a global
archivedSessionIds set and @deepseek-ai/dsh-client-ui-workspace renders the
sidebar rows plus a view-options filter. That shipped feature has no
favourites, no per-conversation delete, no copy-id/path affordance, and no
time-based batch archive — and it deliberately refuses to open an archived
conversation.
This plugin adds those things by attaching to documented official slot points, so it composes with the shipped UI instead of patching it.
| 中文 | English | |
|---|---|---|
| ① | 收藏对话：归档或未归档的对话都能收藏；「…」菜单项 + 行内 ☆，星标即时生效 | Favourite any conversation — archived or not; a menu row plus an inline ☆ star, applied optimistically |
| ② | 复制 ID + 路径：「…」菜单一键复制会话 ID 与转录文件绝对路径（两行） | Copy id + path — one menu row copying the session id and the transcript's absolute path |
| ③ | 单条永久删除：任意非收藏对话可删，二次确认；删完侧栏立即移除该行 | Per-conversation permanent delete — any non-favourite, behind a confirmation, and the sidebar row disappears at once |
| ④ | 超时批量归档：把闲置超过 N 小时的未归档对话一次性归档，可撤回 | Idle batch archive — archives conversations quiet for more than N hours, undoable |
| ⑤ | 导出清单：制表符分隔的 txt，含对话名称 / 对话ID / 所属工作区 / 闲置时长 / 最后活动时间；可复制路径或直接打开所在文件夹 | Export list — a tab-separated txt with name, id, workspace, idle time and last-activity time; copy its path or reveal it in the file manager |
| ⑥ | 收藏筛选：视图选项菜单新增「仅显示收藏（已归档）」与「仅显示收藏（未归档）」 | Favourites filter — view-options rows for favourites that are archived, and favourites that are not |
| ⑦ | 批量删除：一键永久删除「已归档且未收藏」的对话 | Batch delete — permanently removes the archived-and-unfavourited conversations |
| ⑧ | 删除护栏：收藏项拒删、越出会话根目录拒删、符号链接拒删、逐条报告、批量上限 | Delete guardrails — favourites refused, paths outside the sessions root refused, symlinks refused, per-id reporting, batch cap |
| Feature | UI location |
|---|---|
| Favourite / copy / delete one conversation | Sidebar row 「…」 menu (and a hover ☆ on the row) |
| Idle batch archive, export list, favourites list, batch delete | Settings → 归档收藏 |
| Favourites filter | 视图选项 → 筛选会话 |
dsh plugin --profile <profile> add dsh-archive-favorites-forge
Then fully quit and reopen DSH. The host half (lib/index.js) has no
watcher in this harness generation, and the client bundle is snapshotted at
startup — so a page refresh alone does not pick up a new version.
lib/index.js host half — favourites store, transcript-path resolver,
JSON routes, guarded delete, archive/dearchive
lib/client.js client half — official slot registrations + one DOM rule
Slots used (all documented in the harness client contract):
| Slot | What it contributes |
|---|---|
sidebar.workspaces.session.menu.item | 3 rows: favourite, copy id+path, delete |
sidebar.workspaces.session.row.action | 1 hover ☆ star |
settings.section | the 归档收藏 page |
Every contribution is registered through ctx.slots.inject — the "register once
the owning entry is mounted" contract — so the plugin never assumes the sidebar
is up, and never holds a reference to a node the host owns.
The favourites filter is the one exception: the view-options menu is a plain
array with no slot and no trigger id, so that single control is added by
finding the official filter row in the DOM and cloning it. It keys on
role/aria/data-row-key attributes, never on the CSS-module hashes (which
are re-hashed on every build).
localStorageRenderer localStorage is origin-scoped: the desktop shell, a phone view and a
remote browser are different origins and would each keep their own stars. The
host half persists them to
~/.dsh/data/dsh-archive-favorites-forge/favorites.json
which survives a profile switch, a reinstall, and both ends.
There is no official session-delete RPC in this harness generation — the
shipped UI never deletes a session. "Delete this conversation" therefore means
removing the session's own artifact directory under ~/.dsh/sessions/. That is
irreversible, so the host applies these guards before it removes anything:
maxDeletePerCall.Each id is reported separately, so one failure never aborts the batch. After a
successful delete the host emits api-session/removed — the harness's own
row-removal event — so the sidebar drops the row immediately instead of showing
it until the next reload.
| Key | Default | Meaning |
|---|---|---|
enabled | true | Master switch for the host routes |
maxDeletePerCall | 500 | Hard cap on one delete request |
- id: dsh-archive-favorites-forge
config:
maxDeletePerCall: 200
session-<uuid>, but artifact
directories on an upgraded machine use both <uuid> and session-<uuid>.
Every comparison goes through a normaliser and the resolver tries both
spellings, so this works for old and new conversations alike.新会话 / 未命名).cwd) is never counted or
acted on.archiveSession / unarchiveSession methods, and never writes another
plugin's internals.lib/index.js host half
lib/client.js client half (a __ModuleLoader__ bundle)
test/probe-client.mjs DOM-stub + host probe suite
Run the suite:
node test/probe-client.mjs
The probe is not a formality — it has repeatedly caught bugs that a syntax check and a careful read both passed, including:
C--Users instead of C-Users, which
would have handed every "copy path" a nonexistent file;session- prefix;It asserts against the real directories and the real registry on the
machine, plus DOM fixtures that mirror the official markup exactly (including
the selection tick being a bare <svg> on the selected row only) — which is
what exposed each of those.
MIT.