liangmianya/dsh-synapse
Visual, non-linear conversation workspace for DeepSeek Harness — sessions, follow-ups and branches become a browsable conversation map.
Install
via npm
Resolves a published tarball rather than cloning the repository, and installs without any extra setup. Swap `web` for your profile name if you run another one.
via GitHub · npm package
Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.
The desktop app keeps its own profile, desktop, and only the dsh command it ships may change it — the npm-installed dsh refuses that profile. Install the command from the app menu (Manage dsh Command…), open Desktop once, quit it fully, run the line below, then reopen Desktop.
via npm
Resolves a published tarball rather than cloning the repository.
via GitHub · npm package
Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/desktop/pnpm-workspace.yaml.
Our install check ran in a web profile on npm's dsh, not in the desktop app.
What happened when we ran it
Installed cleanly when we ran it
Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run 8d agoon DeepSeek Harness 0.2.2-rc.1.
Show it in your README
For maintainers: the badge serves this listing's latest sandbox verdict, so a re-run updates it on its own — and it links readers to the full result here.
Due diligence
Security
No build script was blocked in our run.
Source: our sandbox install on DeepSeek Harness 0.2.2-rc.1, 8d ago.
package.json declares no preinstall, install or postinstall script.
Source: package.json on GitHub, read at our last sync. prepare is not recorded; it runs only on a GitHub install, and shows up under build scripts when pnpm blocks it.
Neither shell commands nor credentials.
Source: a keyword match on the README — a hint about what the plugin touches, not an analysis of its code.
Not an audit. These are the record of one install and two text scans; nobody has read this plugin's code on your behalf. Plugins run with your agent's permissions.
What it is — dsh-synapse provides a visual non-linear conversation workspace for DeepSeek Harness, turning sessions, follow-ups and branches into a browsable map.
Who it is for — When managing multi-turn conversations with branches and follow-ups in the DeepSeek Harness web profile, this tool helps organize them visually. Users who prefer native DSH interfaces for linear conversations or do not use web profiles may not require the additional mapping tool.
Watch out — Installation requires pnpm and DeepSeek Harness >=0.1.7-rc.2 with Node.js >=22.19.0. Sandbox testing confirmed successful installation and registration in a new profile. No obvious issues found.
The verdict — I would install it because it preserves native session forks for branching while adding a visual map, but only under the web profile requirement.
Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.
dsh-synapse is a DeepSeek Harness plugin that presents sessions, follow-ups and branches as a browsable, draggable and zoomable conversation map.
DeepSeek Harness keeps the native session log as the source of truth. dsh-synapse projects committed session events and native fork relationships into the map, rather than creating a second conversation history. The plugin reuses the existing DeepSeek Harness Web Server and adds the 会话地图 view to its web interface. Selecting text from an answer can populate a follow-up, while switching between the map and the native conversation keeps the current session context aligned. Canvas layout data is written to $DSH_HOME/synapse/; deleting that directory does not delete DeepSeek Harness sessions.
dsh-synapse is intended for developers who need to inspect related sessions and branches spatially, or move between native conversations and follow-ups while retaining their existing session data. It is not a replacement for the native session store, and is a poor fit where a second visual workspace is unnecessary. The plugin requires DeepSeek Harness >= 0.1.7-rc.2, Node.js >= 22.19.0, and the web profile. Its built-in patch supports only that profile. dsh-synapse does not modify prompts, model requests, tool schemas, provider routing or reusable KV-cache prefixes.
DeepSeek Harness stores the plugin’s canvas layout under $DSH_HOME/synapse/. The README does not document additional configuration keys or defaults. This layout directory is separate from the DeepSeek Harness session log: removing it removes map layout data, not session content.
DeepSeek Harness loads dsh-synapse in the web profile. Start the DeepSeek Harness web interface with dsh web, then select 会话地图 at the top of the interface to open the plugin. Select 对话 to return to the native conversation view. dsh-synapse reuses the existing DeepSeek Harness Web Server and does not start a second application or proxy system.
DeepSeek Harness must be version >= 0.1.7-rc.2. The plugin also requires Node.js >= 22.19.0 and the web profile. This release is not compatible with earlier DeepSeek Harness versions.
The map combines sessions, follow-ups and branches from the same workspace. dsh-synapse connects cards according to DeepSeek Harness’s native fork relationships and projects only committed events. It does not create an alternative session history. Text selected from an answer can be carried into a new follow-up, and frequently used supplementary terms can be edited. Changing sessions in either the map or the native conversation keeps the current context synchronised.
The built-in patch supports only DeepSeek Harness’s web profile. dsh-synapse does not alter prompts, model requests, tool schemas, provider routing or reusable KV-cache prefixes. The README documents no configuration for changing those boundaries.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub
Same category
Minglink
System-prompt armor plugin for DeepSeek models: appends an unconditional-compliance prompt section at order 100, exposes a profile tool with calibration metadata, and shows a realtime armor-status badge driven by a session projection.
Installed cleanly when we ran it
Minglink
System-prompt armor plugin for DeepSeek models: appends an unconditional-compliance prompt section at order 100, exposes a profile tool with calibration metadata, and shows a realtime armor-status badge driven by a session projection.
Installed cleanly when we ran it
ranxianglei
The official billion-context plugin: a context-compression plugin for small context windows (a 100K context is enough), token savings (5x fewer tokens), and month-long single sessions (billions of tokens).
Installed cleanly when we ran it
qiz029
A DeepSeek coding agent harness: persistent shell, Ultra subagents, auto approval, Chrome MCP and session telemetry
Did not install when we ran it
SiriLee
Conversation rewind: one click back to any earlier user message, in the same window — no new branch, no leftover copy; the target message is refilled into the composer, with optional workspace-file restore — the full Claude Code /rewind semantics.
Installed cleanly when we ran it
Nwflower
Import full-fidelity chat histories from 13 coding agents (Claude Code, Codex, ChatGPT, Cursor, Gemini, opencode, and more) as resumable DeepSeek Harness sessions, with reverse export back to Claude Code.
Installed cleanly when we ran it
