deepseek-plugin-v0.1.0

mem0ai/mem0deepseek-plugin-v0.1.0Aug 24, 2026by kartik-mem0

AI Summary

Initial release of the DeepSeek Harness plugin, registering Mem0 as two agent-callable tools for memory retrieval and storage.

Key Highlights

New DeepSeek native plugin integration
Two tools: `search_memory` and `add_memory`
Server-side async extraction for stored facts
Configurable `userId` and optional `apiKey`

New Features

DeepSeek Harness Plugin
Search Memory Tool
Add Memory Tool

Full Release Notes

**Initial release** of [`@mem0/deepseek-plugin`](https://www.npmjs.com/package/@mem0/deepseek-plugin), a native DeepSeek Harness (Cordis) plugin that registers Mem0 as two agent-callable
  tools ([#7027](https://github.com/mem0ai/mem0/pull/7027))

  **New Features:**
  - **`search_memory`:** Recalls facts relevant to a query, with an optional `limit` (default 10) and per-call `userId` / `agentId` / `runId` scope overrides.
  - **`add_memory`:** Stores a fact for future sessions, tagged `source: "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)` declares `inject = ['tools']`, so the plugin waits for the harness tool registry to exist, and both tools are registered via
  `ctx.tools.register()` so they auto-unregister when the plugin unmounts.
  - **Config:** `userId` is required; `apiKey` defaults to `$MEM0_API_KEY`; `host` optionally 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_SOURCES` allowlist also needs `"DEEPSEEK_HARNESS"` added before usage surfaces by name in telemetry rather than bucketing into "OTHERS". See [DeepSeek
  Harness](/integrations/deepseek-plugin) for setup.