jujiujiang222-cell/dsh-archive-sessions

dsh-archive-sessions is a session-archiving management plugin built specifically for DeepSeek Harness (DSH). It adds an "Archived Sessions" (归档会话) page to the DSH settings panel, listing every archived session whose durable log still exists on disk and exposing two operator actions: restore and permanent delete (the latter gated by an in-page two-step confirmation). The package follows the published DSH plugin layout, with src/index.js acting as the cordis host that registers same-origin HTTP routes /plugins/dsh-archive-sessions/{list,restore,delete}, and lib/client.js acting as the web-client half that registers the settings.section page. The bundle row is supplied via cordis.patch.yml, which inserts the plugin into the active profile's patch layer stack; installation is triggered with dsh plugin --profile web add github:<owner>/dsh-archive-sessions, or by adding the package via pnpm as a file: or git target and then ensuring the patch row is present.

Typical workflow: after archiving several sessions inside DSH, the user opens Settings → Archived Sessions to review a table containing the session title, creation time, working directory, and a flag indicating whether the session is currently resident in memory. Sessions that should be revived are restored, which moves them back out of the archive set so they reappear in the sidebar; sessions that are no longer wanted are permanently deleted, which removes the underlying session.jsonl[.zstd] artifact under the jsonl persistence backend and detaches the id from workspace accounting. The id is retained as an in-memory tombstone so a still-resident session hides from the sidebar until the next restart, and if a target session is in memory the host waits up to roughly four seconds for its agent to become idle before proceeding. The plugin is aimed at desktop power users who need to govern long-running DSH session archives and reclaim disk space from obsolete logs.

Dependencies and operational notes: the runtime is a DSH desktop or web profile that has the plugin market enabled (the README was authored against the local web profile), and installation requires pnpm plus a cordis.patch.yml bundle row. The host is implemented as a cordis plugin that talks to the app shell, while the web client uses the standard window.__ModuleLoader__ bundle metadata with dsh.client keys; a registry submission guide in docs/registry-submission.md explains how to request listing on awesome-dsh-plugin. Important caveats apply: deletion removes files inside DSH's own data directory, so the host invokes the shell under an explicit danger-full-access policy — review the source before installing and use at your own risk. A deleted session cannot be restored because its log is gone; load-time dependency wiring should be re-verified inside the target profile before publishing updates, and after install the app should be restarted or the client bundle hot-reloaded so the new settings page becomes visible.