Skip to main content
All posts
Plugins

Best DeepSeek Harness Session and Message Plugins (2026)

Eight DeepSeek Harness plugins for rewinding sessions, importing chat history from other coding agents, sharing conversations, and cleaning up session data.

DeepSeek Harness (dsh) persists every session as an append-only event log — that structural choice is why plugins can rewind conversations, export full-fidelity history, or import sessions from other coding agents without reconstructing state from a flat transcript. Here are eight session and message plugins from FindHarness's curated index, ranked by GitHub stars as of August 2026.

The picks at a glance

PluginStarsWhat it doesLink
dsh-turn-rewind42Rewind conversation and workspace state via a Change LedgerPlugin
dsh-chat-import28Import history from 13 other coding agents, resumablePlugin
dsh-interconnect26Cross-instance message/event handoff between DSH instancesPlugin
dsh-message-edit18Branch-based message editing, reroll, retry, version timelinePlugin
dsh-share17One-click conversation sharingPlugin
dsh-suite (plugin-session-export)16Export the session log as Markdown or HTMLPlugin
dsh-explain10Cross-session learning threads with per-source explanationsPlugin
dsh-plugin-session-delete7Delete sessions with a risk-consent dialogPlugin

All eight come from the sessions-messages category in FindHarness's curated (source: awesome) index. None have been security-reviewed by FindHarness — read the plugin security checklist before installing, particularly for plugins that read, export, or delete session data.

Why this category exists: event-sourced sessions

dsh ships two official session persistence backends — session-persistence-jsonl and session-persistence-sqlite — both storing sessions as an append-only log of events rather than a mutable chat array. That's a meaningful architectural detail for this category specifically: rewind plugins can jump to any prior point because the intermediate states were never discarded, export plugins can reconstruct a full trajectory rather than just the visible messages, and import plugins can map another agent's history onto the same event-oriented shape instead of faking a conversation transcript.

The eight plugins

1. dsh-turn-rewind — rewind conversation and workspace

github.com/anionex/dsh-turn-rewind · 42 stars · BSD-3-Clause

Rewinds both conversation state and workspace state together, powered by what the author calls a persistent "Change Ledger." The workspace half matters as much as the conversation half here — rewinding a chat back to an earlier point is only useful if the files an earlier turn edited also revert, and that's the harder problem this plugin is solving.

dsh plugin --profile web add github:anionex/dsh-turn-rewind

2. dsh-chat-import — bring your history from elsewhere

github.com/nwflower/dsh-chat-import · 28 stars · MIT · npm: dsh-chat-import

Imports full-fidelity chat histories from 13 other coding agents — Claude Code, Codex, ChatGPT, Cursor, Gemini, opencode, and more — as resumable dsh sessions, and can export back to Claude Code in reverse. If you're evaluating a move to dsh (see our migration guide) and don't want to start every project's history from zero, this is the most directly useful plugin in this category for that specific case.

dsh plugin --profile web add dsh-chat-import

3. dsh-interconnect — cross-instance messaging

github.com/chinesezjc/dsh-interconnect · 26 stars · MIT

Cross-instance message and event handoff between separate DSH instances, routed through an interconnect server. This is a different axis from the other plugins here — it's not about one session's history, but about multiple running dsh instances (potentially on different machines) exchanging messages and events live.

dsh plugin --profile web add github:chinesezjc/dsh-interconnect

4. dsh-message-edit — branch, reroll, retry

github.com/moeblack/dsh-message-edit · 18 stars

Branch-based message editing with reroll, retry, and a version timeline — the pattern familiar from consumer chat products where editing an earlier message forks the conversation rather than silently rewriting history. Useful if you want to explore multiple directions from the same point in a session without losing the original branch.

dsh plugin --profile web add github:moeblack/dsh-message-edit

5. dsh-share — one-click sharing

github.com/hellodigua/dsh-share · 17 stars · MIT

Shares a conversation with one click. The description is deliberately minimal; if you plan to share sessions that touch private code or credentials, verify exactly what gets included in a share link — redacted vs. full session content — before relying on it in a work context.

dsh plugin --profile web add github:hellodigua/dsh-share

6. dsh-suite (plugin-session-export) — export as Markdown or HTML

github.com/whyihaveyou/dsh-suite (packages/plugins/plugin-session-export) · 16 stars · MIT

Exports the append-only session log as human-readable Markdown or HTML, grouped by trajectory source. "Grouped by trajectory source" is the detail worth noting — it suggests the export distinguishes between, say, the main conversation and any subagent delegations within it, rather than flattening everything into one linear document. Note this plugin lives inside a monorepo at packages/plugins/plugin-session-export — check the repository's own README for the exact install path.

dsh plugin --profile web add github:whyihaveyou/dsh-suite

7. dsh-explain — cross-session learning threads

github.com/yuezengwu/dsh-explain · 10 stars · MIT

A "local-first learning mode": cross-session learning threads with per-source explanations. This sits closer to the memory category conceptually — see our memory plugins roundup if this is really what you're after — but it's tagged under sessions-messages because it's built around threading and per-source attribution rather than a general-purpose fact store.

dsh plugin --profile web add github:yuezengwu/dsh-explain

github.com/lsz-asd/dsh-plugin-session-delete · 7 stars

Adds session deletion to the Web UI and desktop client — a header danger button and a per-session-row menu item, both behind a risk-consent dialog. The description notes it removes the session log, the projection cache, and workspace accounting entries via a host endpoint and agent tool, not just the visible entry in the UI list. Worth having if you're accumulating throwaway sessions and dsh doesn't otherwise expose a clean way to remove them.

dsh plugin --profile web add github:lsz-asd/dsh-plugin-session-delete

FAQ

Are dsh sessions stored locally by default?

Yes — dsh's official persistence backends (session-persistence-jsonl, session-persistence-sqlite) write to local storage under $DSH_HOME. None of the plugins above are required for sessions to persist at all; they add rewind, export, import, sharing, cross-instance messaging, or deletion capabilities on top of that baseline.

Is dsh-share safe to use with sessions that touch private code?

Read the plugin's own documentation before relying on it for anything sensitive — the FindHarness description doesn't specify whether shared links are redacted or contain the full session, and that distinction matters if your sessions include proprietary code, credentials, or internal file paths.

Can I import history from Claude Code and then keep using both tools?

dsh-chat-import's description explicitly mentions "reverse export back to Claude Code," which suggests round-tripping is a supported use case rather than a one-way migration — but confirm the specifics in the plugin's own README before depending on bidirectional sync for daily use.

What's the difference between dsh-turn-rewind and dsh-message-edit?

dsh-turn-rewind reverts both conversation and workspace file state to an earlier point — it's about undoing what happened. dsh-message-edit forks the conversation from an edited message going forward — it's about branching into a new direction rather than undoing the old one. They solve adjacent but distinct problems.

Does deleting a session with dsh-plugin-session-delete free up disk space?

The description states it removes the session log, projection cache, and workspace accounting entries, which suggests a fuller cleanup than just hiding the session from the UI list — but verify against the plugin's own documentation if disk usage is your specific concern.

Next steps

If cross-session persistent memory rather than session log management is what you're after, see 7 DeepSeek Harness Memory Plugins Compared. Browse the full category at /categories/sessions-messages, or start with What Is DeepSeek Harness? if you're new to the project.