@mem0/dsh-mem0. The Harness agent forgets everything between sessions. This plugin gives it two Mem0-backed tools so recall and writes persist across runs, sharing the same memory bank you already use from Claude Code, Codex, and other agents.
Overview
The plugin registers two agent-callable tools:
Unlike file-based memory plugins, Mem0 is a managed backend: server-side extraction, semantic dedup, and conflict resolution, with the same memory reusable across every agent you connect.
How it works
A Cordis plugin is a module exportingapply(ctx, config). This one declares inject = ['tools'] so it waits for the harness tool registry, then registers the two tools via ctx.tools.register(...). When the plugin unmounts, the tools are removed automatically (Cordis revertible effects).
Prerequisites
-
A Mem0 Platform account and API key:
- Sign up at app.mem0.ai
- Get your API key (starts with
m0-)
- The DeepSeek Harness installed.
- Your API key exported in your shell:
Try it locally
-
Build the plugin:
-
Point the Harness at it. Copy
cordis.example.yml, set the absolute path todist/index.jsand youruserId, then load it: - Open the web UI and ask the agent to remember something, then recall it in a later turn.
cordis.yml entry looks like this:
config.host at that base URL (defaults to api.mem0.ai). host is a Platform base-URL override, not a switch to self-hosted Mem0 OSS.
Configuration
Both tools also accept optional per-call
userId, agentId, and runId params so a single install can partition memory by entity, agent, or session; when omitted they fall back to the configured userId.
Telemetry
Writes are taggedsource="DEEPSEEK_HARNESS" so Mem0’s backend can attribute usage to this integration.