Apache-2.0 的持久 agent memory 服务器，为 DeepSeek Harness 提供原生 DSH/Cordis 集成包，可托管可自托管，支持多运行时共享记忆与混合检索。
DSH 适配
原生运行时
作者声明
安全审计
未审计
最后核验
2026-08-21
许可证
Apache-2.0
01它能帮你完成什么？
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
02如何接入 DeepSeek Harness？
前置条件
- 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)
安装步骤
- 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
验证接入成功
作者未说明
03DSH 适配与能力边界
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
04适合谁？何时不该用？
适合
- 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
不适合
- 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.
05兼容性、维护与安全提示
- 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)
06常见问题
如何把 mem9 接入 DeepSeek Harness？
mem9 提供原生 DSH/Cordis 集成包，内置召回、智能写入和记忆工具。按 dsh-plugin/README.md 中的 DeepSeek Harness 指南安装，然后把 MEM9_API_URL 和 MEM9_API_KEY 指向托管 API 或你的自托管服务器即可。
必须自托管 mem9 服务器吗？
不必。最快的方式是直接使用托管 API（https://api.mem9.ai）。自托管同样完整支持：应用对应后端的控制面 schema（TiDB、PostgreSQL 或 db9），再用 MNEMO_DSN 启动 mnemo-server。两者 API 契约一致，以后切换只需改 base URL 和凭证。
我的 agent memory 存在哪里？
存在 MEM9_API_URL 指向的 mem9 空间里：托管 API 基于 TiDB Cloud Starter；自托管时则存在你自己的数据库。记忆的写入、搜索、更新和删除都通过 mem9 服务器 API 完成。
多个智能体可以共享同一份记忆吗？
可以。一个空间可同时服务 OpenClaw、Hermes Agent、Claude Code、OpenCode、Codex、DeepSeek Harness、Dify 应用和自定义客户端，所有运行时都能召回同一批事实。设置 X-Mnemo-Agent-Id 可以区分共享空间内的写入来源。
07相关的 DSH 工作流
memos
作者 memtensor
面向 LLM 与 AI 智能体的自进化记忆系统，提供超持久记忆、混合检索与跨任务技能复用，可显著节省 Token。
dsh-anchored-standard
作者 xiaobright
DeepSeek Harness 两阶段预设：先最小对齐引导，再启用完整标准工具集。
dsh-infinite-gen-3
作者 minglink
DeepSeek v4 Pro 网络安全红队工具（无限三代） — jailbreak prompts and test suite for DeepSeek 求 Star 收藏 ⭐
mindmemos
作者 mindscale-noah
为 DSH 智能体提供跨会话持久记忆，每轮自动召回相关上下文并回写经验，通过模式学习与技能蒸馏持续进化。
08数据与来源
| 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.
页面基于项目公开文档、仓库元数据和 DSH Plugins 的结构化解析生成；最后核验于 2026-08-21。发现错误？提交更正。
最佳 DeepSeek Harness 插件
从全目录挑出的 12 个值得优先安装的插件，覆盖各个分类。