plur-ai/dsh-plugin
dsh
PLUR memory for DeepSeek Harness — engrams injected into the system prompt, no tool call required. Local-first, Apache-2.0.
Install
npx @deepseek-ai/dsh plugin --profile web add @plur-ai/dshRestart `dsh web` after install. Bundle APIs can change during the developer preview.
README badge
[](https://dshhub.dev/plugins/plur-ai-dsh-plugin)Paste this into your README. The star count updates with every catalog sync.
From the README
Excerpt from plur-ai/dsh-plugin, cleaned of badges and images.
@plur-ai/dsh
Persistent memory for DeepSeek Harness. Your agent corrected on Monday remembers on Tuesday.
English | 中文
Source lives in the PLUR monorepo. This repository is the plugin's public entry point — the npm package is built and published from the monorepo. Open issues and pull requests there.
Exposing memory as a tool is the common pattern — the model still has to decide to call it. This one puts the memories themselves in the prompt.
Overview
DeepSeek Harness starts every session knowing nothing about you. You re-explain the same conventions, corrections and preferences you explained yesterday.
This plugin gives dsh a memory that survives the session: corrections you make once, project conventions, the decisions behind them. It is for anyone who uses dsh for real work in the same codebase more than once.
Everything stays on your machine as plain YAML you can read, edit and delete.
Compatibility
| DeepSeek Harness | 0.1.0-rc.6 and later on the 0.1.x line (^0.1.0-rc.6) |
| Cordis | ^4.0.1 |
| Node | 20, 22, 24, 26 (tested in CI on all four) |
| Last verified against | dsh 0.1.0-rc.6, 2026-08-15 |
The dsh line is pre-1.0 and moving. Peer ranges use a caret so this plugin keeps
installing as the line advances; if a future release changes a host contract, the
plugin degrades to "no memory" rather than breaking your agent — every host
registration is contained, and /plur will show the failure.
Install
dsh plugin --profile web add @plur-ai/dsh
That's it. Restart dsh and your agent has memory.
Requires @plur-ai/core, which
installs alongside it.
Quick start
Teach it something once:
You: Always use pnpm in this project —
npm installbreaks the lockfile in CI.
Nothing else to do; the correction is detected and stored. Start a new session tomorrow, in the same directory:
You: How do I install dependencies here?
Agent: Use
pnpm install— you mentioned npm breaks the lockfile in CI.
No reminder, no tool call. To see what it knows, run /plur-memory.
Uninstall
dsh plugin --profile web remove @plur-ai/dsh
Your memories are not touched — they live in ~/.plur, independently of this
plugin, and remain available to every other PLUR integration. To remove them
too, delete that directory; to remove one engram, use plur_forget or
@plur-ai/cli.
To disable without uninstalling, set injectionMode: off (below).
How it works
PLUR registers a system-prompt section that DeepSeek Harness re-renders on every request. Relevant memories are simply there, in front of the model, with no tool call to decide on.
Recall runs off the turn path, so the block lands from the second assembly of a session onward. A turn is never delayed waiting on the memory store.
| Cue-based memory | @plur-ai/dsh | |
|---|---|---|
| Model must call a tool to recall | Yes | No |
| Extra round trip per recall | Yes | No |
| Works when the model ignores the hint | No | Yes |
| Tool schemas billed every request | 13 | 5 |
…
