@dshwp/dsh-session-manager
DeepSeek Harness Web UI 的会话管理器：从设置面板浏览所有会话、归档 / 取消归档（恢复）/ 删除会话，以及预览对话内容。· DSH 会话管理：设置页查看全部与已归档会话，归档 / 恢复 / 删除 / 内容预览。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:wuxiangru915/dsh-session-manager#902bae8ea3e8fdd7fc7be40bc0d04ea8b4571f6f
Session Manager 以 @dshwp/dsh-session-manager 发布，当前版本为 0.1.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Session manager for DeepSeek Harness.
dsh-session-manager gives the Harness Web UI a full session-management surface: browse all sessions and the archived ones, restore (unarchive) archived sessions back to their original workspace, archive any session, delete sessions with a two-step confirmation, and preview conversation content — all from the Settings panel, with zero modification to official packages.
Stock DSH archives sessions one-way: the sidebar's Archive action hides a session from every view (workspace groups, ungrouped, search, flat list), and there is no view or API to bring it back — archived sessions are effectively lost until you hand-edit ~/.dsh/storages/workspace.json. This plugin makes archiving a reversible, manageable state and adds an overview of every session on disk:
right-click a session -> Archive (stock DSH)
-> the session vanishes from the sidebar (nowhere to see it again)
-> this plugin: Settings -> Session manager -> archived tab
preview its content, Restore it (back to its original workspace
position), or Delete it from disk (two-step confirmation)
-> the all-sessions tab lists every persisted session (grouped by
workspace, ungrouped ones included) so nothing is ever lost sight of
dsh.bundle patch layer); every operation goes through official services (workspaceRegistry, sessionPersistence, sessionQuery, fs, shell, …) — no official package is patched or overridden./dsh-sm/* routes reject non-loopback hosts and cross-origin requests (Host + Origin / Sec-Fetch-Site fence).# one line, from a git source
dsh plugin --profile web add github:omdsh-dev/dsh-session-manager
# restart the web server, then hard-refresh the page
Local development:
dsh plugin --profile web add /path/to/dsh-session-manager
The repository ships plain-JS lib/ artifacts with no build step, so git-source installs work without any build tooling on the user's machine.
Session manager (settings page)
Open Settings → Session manager:
—), status badges for archived / live / running. Actions: Archive, Delete, and Delete all (two-step; skips running/open sessions).lib/
├── index.js Host half: cordis plugin (injects webServer) exposing POST /dsh-sm/* routes
└── client.js Browser half: __ModuleLoader__ bundle registering the Settings section
cordis.patch.yml dsh.bundle patch layer — one insert row drives both halves
browser (Settings page) --POST /dsh-sm/*--> host handlers
archived/list · archived/unarchive · sessions/list · sessions/archive
· sessions/delete · sessions/detail
workspaceRegistry (archive-set read/write) + sessionPersistence (headers/locate)
+ sessionQuery (titles/content) + fs/shell (size/delete) + agents (running guard)
Host routes:
| Route | Payload | Returns |
|---|---|---|
POST /dsh-sm/archived/list | {} | { items, totalBytes } |
POST /dsh-sm/archived/unarchive | { sessionId } | { ok, changed, archivedSessionIds } |
POST /dsh-sm/sessions/list | {} | { items } |
POST /dsh-sm/sessions/archive | { sessionId } | { ok, archivedSessionIds } |
POST /dsh-sm/sessions/delete | { sessionId } | { ok, deleted, sessionId, path?, reason? } |
POST /dsh-sm/sessions/detail | { sessionId } | { id, createdAt, cwd, totalEvents, messageCount, truncated, messages } |
The unarchive path rewrites the durable archive set through workspaceRegistry.setState (with a workspace storage-domain fallback), so the registry's in-memory state and the on-disk global.archivedSessionIds stay consistent; the client refreshes the workspace/session stores afterwards so the sidebar updates immediately.
node test/smoke.mjs # 10 host-logic checks against stub services
The smoke test drives apply(ctx) with stub services and covers the route wiring, the loopback/origin fence, archive-set read/write, delete bookkeeping and detail extraction. End-to-end verification was performed against a real profile (a second instance on a separate port plus a browser walkthrough of restore / archive / delete-all).