Mem0 DeepSeek Plugin (v0.1.0)
- New @mem0/deepseek-plugin package, a native DeepSeek Harness (Cordis) plugin that registers Mem0 as two agent-callable tools
- search_memory tool that recalls facts relevant to a query with optional limit (default 10) and per-call userId, agentId, or runId scope overrides
- add_memory tool that stores a fact for future sessions tagged source: DEEPSEEK_HARNESS with asynchronous server-side extraction
- Cordis lifecycle support with apply(ctx, config) that declares inject = ['tools'] and registers both tools via ctx.tools.register() for automatic unregistration on plugin unmount
- Configuration options with required userId, apiKey defaulting to $MEM0_API_KEY environment variable, and optional host parameter for dedicated Mem0 Platform base URL
From Mem0
Initial release of @mem0/deepseek-plugin, a native DeepSeek Harness (Cordis) plugin that registers Mem0 as two agent-callable
tools (#7027)
New Features:
-
search_memory: Recalls facts relevant to a query, with an optionallimit(default 10) and per-calluserId/agentId/runIdscope overrides. -
add_memory: Stores a fact for future sessions, taggedsource: "DEEPSEEK_HARNESS"for backend attribution; extraction runs asynchronously server-side, so a stored fact may take a moment to become searchable. -
Cordis lifecycle:
apply(ctx, config)declaresinject = ['tools'], so the plugin waits for the harness tool registry to exist, and both tools are registered viactx.tools.register()so they auto-unregister when the plugin unmounts. -
Config:
userIdis required;apiKeydefaults to$MEM0_API_KEY;hostoptionally points at a dedicated Mem0 Platform base URL (not a switch to self-hosted Mem0 OSS).Developer preview: auto-capture and auto-recall (memory injected into context automatically, without an explicit tool call) are planned but not yet built. The backend's
KNOWN_EVENT_SOURCESallowlist also needs"DEEPSEEK_HARNESS"added before usage surfaces by name in telemetry rather than bucketing into "OTHERS". See DeepSeek Harness for setup.