dsh-archive-browser

DeepSeek Harness treats archiving as a one-way street. Once a session is archived it vanishes from every list and the sidebar, and the official build ships no unarchive entry point, so historical conversations sink out of reach. dsh-archive-browser adds a dedicated panel at the bottom of the sidebar that pulls those buried sessions back into view. From there you can read the full transcript with role-colored rendering, run a read-only impact audit that itemizes every file the session created or modified, every command it executed, and every sub-agent or fork it spawned, restore the session to the sidebar with a single click, pipe a digest of the archived content into your current input box, or fork a brand-new live session from any archived node and pick the conversation right where you left off.

The panel is deliberately lightweight. Opening the list reads only DSH's own projection cache and a single stat call, never decompressing any zstd transcript frame (roughly 4 ms for nine archived sessions versus over 330 ms for full extraction). Message counts and other details are loaded lazily the moment you expand a particular session. Sorting runs entirely client-side and supports four rules: most-recent descending, most-recent ascending, archive order, and title, with your choice remembered across sessions. The impact panel is strictly read-only: it mutates nothing, touches files only for existence, size, and mtime checks, and never auto-uninstalls dependencies, leaving cleanup decisions firmly in your hands.

This is the plugin to reach for when your DSH workspace has grown a graveyard of archived sessions and you need to look back without breaking what you have. Use it to audit exactly what a past conversation did on your machine before deciding to clean up, to rescue a useful thread back into the active sidebar, to feed old context into a fresh task, or to fork a new branch from an old node and keep going. It respects DSH's storage layout, works through the host-side HTTP routes and workspaceRegistry incremental broadcasts, and requires no changes to your data files, just a one-time restart after install to mount the routes.