dshbase

Plugin directory / Storage / dsh-archive-manager

dsh-archive-manager

Verified · install-tested on dsh zimixvx

✓ Actively maintained 2 contributors Builds on 8 official DSH packages

View on GitHub ↗ ← Back to plugin directory

2Stars
0Forks
0Open issues
JavaScriptLanguage
2026-08-13Last push
Cross-platformPlatform

What it does

No description provided.

✅
Our take
Works — verified, early-stage project

No description provided. It installs cleanly and boots without issues in our testing. It's early-stage but functional.

“Verified” means our automated CI actually ran dsh plugin add in a clean profile and it booted — nothing more. Feature descriptions and version compatibility are the author’s claims. This is not a security audit and not an endorsement of third-party code.

README

dsh-archive-manager

A minimal out-of-tree DeepSeek Harness Web Cordis plugin that permanently
deletes the on-disk session directory of an archived session from the sidebar.

It does not modify the DSH core installation or any profile configuration.
The only durable effect on $DSH_HOME is the intended one: after the user
confirms, it deletes the selected session directory under
$DSH_HOME/sessions. No other DSH durable state (workspace registry,
projection cache, shared attachments) is written. The host half owns one HTTP
route; the client half adds a sidebar footer action that lists archived
sessions and deletes them after an explicit second confirmation.

What it does

  • Host half (index.js) registers POST /archive-manager/delete.
  • Client half (client.js) registers a sidebar.footer.action list entry
    (id: archive-manager, order: 80). Wide mode shows the label 已归档 N;
    the narrow rail shows only the archive icon.
  • The modal lists only the ids in the workspace registry's archivedSessionIds
    that also have a session summary in the client session baseline, displaying
    displayTitle (or the id), cwd, and updatedAt.
  • Each row has a trash button. Deleting requires a clear second confirmation
    stating that the session directory will be permanently deleted and cannot be
    restored.
  • Deleting issues a same-origin POST /archive-manager/delete and, on
    success, refreshes both sessions and workspaces. A local deleted-id set
    hides the row even though the archived marker is intentionally left intact.

Install

This is an out-of-tree plugin: place it on disk and install it into the
existing web profile.

Option A — install from GitHub

dsh plugin --profile web add "github:zimixvx/dsh-archive-manager"

Option B — install from a local path

With the plugin directory at D:\Code\DeepseekHarness\plugins\dsh-archive-manager:

dsh plugin --profile web add "D:\Code\DeepseekHarness\plugins\dsh-archive-manager"

Then add the plugin to the web profile's bundle list in
$DSH_HOME/profiles/web/package.json:

{
  "name": "dsh-profile-web",
  "private": true,
  "dependencies": {
    "dsh-archive-manager": "file:D:/Code/DeepseekHarness/plugins/dsh-archive-manager"
  },
  "dsh": {
    "profile": {
      "bundles": [
        "@deepseek-ai/dsh-base",
        "@deepseek-ai/dsh-web-app",
        "dsh-archive-manager"
      ]
    }
  }
}

The exact dependencies entry is written by dsh plugin --profile web add;
only the bundles list needs the manual addition.

The plugin's cordis.patch.yml (declared via dsh.bundle.patch) inserts the
host row:

- insert:
    - id: archive-manager
      name: dsh-archive-manager

Restart

A running process does not pick up new bundle rows, so restart the web profile:

dsh web

After a page refresh, the sidebar footer shows the archive-management action.

Safety and limitations

  • Only archived sessions. The route refuses any id not present in
    workspaceRegistry.archivedSessionIds.
  • Live sessions are refused — checked before the persistence lookup and
    again immediately before the rm, with HTTP 409.
  • Raw-artifact backend required. The persistence backend must advertise
    supportsRawArtifacts === true and a locate() returning
    { kind: 'jsonl', path }. Otherwise the route answers 501.
  • Deletes the session directory only. rm(dirname(location.path), { recursive: true, force: false }) removes the directory that holds the
    session's JSONL log (and any session-local files inside it). It does not
    modify the workspace registry, the archived markers, the projection cache,
    or content-addressed attachments (which live in a separate shared store and
    are shared across sessions).
  • Stale archived markers. After a successful delete, the archived marker in
    archivedSessionIds remains by design (removing it would mutate the
    registry). Because the panel only lists archived ids that still have a
    session summary, and the physical deletion removes that summary, the leftover
    marker does not reappear after a page reload. A local deleted-id set also
    hides the row immediately even if the follow-up refresh fails.
  • Not reversible. The deletion is a recursive rm with force: false.
    There is no trash or restore path.

Uninstall

Remove dsh-archive-manager from the profile's dsh.profile.bundles (and from
dependencies), then restart. The plugin adds no durable state of its own, so
there is nothing else to clean up.

License

MIT — see LICENSE.

Install

🧩 Let your agent install it (recommended)

Install the catalog once, then DeepSeek Harness can find and install any plugin from this site automatically:

dsh plugin add dshbase-catalog

Then say "install dsh-archive-manager for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.

This plugin is GitHub source (not published to npm) — install it straight from the repo:

Web profile:

dsh plugin --profile web add github:zimixvx/dsh-archive-manager

Headless (CLI) profile:

dsh plugin --profile headless add github:zimixvx/dsh-archive-manager

Test report

Verified: L1 install + L2 load + L3 runtime from GitHub source on dsh 0.1.0-rc.6.

When to use it

Give the agent durable storage — a database, file store, or persistence layer — so state survives sessions.

Who it's for

Users whose tasks need to read or write structured data and keep it across runs.

For developers — extending it

Storage backends and data models are the seams — plug a new database, add schemas, or expose query tools.

Security: not yet scanned — our daily static scan will cover it shortly.

Share this badge

More in Storage

Browse all 7797 plugins →