This is a community plugin, not an official DeepSeek product.

Session Delete is an independent project. It is not affiliated with, endorsed by, or supported by DeepSeek AI, and it is not part of DeepSeek Harness. DeepSeek Harness and DeepSeek are names and marks of their respective owners. You are installing code that deletes files on purpose. Read Safety first.

Why this exists

DeepSeek Harness archives sessions. Archiving is useful — the row leaves the sidebar, the session can come back — but it is not removal. The compressed log stays under ~/.dsh/sessions/, the projection checkpoint stays under ~/.dsh/storages/session_projcache/, and the workspace keeps accounting for an id you may never open again.

Session Delete adds the missing verb.

	Archive	Delete
Row leaves the sidebar	✅	✅
Conversation log on disk	stays forever	removed
Projection cache	stays	removed
Workspace accounting / pin / archive entry	kept	removed
Can be restored	unarchive	no

Archive is untouched. Delete is a second, explicit choice at the bottom of the same menu, behind a confirmation.

Install

Requires DeepSeek Harness 0.2.x (tested on 0.2.1-rc.1). Desktop and the Web UI are both supported.

The repository is the install unit. The npm package inside it is dsh-plugin-session-delete; the spec you paste is the GitHub address.

1. From the Plugins page (recommended)

1. Open the sidebar and choose Plugins.

2. Install a plugin and paste:

   github:Adolanium/dsh-session-delete
   

3. Install it. The bundle is enabled by default.

4. Refresh the DeepSeek Harness window (Ctrl+R / Cmd+R). The browser half is loaded lazily, so the menu entry appears after a reload.

No build permission is needed: the package ships plain JavaScript, has no prepare script, and has no runtime dependencies.

2. With the dsh CLI

If you boot profiles yourself (Web, headless, or a stopped Desktop), the same spec installs into a named profile:

dsh plugin --profile desktop add github:Adolanium/dsh-session-delete

dsh appends the bundle to the profile's dsh.profile.bundles because the package declares dsh.bundle. Start DeepSeek Harness afterwards, then refresh the window.

Pin the install if you want it frozen to this release:

dsh plugin --profile desktop add github:Adolanium/dsh-session-delete#v0.1.0

Remove it with:

dsh plugin --profile desktop remove dsh-plugin-session-delete

Running the CLI against the desktop profile while the Desktop app is running is supported by the profile lock, but the Plugins page is the smoother path there — it owns the same operation and reports activation status.

3. From a checkout (development)

git clone https://github.com/Adolanium/dsh-session-delete.git
cd dsh-session-delete
pwsh -File scripts/install-dev.ps1

That links the checkout into ~/.dsh/profiles/desktop/node_modules and adds the Loader entry to the profile patch (with a timestamped backup). Undo with scripts/uninstall-dev.ps1.

The profile reloads configuration live, so a linked package activates without a restart. HMR does not watch module roots, so code edits need a restart.

Use

Open a session row's ⋯ menu and choose Delete session….

The dialog names the conversation and explains that the log and its cached projections will be removed. Delete performs the removal; Cancel leaves everything alone.

What happens next depends on the session:

Session state	Result
Cold — no live Agent owns it	Removed immediately. The row leaves the list; the dialog closes.
Live — open in this app, or a running turn owns it	The dialog explains that the log is still in use and offers Delete on next start.
Unknown id	Rejected. Nothing is touched.

Delete on next start

A live session cannot be pulled out from under its Agent, so the second option queues it instead:

• the id is written to ~/.dsh/plugin-session-delete/pending.json;
• the session is archived (best effort) so the row disappears from the default list;
• the next DeepSeek Harness start retries the removal, when the write handle is free;
• unarchiving the session cancels its queued removal — the archive is the visible "pending removal" state.

A queued id whose session is already gone is dropped silently. A queued id that is still in use stays queued for the next start.

What Delete removes

For one session id, the Host removes:

• the session directory under ~/.dsh/sessions/<project>/<session-id>/, including every format generation (session.vN.jsonl.zstd) and the lock artifact;
• the projection-cache record from the session_projcache domain, through the domain itself, so an in-memory row cannot survive the delete;
• the workspace accounting slot, the global pin, and the archive entry.

It deliberately leaves:

• attachments — content-addressed under ~/.dsh/attachments and possibly shared with other sessions;
• subagent child sessions — separate ids, hidden from the sidebar by design; delete them individually;
• the SQLite search index, if your composition uses dsh-session-query-sqlite — it reconciles deleted sources on the next search;
• derived rows in other domains (telemetry, titles) — they are keyed by an id that no longer resolves and are ignored.

Safety model

Deleting a file is easy. Deleting the right file while the app is running is the hard part. The plugin is built around four rules:

