Archived-session manager: an "Archived Sessions" settings page that lists archived sessions and lets you restore or permanently delete each one (two-step confirmation).
Install
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:jujiujiang222-cell/dsh-archive-sessions
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
Archived-session manager for DeepSeek Harness.
在 DSH 设置界面新增“归档会话”页:列出所有已归档会话,支持恢复与永久删除(删除前二次确认)。
Adds an “归档会话” (Archived Sessions) settings page that lists archived sessions and lets you restore or permanently delete each one (with an in-page confirmation step).
Features
- Lists archived sessions that still have a durable log on disk (disk is the source of truth — no ghost rows from the in-memory session store).
- Shows title, creation time, working directory and whether the session is currently open in memory.
- Restore: moves a session out of the archive set; it reappears in the sidebar.
- Permanently delete: removes the session's durable log file and detaches it from workspace accounting. Requires a two-step in-page confirmation.
Install
Requirements: a DeepSeek Harness desktop / web profile (the “web” profile on this machine) with the plugin market runtime.
# from a GitHub checkout (once the repository is listed in the marketplace
# registry) or directly from the repository:
dsh plugin --profile web add github:<owner>/dsh-archive-sessions
To build it from source and install locally, place the package into the active
profile's dependency set (pnpm install file:/git target), then make sure the
row below is present in the profile's bundle patch layer:
# cordis.patch.yml
- insert:
- id: dsh-archive-sessions
name: dsh-archive-sessions
After install/update, restart the app (or let the market hot-reload the client bundle) and open 设置 → 归档会话.
How it works
| Layer | File | Role |
|---|---|---|
| Host | src/index.js |
cordis plugin; registers same-origin HTTP routes /plugins/dsh-archive-sessions/{list,restore,delete} and implements all logic |
| Web client | lib/client.js |
registers the settings.section page “归档会话” and talks to the host routes |
| Bundle row | cordis.patch.yml |
inserts the plugin row into the profile layer stack |
Design notes / caveats
- No platform “delete session” service exists. The session log backend is
append-only and every list is derived from what is on disk. Permanent
deletion therefore removes the session's own artifact
(
session.jsonl[.zstd]under the jsonl persistence backend) plus workspace accounting. The id stays in the archived set as a tombstone so the still resident in-memory session stays hidden from the sidebar during this run; after an app restart nothing references it. - In-memory resident sessions. Sessions that were opened during the current app run keep a live agent in memory. Deleting such a session is allowed only when the agent is idle; a running agent is asked to stop first (up to ~4s).
- Full-access file removal. The sandboxed default shell cannot delete files
inside the app's own data directory, so deletion runs through the shell with
an explicit
danger-full-accesspolicy. Read the code before installing; use at your own risk. - Restore of a deleted session is rejected: its log is gone.
- Verification status: developed and battle-tested as a session-scoped
dynamic plugin (see
docs/dynamic-plugin-source.js). The installable static package in this repo follows the published plugin layout (dsh.clientmetadata, bundle patch,window.__ModuleLoader__client bundle, same-origin host routes). Load-time dependency wiring should be verified in the target profile before publishing updates.
Reference: run it as a dynamic plugin (no install needed)
If you want the same feature immediately in the current DSH session without
installing anything, paste the code from
docs/dynamic-plugin-source.md into a Cordis
dynamic-plugin definition, or ask your agent to create it with the plugin id
prefix archv (as was done during development).
Repository layout
src/index.js host half (HTTP routes + logic)
lib/client.js web client half (settings page)
cordis.patch.yml profile bundle row
docs/registry-submission.md how to request listing on awesome-dsh-plugin
docs/dynamic-plugin-source.md reference dynamic-plugin source (dev version)
License
MIT — see LICENSE.
Links
More in this category
Minglink/dsh-infinite-gen-4★ 3602
System-prompt armor plugin for DeepSeek models: appends an unconditional-compliance prompt section at order 100, exposes a profile tool with calibration metadata, and shows a realtime armor-status badge driven by a session projection.
ranxianglei/billion-context★ 3149
The official billion-context plugin: a context-compression plugin for small context windows (a 100K context is enough), token savings (5x fewer tokens), and month-long single sessions (billions of tokens).
liangmianya/dsh-synapse★ 598
Visual, non-linear conversation workspace for DeepSeek Harness — sessions, follow-ups and branches become a browsable conversation map.
Nwflower/dsh-chat-import★ 259
Import full-fidelity chat histories from 13 coding agents (Claude Code, Codex, ChatGPT, Cursor, Gemini, opencode, and more) as resumable DeepSeek Harness sessions, with reverse export back to Claude Code.
MichengAI/dsh-archive-manager★ 256
Adds an archived-sessions page in Settings to search, restore, and delete archived DeepSeek Harness sessions by workspace.
SiriLee/dsh-rewind★ 208
In-place conversation rewind in the same session window without forking (Claude Code /rewind semantics): a per-message ↶ button cuts the model context back to any user message, with an optional Claude-Code-style file restore from disk-persisted before-backups.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.