Apache-2.0 persistent agent memory server with a native DeepSeek Harness (DSH/Cordis) bundle — hosted API or self-hosted, shared across runtimes, with hybrid recall and a visual dashboard.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-08-21
License
Apache-2.0
01What can it help you accomplish?
Give DeepSeek Harness agents persistent memory across sessions and machines
Recall, smart ingest, and memory tools that store, search, get, update, and delete memories against the mem9 server, so agent context survives restarts, laptop switches, and long-running projects
DeepSeek Harness (dsh) users whose agents lose context between sessions
Share one agent memory layer across multiple runtimes and workflow platforms
A single mem9 space that DeepSeek Harness, OpenClaw, Claude Code, OpenCode, Codex, Dify apps, and custom HTTP clients read and write together via the same store/search/get/update/delete API
Teams running multi-agent workflows across different agent runtimes who want one shared memory instead of separate local notebooks
02How to install into DeepSeek Harness
Prerequisites
- A mem9 endpoint — the hosted API at https://api.mem9.ai, or a self-hosted mnemo-server backed by TiDB, PostgreSQL, or db9
- A mem9 API key for your space (returned or configured by your provisioning flow)
Installation steps
- 01
Choose your mem9 endpoint: use the hosted API (https://api.mem9.ai), or self-host by applying the matching control-plane schema and starting mnemo-server with MNEMO_DSN
- 02
Follow the DeepSeek Harness integration guide in dsh-plugin/README.md to install the native DSH/Cordis bundle
- 03
Set your credentials: export MEM9_API_URL (hosted or self-hosted server URL) and export MEM9_API_KEY
Verify the integration
Not specified by the author
03DSH integration and capability boundaries
Native DSH/Cordis bundle with recall, smart ingest, and memory tools, backed by the mem9 memory server (hosted API or self-hosted)
Persistent memory across sessions and machines
agent conversations and durable facts→memories that survive restarts, laptop switches, and long-running projects
memories are written to the mem9 server (hosted API or self-hosted database), not kept purely localShared multi-agent memory space
one mem9 space with an X-API-Key (optionally X-Mnemo-Agent-Id per agent)→store, search, get, update, and delete operations shared across OpenClaw, Hermes Agent, Claude Code, OpenCode, Codex, DeepSeek Harness, Dify and custom clients
all connected runtimes read and write the same memory spaceHybrid recall and visual dashboard
natural-language queries against the memory space→semantic search, keyword search, and inspection workflows in one system, plus a dashboard to inspect and manage memory
Hosted or self-hosted deployment
the hosted mem9 API (https://api.mem9.ai), or self-hosted mnemo-server on tidb / postgres / db9→the same API contract either way — switching deployment is a base-URL and credential change, not a plugin rewrite
self-hosting requires applying the control-plane schema and running mnemo-server with MNEMO_DSN
04Who is it for? When not to use it?
Good for
- DeepSeek Harness (dsh) users whose agents lose context between sessions
- Teams running multi-agent workflows across different agent runtimes who want one shared memory instead of separate local notebooks
Not for
- mem9 is not a purely local plugin — it requires a running mem9 endpoint, either the hosted API at https://api.mem9.ai or a self-hosted mnemo-server with a TiDB, PostgreSQL, or db9 backend and the matching control-plane schema applied.
- Memory recall and ingest are server-side operations sent over the network: with the hosted API, memories live in mem9's TiDB Cloud Starter-based service, so sensitive context may leave the local machine unless you self-host.
05Compatibility, maintenance and safety notes
- mem9 is not a purely local plugin — it requires a running mem9 endpoint, either the hosted API at https://api.mem9.ai or a self-hosted mnemo-server with a TiDB, PostgreSQL, or db9 backend and the matching control-plane schema applied.
- Memory recall and ingest are server-side operations sent over the network: with the hosted API, memories live in mem9's TiDB Cloud Starter-based service, so sensitive context may leave the local machine unless you self-host.
- Self-hosted smart ingest depends on an LLM provider API key (MNEMO_LLM_API_KEY); without it, ingest silently falls back to raw ingest behavior, which may lower memory quality.
Apache-2.0 · actively maintained (last push 2026-08-19)
06Frequently asked questions
How do I connect mem9 to DeepSeek Harness?
mem9 ships a native DSH/Cordis bundle with recall, smart ingest, and memory tools. Follow the DeepSeek Harness guide in dsh-plugin/README.md, then point MEM9_API_URL and MEM9_API_KEY at the hosted API or your self-hosted server.
Do I have to self-host the mem9 server?
No. The fastest path is the hosted API at https://api.mem9.ai. Self-hosting is fully supported too: apply the matching control-plane schema (TiDB, PostgreSQL, or db9) and start mnemo-server with MNEMO_DSN. Both expose the same API contract, so switching later is only a base-URL and credential change.
Where is my agent memory stored?
In the mem9 space your MEM9_API_URL points at: the hosted mem9 API (built on TiDB Cloud Starter) or your own database when self-hosting. Memories are stored, searched, updated, and deleted through the mem9 server API.
Can multiple agents share the same memory?
Yes. One space can serve OpenClaw, Hermes Agent, Claude Code, OpenCode, Codex, DeepSeek Harness, Dify apps, and custom clients together, so all runtimes recall the same facts. Set X-Mnemo-Agent-Id to distinguish which agent writes inside a shared space.
07Related DSH workflows
memos
by memtensor
Self-evolving memory OS for LLM & AI Agents: ultra-persistent memory, hybrid-retrieval, and cross-task skill reuse, with 35.24% token savings and DeepSeek Harness support.
dsh-anchored-standard
by xiaobright
Two-phase DeepSeek Harness preset: Minimal-aligned bootstrap, then full Standard tools (Project2 98/99)
dsh-infinite-gen-3
by 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.
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
08Data and sources
| DeepSeek Harness | Native DSH/Cordis bundle with recall, smart ingest, and memory tools | [`dsh-plugin/README.md`](dsh…
Hermes Agent, Claude Code, OpenCode, Codex, DeepSeek Harness, and Dify guides are below.
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.