DeepSeek Harness plugin

dsh-sessions-rm

Session management for DeepSeek Harness (DSH): list all historical sessions in a settings page and physically delete a session's log directory (with a type-to-confirm dialog and an audit trail).

Jump to install

Source facts

Repository
Temoa/dsh-sessions-rm
Latest update
Aug 17, 2026
Category
Memory
GitHub stars
0
Format
plugin
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-20

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/Temoa/dsh-sessions-rm
Plugin: dsh-sessions-rm
Author: Temoa

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer4 files
README.mdSource · read only
README language

@temoa/dsh-sessions-rm

Session management for DeepSeek Harness (DSH): a settings page that lists every historical session and physically deletes a session's log directory (irreversible, type-to-confirm, with an audit trail).

English | 中文

Features

  • Settings → Session Management — an additive settings.section page (no shipped UI is replaced).
  • Session list — title, relative time, status badges (running / persisted), blank vs untitled distinction.
  • Type-to-confirm delete — a modal dialog shows the session and an irreversible warning; you must type 确认删除 before the confirm button becomes clickable (guards against accidental deletes). Esc / backdrop / cancel close it.
  • Physical deletion — the Host locates the log via sessionPersistence.locate() and deletes the whole session directory (log + session-owned artifacts) directly through Node fs — no shell or sandbox involved, consistent across platforms.
  • Audit trail — every delete request (success or failure) appends one JSON line to ~/.dsh/sessions-rm.log (time / sessionId / title / ok / path or error).
  • Theme-aware — follows light / dark / system via official theme tokens.

Install

Option A — install as a package (dsh plugin add), no --patch needed

Install straight from GitHub — pnpm pins the package by commit with a full integrity hash:

dsh plugin --profile web add git+https://github.com/Temoa/dsh-sessions-rm.git

Because the package declares dsh.bundle.patch (cordis.patch.yml), the reconciler appends it to the profile's dsh.profile.bundles automatically — the plugin mounts at the PROFILE level and is active for every session on that profile. The client half is discovered through dsh.client (exports["./client"]) and the Host Remote manifest through exports["./typert"] (registered by dsh-typert-loader); no manual patch file is needed.

To uninstall: dsh plugin --profile web remove @temoa/dsh-sessions-rm.

> After changing plugin code, fully restart the harness — modules are cached per process URL.

Option B — install from source (local development)

git clone git+https://github.com/Temoa/dsh-sessions-rm.git
cd dsh-sessions-rm
dsh web --patch ./cordis.patch.yml

Dependencies

The package declares no dependencies — runtime imports (@deepseek-ai/cordis, @deepseek-ai/dsh-typert-protocol, @deepseek-ai/dsh-home-paths, zod) are provided by the DSH installation. Two ways to make them resolvable:

1. Symlink DSH's node_modules into the plugin directory (recommended, offline): ``bash ln -s /path/to/dsh/node_modules node_modules ` 2. Or run npm install in the plugin directory if the @deepseek-ai/*` packages are available on your registry.

Usage

Open Settings → Session Management: pick a session, click 删除 (Delete), type 确认删除 in the dialog, then confirm. The row disappears, the sidebar hides the session immediately (archived), the log directory is physically removed, and one line is appended to ~/.dsh/sessions-rm.log.

How it works

  • Hostlib/index.js registers ctx.sessionRm (a TypertRemoteService subclass) exposing list / delete. lib/typert.host.js is the Typert manifest (exports["./typert"]) auto-registered by dsh-typert-loader; api-gateway routes sessionRm/* wire calls to the service methods.
  • Clientlib/client.js (a factory-form CJS bundle built by scripts/build-client.js from src/client.js) registers matching descriptors via ctx.remote.$mount() and calls ctx.remote.sessionRm.list()/delete().
  • Delete pipeline — reject running agents → workspaceRegistry.archiveSession() (sidebar hides instantly via the archive set) → sessionPersistence.locate() → Node fs delete → append audit line.
  • Pure JS + hand-written decorator marking@Remote is a TS decorator; this project reuses the official Remote() decorator by constructing a decorator context manually (see addRemote in lib/index.js), so no TS toolchain is needed.

Configuration

None — the plugin is intentionally configuration-free. All behavior is fixed by design.

Development

npm run build:client   # node scripts/build-client.js → lib/client.js
npm test               # node test/index.mjs — manifest/bundle structure checks

Tests cover: Host service class shape, Typert manifest structure (package/face/codecs/invocations), and client bundle format.

Boundaries

  • Running sessions cannot be deleted — DSH has no public API to dispose a live agent; deleting a running session's log would corrupt the runtime.
  • Deleting is irreversible — log and artifacts are permanently removed. The archive step hides the session from the sidebar immediately; the in-memory record disappears after a restart.
  • Path self-validation — the delete target is derived from sessionPersistence.locate() and validated to be an absolute path; no external input is accepted. Deletion and audit writes run directly through Node fs, independent of the shell or the deployment sandbox boundary (the Windows profile mounts the pwsh executor, and the sandbox is unusable when dsh web starts from a drive root).
  • User-role semantics — the settings page is an additive UI; it never replaces shipped surfaces and reads no model context.

License

MIT