1. One writer. Before touching anything, the Host takes the persistence write handle for the session and immediately closes it. A live Agent, another DSH process, or a crashed-but-held lock makes that open fail, and the delete is refused. The handle is the proof of "nobody is using this".
2. Loopback only. The route is rejected for non-loopback peers. A present Origin must be the Web client's origin or the Desktop shell's dsh-app://app; a cross-site fetch cannot reach it (JSON content type forces a preflight the route does not answer).
3. Strict identity. The id must match ^[A-Za-z0-9][A-Za-z0-9._-]{0,127}$, the target directory must be named exactly that id, and it must contain a canonical session[.vN].jsonl[.zstd] log. A malformed id cannot address another path.
4. No surprises. If the materialized log is not under the configured root, the Host refuses and says so instead of deleting accounting and leaving the log behind. Cleanup failures are logged; the response reports what happened.

There is no network access, no telemetry, and no background process. The plugin reads and writes local files through the Host's own services.

Configuration

All fields are optional. Defaults match a stock installation.

Field	Default	Meaning
dshHome	$DSH_HOME, else ~/.dsh	Data root used to derive the two roots below.
sessionsRoot	<dshHome>/sessions	Session persistence root — the root of dsh-session-persistence-jsonl.
storagesRoot	<dshHome>/storages	Storage root used only as a fallback when the storageDomain service is absent.

Set these in the profile entry if you run a non-default persistence root:

- id: session-delete
  name: dsh-plugin-session-delete
  config:
    sessionsRoot: /srv/dsh/sessions

Uninstall

• Plugins page: open the plugin and remove it.
• CLI: dsh plugin --profile desktop remove dsh-plugin-session-delete.
• Dev link: pwsh -File scripts/uninstall-dev.ps1.

Queued removals stay in ~/.dsh/plugin-session-delete/pending.json; delete that file if you want to forget them.

How it works

Session row menu
      │  "Delete session…"
      ▼
Confirmation dialog (browser half, shell.overlay)
      │  POST /plugin-session-delete/api  { sessionId, mode }
      ▼
Host half
      ├─ write-handle gate ────────► live?  → 409 session/in-use
      ├─ remove session directory
      ├─ drop session_projcache record
      └─ detach / unpin / unarchive
      ▼
Client refreshes the session baseline → the row disappears

The Host half is one Cordis plugin (lib/index.js) that injects sessionPersistence and workspaceRegistry and registers one exact route on webServer. The browser half (lib/client.js) is a hand-written module-loader bundle: one entry in sidebar.workspaces.session.menu.item, one dialog in shell.overlay, and nothing else.

Compatibility

• DeepSeek Harness 0.2.x (tested on 0.2.1-rc.1, Desktop and Web).
• Windows, macOS, and Linux.
• No dependencies, no build step, no native modules.
• The plugin uses public Host services (sessionPersistence, workspaceRegistry, storageDomain) and public client slots. It does not monkey-patch, fork, or modify DeepSeek Harness.

Developer preview means breaking changes. If a release moves one of those seams, the plugin fails soft: a missing service keeps it inactive, and a failed delete returns an error instead of half-cleaning a session.

Development

node --test

Nineteen tests, no dependencies:

• Host (test/host.test.mjs) — the real plugin against a temporary DSH home, a fake persistence seam, a fake workspace registry, and direct HTTP request/response objects. Covers the cold/live/queued paths, id and origin checks, the location guard, and the unarchive-cancels-removal rule.
• Browser (test/client.test.mjs) — the real lib/client.js loaded through a stub of the module-loader contract; renders the menu item and dialog and drives the request/refresh flow with a stub fetch.

The artwork is generated with image models and composed with sharp; the source banner lives in assets/.

FAQ

Does this replace Archive? No. Archive and its unarchive flow are unchanged. Delete is an additional, explicit action.

Can I undo a delete? Not for an immediate removal. For a queued one, unarchive the session before the next start.

Why does it say the session is still open? The session has a live Agent in this Host. Use Delete on next start; the next launch removes it.

Why can't it find my session? Your persistence root is not ~/.dsh/sessions. Set sessionsRoot to the root used by dsh-session-persistence-jsonl.

Does it delete files outside ~/.dsh? No. Only the session's own directory under the configured root, its session_projcache record, and its registry entries.

Does it work in the browser-only Web UI? Yes. The browser half calls the same-origin route; the Host enforces loopback and origin checks.

License

MIT.

Community project

Session Delete is an independent community plugin. It is not affiliated with, endorsed by, sponsored by, or officially associated with DeepSeek AI or the DeepSeek Harness project. DeepSeek, DeepSeek Harness, and dsh are names and marks belonging to their respective owners. Use it at your own risk; it deletes data by design.