README.md

August 30, 2026 · View on GitHub

Session Archive: local-first archived-chat center for DeepSeek Harness

Session Archive

A local-first archived-chat center for DeepSeek Harness

dsh-archived-chats

npm version npm downloads CI Node.js 18 and 24

MIT License Awesome DSH Plugin GitHub stars

English · 简体中文

Plugin market · npm · Releases · Discussions · Private security report

Session Archive gives DeepSeek Harness a first-class home for chats that disappear from the sidebar after archive. Browse every archived conversation by workspace, search its full content, inspect validated local history, and recover or remove it through explicit, reversible workflows.

Formerly Archived Chats, now Session Archive / 会话档案. The package name, repository, install command, and local data location are unchanged; existing users need no data migration.

Quick start

dsh plugin --profile web add dsh-archived-chats@latest

Restart DSH once, then open Settings → Session Archive.

Update an existing installation:

dsh plugin --profile web update dsh-archived-chats

Native read-only History preview with snapshot time and a synthetic stored image Storage and Retention with session directories, protection snapshots, and policy controls

Core capabilities

AreaWhat it provides
Browse and searchWorkspace-grouped archive browsing, full-text search across messages and tool results, filters, sorting, tags, and notes.
Read-only previewNative conversation layout for Markdown, reasoning, tool activity, JSON, code, and available stored images, with responsive turn navigation.
Local HistoryValidated versions captured after archive, read-only snapshot preview, confirmed deletion, clear-history, and Restore as copy without overwriting the source.
Backup and restoreJSON + Markdown ZIP export with preview-first, conflict-safe import. Existing session IDs are never overwritten.
Recoverable deletionSnapshot-protected Recycle Bin with immediate Undo, two-level restore, and separately confirmed permanent deletion.
Storage and relationshipsSeparate storage accounting, preview-first retention policies, and read-only Origins & Branches for forks and subagent trees.

Safety by design

  • Local only: plugin metadata, recycle records, policies, and validated snapshots stay under $DSH_HOME/plugin-data/archived-chats/. Nothing is uploaded or cloud-synced.
  • No silent overwrite: imports and History restores create or select non-conflicting IDs; they never replace an existing session.
  • Deletion stays explicit: ordinary removal enters the Recycle Bin after snapshot protection. Physical removal is available only through confirmed permanent-purge actions.
  • No automatic cleanup: retention policies are saved separately from execution. Every cleanup starts with a short-lived preview and explicit selection.
  • Backup scope is visible: ZIP exports preserve complete session JSON and readable Markdown, but do not include attachment bytes or descendant sessions.

Compatibility

Features activate from the public capabilities exposed by the DeepSeek Harness Host instead of a hard-coded Host version.

Host capabilityPlugin behavior
Archive and session readsBrowsing, search, preview, History inventory, storage accounting, and lineage.
Attachment readsStored images appear in conversation and snapshot previews; without it, text remains readable.
Public session writerZIP import, Restore as copy, and snapshot fallback when an original is missing all write through the Host's public create / append / locate capability, or a dedicated restore entry point where one exists.
Missing write capabilityThe operation returns restore-unsupported without writing or overwriting data.

Back up $DSH_HOME/plugin-data/archived-chats/ before downgrading to a release that does not display History or understand recycle snapshots.

Demo preview

The eight fixed screenshots below come from an isolated Simplified Chinese light-theme Web environment with synthetic conversations. They contain no real user data, paths, notes, or credentials, and are the same ordered image set declared to the plugin market.

View all eight screenshots
Session Archive overview with five management views
Archive overview
Full-text search, filters, tags, and readable hit excerpts
Full-text search
Native read-only History preview with a stored image
Read-only preview
History timeline with restore-as-copy and deletion actions
History timeline
Irreversible confirmation before clearing ordinary History
Clear History confirmation
Recycle Bin protection snapshot, restore, and permanent deletion
Recycle Bin
Storage accounting and retention policy controls
Storage and retention
Origins and Branches with forks, subagents, and recycled state
Origins and Branches

Documentation

ResourceEnglish简体中文
User guideRead the guide查看指南
ArchitectureMaintainer architecture维护者架构
Release historyGitHub ReleasesGitHub Releases

See also Support, Security, Contributing, Code of Conduct, and Discussions.

Project status

Session Archive is actively maintained. The latest stable npm release receives fixes and security updates; older releases should be upgraded before reporting a problem. Reproducible bug reports and focused pull requests are welcome. Accepted community tasks are marked help wanted; read the claim workflow before starting substantial work. Maintenance is performed as availability permits, so no fixed response or release schedule is promised.

Development

npm test

The suite covers Host and browser behavior, export/import, History, Recycle Bin, retention, search, responsive layout, public types, package contents, and repository hygiene. It uses isolated temporary data and never reads real sessions.

Uninstall

dsh plugin --profile web remove dsh-archived-chats

Uninstalling removes only the plugin package. It does not delete local data under $DSH_HOME/plugin-data/archived-chats/ or trigger Recycle Bin permanent purge. Retained data includes metadata.json, trash.json, retention.json, the snapshots/ directory, and any legacy pending-deletions.json that has not yet been migrated. A later reinstall can use this data. Before permanently removing the directory, restore and back up anything you need, then delete it manually only after confirming that none of its data is still required.

License

MIT