dsh-session-manager

A DeepSeek Harness plugin that manages archived sessions. The official workspace browser only has an "archive session" action — archived sessions then disappear from every view, with no way to list, restore, or permanently delete them. This plugin fills that gap and adds a red Delete permanently item to the session context menu.

中文文档

Features

1. Settings page: Settings → Session Manager

• Lists every archived session: title, owning workspace, project directory, update time, running state
• Restore (returns to its pre-archive position) and red Delete permanently per session
• Select all + bulk delete: tick rows (or the header checkbox) and delete every selected session in one confirmed action. The run is serial and tolerant: a failing session is reported in full while the rest still go through, sessions with a running task are skipped (the dialog says how many before you commit), and the per-run result is one summary — clean, partially failed, or all-running refused
• Destructive confirm dialog — every delete is a direct physical delete, there is no backup layer
• Backed by the official session / workspace client stores — fully reactive

2. Session context menu: red "Delete permanently"

Hover a session row in the left sidebar → ⋯ menu: below the built-in Rename / Fork session / Archive session items, a red Delete permanently item appears (native danger styling, same confirm dialog).

The official workspace browser exposes no slot for session menus, so the plugin augments the rendered popup via DOM observation + React-fiber resolution. The augmentation is passive: if the host UI structure changes and resolution fails, the button simply does not appear — nothing else is affected.

3. Agent tools

Tool	Notes
session_list_archived	List archived sessions as JSON
session_restore_archived	Restore by id (reversible, no confirmation)
session_delete_permanently	Delete by id; requires confirm: true; refuses running sessions

Install

git clone https://github.com/SunshineR04/dsh-session-manager.git
dsh plugin --profile <name> add "file:/path/to/dsh-session-manager"

dsh plugin add installs through pnpm and appends the package to dsh.profile.bundles; this package's cordis.patch.yml bundle layer mounts the plugin row automatically. Restart the dsh desktop app afterwards (new bundles are not hot-loaded).

Alternatively mount it manually in the profile's cordis.patch.yml (the bundle channel above is easier):

- insert:
    - id: session-manager
      name: dsh-session-manager

Delete semantics

Deleting runs in this order:

1. Open sessions only: a persistent pending-deletion marker is written before any mutation (crash safety — a crash mid-delete always leaves the next boot a marker to sweep), right after the read-only existence check; malformed ids read back from that queue file are pattern-validated before any filesystem use.
2. Registry bookkeeping (durable + broadcast): detaches the id from its workspace's sessionIds and removes it from the global archive set. The detach does not trust the workspace's filtered sessionIds view alone — a stale registry header index can hide the id from that getter (which used to let deleted sessions survive, resurfacing as ungrouped entries), so the raw workspace record is checked as a fallback.
3. Removes the session artifact directory ~/.dsh/sessions/<encoded-project>/<session-id>/ (session.jsonl.zstd). The directory is resolved through three seams in turn — registry header + persistence locate, the persistence header listing, then a raw scan of the sessions root for a directory named exactly the session id — so a degenerated header seam can no longer silently skip the deletion.
4. Removes the metadata checkpoint ~/.dsh/storages/session_projcache/sessions/<id>.json (and .bak-*).
5. Broadcasts the official api-session/removed event, so every connected client drops the session from its list store immediately. (The host itself only emits this event when a live session is disposed, which a cold delete never is.)

The SQLite search index reconciles itself once the source files are gone; attachments are content-addressed and intentionally kept.

• Every delete is a direct physical deletion — there is no backup layer, so double-check the confirm dialog.
• Deleting an open session works immediately: its registry accounting, files and metadata are removed at once (post-delete flushes cannot recreate anything — appends open the log by path and never recreate a deleted directory). Because dsh has no public "close session" API, the in-memory copy lingers (and still shows in that open view) until the owning UI scope dies; the id is kept in the archive set as a tombstone, so it is hidden from the workspace browser and every listing meanwhile, and the next dsh restart finishes the cleanup. Running sessions are still refused.
• Pending banner: the settings page lists only the sessions you can still act on. Entries with files on disk (e.g. a mid-delete crash leftover) get a row with Cancel deletion, which clears the tombstone as well (registry first, marker second, so a failure leaves the entry fully retryable). Entries whose files are already gone (the normal open-session delete) have nothing left to act on, so they collapse into a single "already deleted · clears after restart" summary line with an optional expander for their ids instead of occupying the banner — and canceling one is refused by the host too (session/data-gone), not just hidden by the UI.
• Restore only removes the id from the archive set — archiving keeps the workspace sessionIds slot, so the session returns to its previous position. A queued-for-deletion id is refused with session/pending (cancel it first when its files are still on disk); restoring one would expose an artifact-less husk.

Config

Field	Default	Description
sessionListLimit	500	Max entries per list call
allowDeleteRunning	false	Force-delete sessions with a running task (skips the refusal and the tombstone — dangerous; open-idle sessions delete immediately either way)
toolDeleteRequiresConfirm	true	Agent delete tool requires confirm: true
menuDeleteAvailable	true	Mount the red menu item

Develop

pnpm install
pnpm test   # syntax check + host unit tests + client render smoke tests

The render tests mount the real client settings section with React inside jsdom (test/client.render.test.mjs) — they catch UI crashes the host tests cannot see.

Browser E2E (optional)

Boots a throwaway dsh web instance against an isolated DSH_HOME (never your real data) and drives the UI with puppeteer-core + local Chrome:

cp scripts/e2e-seed.local.example.json scripts/e2e-seed.local.json
#    ^ fill in your own session/workspace data (gitignored, never committed)
node scripts/e2e-seed.mjs <e2e-home> ~/.dsh         # 1. seed the isolated test HOME
# 2. create a profile in that HOME with this plugin, then start the test web instance.
#    ⚠ The desktop `dsh` shim hardcodes DSH_HOME=<real home>, so prefixing the
#    command with DSH_HOME=<e2e-home> does NOT isolate (verified: the profile
#    lands in the real home). Invoke the CLI entry directly instead — verified
#    for `plugin add`; use the same form for the serve flags:
#      ELECTRON_RUN_AS_NODE=1 DSH_HOME=<e2e-home> "<DSH Desktop.exe>" --expose-internals \
#        "<app.asar>/lib/desktop-cli.js" plugin --profile sm-test add <tarball>
#      ELECTRON_RUN_AS_NODE=1 DSH_HOME=<e2e-home> "<DSH Desktop.exe>" --expose-internals \
#        "<app.asar>/lib/desktop-cli.js" --profile sm-test --port 43123 --no-open
node scripts/e2e-check.mjs <printed token URL>      # 3. read-only checks: menu item / settings page
node scripts/e2e-mutations.mjs <URL> <e2e-home>     # 4. closed loop: restore → archive → delete

References

Built after studying these projects (some locally inspectable under ~/.dsh/profiles/desktop/node_modules):

• omdsh-dev/DSH-better-sidebar — the community-plugin reference for bundle patches, client injection, settings-section registration and host routes
• ysr666/dsh-vision-router — the hand-written no-bundler client skeleton this package follows
• deepseek-ai/deepseek-harness — the host itself: workspace controller, session controller, jsonl persistence, workspace domain (archive-set semantics)
• koishijs/koishi — Cordis runtime upstream
• tmux-plugins/tmux-resurrect, opencode-ai/opencode — conceptual references for session save/restore/cleanup UX

License

MIT