DeepSeek Harness memory

DeepSeek Harness memory plugins: what works across sessions

DeepSeek Harness 0.2.1-rc.5 has durable sessions and compaction, but no cross-session memory provider is enabled by default. DSH refuses plugins whose declared range misses your release, so check the package line before you install.

DeepSeek Harness. Sources checked 2026-11-02.

Which DeepSeek Harness memory plugin should you use?

For current DSH 0.2.x, use a plugin that declares 0.2 compatibility, such as the OpenViking bundle, if you want automatic capture and recall. If you prefer explicit model-called tools, the official DSH repository ships default-off MCP overlays for Memorix, MCP Reference Memory, and Engram under apps/cli/config/examples/mcp-memory.

MemoryRouter provides automatic capture and relevant recall through dsh-memoryrouter, a community Cordis plugin. Version 0.2.0, published 2026-11-02, declares engines.dsh >=0.2.1-rc.1 <0.3.0, so it passes the DSH install check on 0.2.1-rc.5. It was verified on a clean 0.2.1-rc.5 install: a fact taught in one headless session was recalled in a new session. Still on DSH 0.1.x? Pin [email protected].

DeepSeek Harness memory options compared

Four different layers are often called DSH memory. They differ in scope, recall behavior, and whether the current harness will load them. Checked on 2026-11-02.

Option	Recall trigger	Storage and scope	Current status
Session log and compaction	Resume or fork the same session. Compaction replaces older model-visible history with a summary.	An append-only session log. Persistence is provided by a backend such as the JSONL plugin.	Built into current DSH. It continues one session lineage, not shared cross-session memory. Source
Official memory MCP guide	The model calls provider write and search tools exposed by the DSH MCP client.	Provider-owned. The documented reference server uses one local JSONL knowledge graph.	Copy-paste ready in current master after you install the pinned third-party provider. Source
@openviking/dsh-memory-plugin	Automatic context injection and session capture, plus explicit OpenViking MCP tools.	An OpenViking server, local or remote, with cross-session and cross-project scope.	Declares DSH >=0.1.0-rc.6 and <1.0.0-0. Its docs list verified 0.2.1 releases through rc.3. Source
dsh-memoryrouter 0.2.0	Automatic relevant recall before a turn and automatic capture after a completed turn.	A hosted, key-scoped vault shared across DSH sessions, channels, machines, and connected tools.	Declares engines.dsh >=0.2.1-rc.1 <0.3.0. Installs and recalls across sessions on current DSH 0.2.1-rc.5. Use 0.1.1 on DSH 0.1.x. Source

What DeepSeek Harness includes today

DSH sessions are event-sourced append-only logs. A persistence plugin can save that log, and the shipped compaction backend can replace an older model-visible span with one summary while keeping the original shadowed events available for deterministic replay. That is durable session history, not automatic retrieval from unrelated sessions.

The official repository ships three default-off third-party MCP overlays under apps/cli/config/examples/mcp-memory. DSH starts or connects to the chosen provider and exposes its tools, but it does not install, initialize, or manage that provider for you. DeepSeek describes the overlays as interoperability examples rather than endorsements.

What DeepSeek Harness forgets

Without an enabled compatible provider, a fresh unrelated session only has the context assembled for that session.

A new session does not automatically retrieve decisions from a different session.
Compaction keeps a working summary inside one session; it does not create a shared semantic index.
The official MCP examples only write or search when the model calls the provider tools.
A plugin whose declared range misses your DSH release is refused at install time; dsh-memoryrouter 0.2.0 covers 0.2.1-rc.1 and later, 0.1.1 covers 0.1.x.

Pick a memory path that matches your DSH version

Check the host version before installing any bundle. DSH enforces plugin peer ranges, so a one-command install is only valid when the package admits your release.

1
Check the installed DeepSeek Harness version
Version check
```
dsh --version
```
2
For explicit local tools, apply one official MCP overlay
Run the patch command from a DeepSeek Harness source checkout, or copy that overlay into your own patch layer. The reference server uses a local JSONL graph and substring search, not semantic retrieval.
Official reference example
```
npm install --global @modelcontextprotocol/[email protected]
dsh web --patch "$PWD/apps/cli/config/examples/mcp-memory/mcp-reference-memory.cordis.yml"
```
3
For a hosted vault with automatic recall on DSH 0.2.x, install dsh-memoryrouter
Version 0.2.0 passes the DSH compatibility check on 0.2.1-rc.1 and later. Add your Memory Key to the profile patch (or export MEMORYROUTER_API_KEY), restart, then run the fresh-session recall test: teach a fact in one session and ask for it in a new one. On DSH 0.1.x, install [email protected] instead.
MemoryRouter plugin
```
dsh plugin --profile <your-profile> add dsh-memoryrouter
```
4
Add your Memory Key to the profile patch
Edit cordis.patch.yml in the profile directory under ~/.dsh/profiles. Without a key the plugin loads, logs one warning, and does nothing.
cordis.patch.yml
```
- id: memoryrouter
  config:
    apiKey: mk_your_key_here
```
5
Alternative: OpenViking for a self-hosted server
OpenViking declares support across the 0.x line from 0.1.0-rc.6 and documents automatic recall and capture against an OpenViking server you run. Confirm its latest verified-release list before installing.
OpenViking plugin
```
dsh plugin --profile <your-profile> add @openviking/dsh-memory-plugin
```

MemoryRouter gives a DSH profile a hosted vault that follows the same key across sessions, channels, machines, and connected tools, with no server to run. The plugin stores only the clean user message and final assistant reply; tool calls, reasoning, and injected context are filtered out.

Get a MemoryRouter key

Works with dsh-memoryrouter 0.2.0 on DSH 0.2.1-rc.1 and later. 14-day free trial.

OpenClaw memory

Workspace files plus the mr-memory plugin for sessions that keep their context.

Hermes Agent memory

Swap the memory provider to MemoryRouter with a published Python package.

Claude Code memory

Keep project decisions across sessions and compaction with the published hook package.

DeepSeek Harness memory FAQ

Does DeepSeek Harness have built-in memory?

Are the official DeepSeek Harness MCP memory examples ready to run?

Is dsh-memoryrouter an official DeepSeek Harness plugin?

Does dsh-memoryrouter support the latest DSH release?

Should I use a DSH memory plugin or an MCP memory server?

Does DSH compaction count as cross-session memory?

Does MemoryRouter memory follow a DSH profile across machines?

Sources

Sources checked 2026-11-02. Tool behavior changes; check the vendor docs before relying on a detail.