Apache-2.0 memory OS for LLM agents; plugs into DeepSeek Harness via an official local plugin (100% on-device SQLite) or a managed cloud plugin with automatic recall before tasks and capture after turns.
DSH integration
Compatible
Author-claimed
Safety audit
Unaudited
Last verified
2026-08-21
License
Apache-2.0
01What can it help you accomplish?
Give DeepSeek Harness sessions persistent, self-evolving agent memory
Automatic recall of relevant context before the first model step of each request, and automatic saving of new user/assistant messages back to memory after a successful turn — without modifying DSH's core
Developers running DeepSeek Harness (dsh) who want their agent to remember context and grow across sessions
Keep all agent memory 100% on-device
Local-first memory with hybrid retrieval (FTS5 + vector), smart dedup, tiered skill evolution (L1 traces / L2 policies / L3 world model), multi-agent collaboration, SQLite storage and a Memory Viewer dashboard
Privacy-sensitive developers and teams who want agent memory in DeepSeek Harness, Hermes or OpenClaw with nothing leaving their machine
02How to install into DeepSeek Harness
Prerequisites
- Local plugin: Node.js and an already-installed DeepSeek Harness (dsh), OpenClaw, or Hermes
- Cloud plugin: a MemOS Cloud API key (starts with `mpg-`) created on the MemOS dashboard
Installation steps
- 01
Local plugin (macOS / Linux) for DeepSeek Harness: `curl -fsSL https://raw.githubusercontent.com/MemTensor/MemOS/main/apps/memos-local-plugin/install.sh | bash -s -- --agent dsh --profile web` — the installer deploys MemOS as an out-of-tree DSH bundle
$ curl -fsSL https://raw.githubusercontent.com/MemTensor/MemOS/main/apps/memos-local-plugin/install.sh | bash -s -- --agent dsh --profile web
- 02
Local plugin (Windows PowerShell): `irm https://raw.githubusercontent.com/MemTensor/MemOS/main/apps/memos-local-plugin/install.ps1 -OutFile "$env:TEMP\memos-install.ps1"; powershell -ExecutionPolicy Bypass -File "$env:TEMP\memos-install.ps1"`
- 03
Cloud plugin: create a MemOS API Key on the MemOS dashboard, then install into the default DSH `web` profile: `npx @deepseek-ai/dsh plugin --profile web add @memtensor/memos-cloud-dsh-plugin@latest`
$ npx @deepseek-ai/dsh plugin --profile web add @memtensor/memos-cloud-dsh-plugin@latest
- 04
Cloud plugin: add `MEMOS_API_KEY: mpg-your-key` to `~/.dsh/.credentials.yaml`
- 05
Cloud plugin: add the minimal plugin configuration to `~/.dsh/settings.yaml`: `memos-cloud:` with `apiKeyEnv: MEMOS_API_KEY`
- 06
Cloud plugin: restart the DSH Web profile: `npx @deepseek-ai/dsh web`
$ npx @deepseek-ai/dsh web
Verify the integration
Not specified by the author
03DSH integration and capability boundaries
Official memory plugin installed inside DeepSeek Harness via DSH's native plugin mechanism (cloud plugin via `dsh plugin add`, local plugin as an out-of-tree DSH bundle)
Automatic recall & capture for DeepSeek Harness
DSH user requests and completed turns→Relevant memories recalled before the first model step; new user and assistant messages saved after a successful turn
Cloud plugin sends conversation messages to MemOS Cloud and requires a MemOS API keyLocal-first hybrid memory (memos-local-plugin)
Agent conversations and task traces from DeepSeek Harness, Hermes or OpenClaw→Hybrid retrieval (FTS5 + vector), smart dedup, tiered skill evolution (L1 traces / L2 policies / L3 world model), multi-agent collaboration, Memory Viewer dashboard
Writes a local SQLite database on your machineSelf-hosted MemOS REST service
Docker Compose deployment (MemOS API + Neo4j + Qdrant) or uvicorn without Docker→Memory API served at `http://localhost:8000` — create cubes, add memories, search memories
Requires Neo4j and Qdrant infrastructure; `.env` must be filled with LLM/embedder API keys
04Who is it for? When not to use it?
Good for
- Developers running DeepSeek Harness (dsh) who want their agent to remember context and grow across sessions
- Privacy-sensitive developers and teams who want agent memory in DeepSeek Harness, Hermes or OpenClaw with nothing leaving their machine
Not for
- The cloud plugin stores memories on MemOS Cloud and requires a MemOS API key plus network access; it is fail-open, so a temporary outage does not interrupt the current DSH task, but recall/capture is unavailable while offline.
- The full self-hosted MemOS service needs Neo4j and Qdrant infrastructure (and LLM/embedder API keys in `.env`); only the local plugin runs with no infra on local SQLite.
05Compatibility, maintenance and safety notes
- The cloud plugin stores memories on MemOS Cloud and requires a MemOS API key plus network access; it is fail-open, so a temporary outage does not interrupt the current DSH task, but recall/capture is unavailable while offline.
- The local plugin installer requires Node.js and an already-installed DeepSeek Harness (or OpenClaw / Hermes); for DSH it deploys MemOS as an out-of-tree bundle, so a working dsh installation is mandatory first.
- The full self-hosted MemOS service needs Neo4j and Qdrant infrastructure (and LLM/embedder API keys in `.env`); only the local plugin runs with no infra on local SQLite.
Apache-2.0 · actively maintained (latest release memos-local-plugin-v2.0.16, 2026-08-16)
06Frequently asked questions
How do I connect MemOS to DeepSeek Harness?
Two official ways. Local plugin: run the one-line install script with `--agent dsh --profile web` (macOS / Linux) or the PowerShell installer (Windows) — MemOS is deployed as an out-of-tree DSH bundle. Cloud plugin: `npx @deepseek-ai/dsh plugin --profile web add @memtensor/memos-cloud-dsh-plugin@latest`, then add `MEMOS_API_KEY` to `~/.dsh/.credentials.yaml` and the `memos-cloud` config to `~/.dsh/settings.yaml`, and restart with `npx @deepseek-ai/dsh web`.
Is it a native DSH plugin or MCP?
It connects through DeepSeek Harness's native plugin mechanism — the README explicitly says DSH is connected to MemOS Cloud 'through its native plugin mechanism', not via MCP.
What are the prerequisites?
For the local plugin: Node.js and an already-installed DeepSeek Harness. For the cloud plugin: a MemOS API key created on the MemOS dashboard (keys start with `mpg-`).
Where does my memory data go?
The local plugin is 100% on-device — local-first SQLite storage, nothing leaves your machine. The cloud plugin saves memories to MemOS Cloud, the hosted service.
What happens if MemOS Cloud is down?
The cloud plugin is fail-open: a temporary MemOS Cloud outage does not interrupt the current DSH task.
07Related DSH workflows
dsh-anchored-standard
by xiaobright
Two-phase DeepSeek Harness preset: Minimal-aligned bootstrap, then full Standard tools (Project2 98/99)
mem9
by mem9-ai
Unlimited memory for OpenClaw
mindmemos
by mindscale-noah
Gives dsh agents persistent cross-session memory: auto-recalls relevant user/task context before each turn and writes back lessons after each turn, evolving memory via schema learning and skill distillation
dsh-mnemon
by omdsh-dev
Composable, view-based memory for DeepSeek Harness. Pluggable sources and strategies, with three-tier memory out of the box.
08Data and sources
Add automatic recall, background capture, hybrid retrieval, and a local Memory Viewer to DeepSeek Harness—powered by the…
Connect DeepSeek Harness to MemOS Cloud through its native plugin mechanism.
MemOS now brings persistent memory to **DeepSeek Harness** through both local and cloud plugins.
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-08-21. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.