Introduction

The philosophy of DSH is “Everything is a plugin,” and Web GUI capabilities can be extended through plugins. For users who already have archived sessions, a common problem is the lack of a centralized management entry: they need to confirm whether a specific archived session should continue or, after confirming it is useless, clean up the session logs on disk.

Below is an introduction to @chushiz/dsh-archive-manager. It is an archived session management plugin for the DeepSeek Harness Web GUI, used to browse, restore, or physically delete archived sessions. This plugin is maintained by ChuShiZ and is licensed under MIT.

What is this

@chushiz/dsh-archive-manager is a DSH Web GUI plugin with the entry point at Settings > Archived Sessions.

It primarily provides three categories of operations:

  • Browse and Search: View archived sessions by workspace, and support full-text search of titles, table of contents, id, presets, and session bodies.
  • Restore: Unarchive and open the session.
  • Delete: Physically remove the session log directory; this is irreversible.

Core Features

  • Browse archived sessions grouped by workspace.
  • Support full-text search of titles, table of contents, id, presets, and session bodies.
  • Search user messages, AI replies, tool calls and parameters, and todo based on the harness’s sessionQuery SQLite FTS5 index.
  • Search result highlighting, short keyword windows centered on the keyword, a maximum of 5 results per session, and filtering by type.

Preview, Restore, and Batch Delete

  • Click the title to expand a preview of the last 4 sentences of conversation.
  • “Restore and Open” unarchives and opens the session.
  • Multi-select checkboxes + top batch delete.
  • Automatically stop active agents before deleting.
  • Deleting will physically remove the session log directory; the operation is irreversible.

Installation and Enablement

First, confirm that the DSH and Node.js versions meet the requirements below, then proceed with the installation.

Execute the official installation command in the DSH plugin environment:

dsh plugin --profile web add @chushiz/dsh-archive-manager

After installation, restart dsh web.

Once enabled, go to the Settings > Archived Sessions page to use this plugin.

Typical Usage

The following is explained in the order of actual operations.

  1. Go to Settings > Archived Sessions and browse archived sessions by workspace.
  2. Enter keywords to search. The search scope includes titles, table of contents, id, presets, and full-text search of session bodies.
  3. When you need to confirm the target session, click the title to view a preview of the last 4 sentences of the conversation.
  4. If the session is still useful, select “Restore and Open,” and the plugin will unarchive and open the session.
  5. If the session is useless, first use the multi-select checkboxes to select the target sessions, then perform the delete via the top batch delete.
  6. Active agents will be stopped automatically before batch deleting; deleting will physically remove the session log directory, which is irreversible.

Version and Runtime Environment

The versions and dependency requirements verified from the provided materials are as follows:

dsh >= 0.1.0-rc.7: Supported (FTS5 search + direct service connection)
dsh < 0.1.0-rc.7: Unverified (Depends on sessionQuery.searchSessions and webServer carrier)
Node.js ^22.19 || >=24 (As required by dsh)
peerDependencies:
@deepseek-ai/cordis ^4.0.1
@deepseek-ai/dsh-client-runtime ^0.1.0-rc.8

Runtime fallback behaviors:

  • Automatically fallback to per-session scanning when there is no FTS backend (openAt: never).
  • Automatically fallback to HTTP API when the service is not proxied to the browser.

Permission Boundaries

The boundaries between the plugin’s host side and client side are as follows:

  • Host side: Operations on the workspace registry’s archive collection and persistence state: list is read-only, unarchive reverses archiving, and delete removes the log directory via shell.
  • Host constraints: Does not write logs and does not register tools facing the model.
  • Client side: Registers the settings.section on the settings page and calls the above operations via the archiveManager service.

Since delete removes the session log directory via shell, you need to understand its impact according to the current DSH process permissions. Before installing, it is recommended to check the source code and license, then proceed with the physical delete.

Conclusion

@chushiz/dsh-archive-manager centralizes common management actions for archived sessions within the DSH Web GUI settings page: browsing by workspace, full-text search, preview, restore and open, or physical deletion after confirming they are useless.

The provided materials did not provide the directory page URL. The project GitHub repository is:

https://github.com/ChuShiZ/dsh-archive-manager