Highlights - Mem0 — ContextQMD

DeepSeek Harness: Mem0 as a Native Cordis Plugin

The DeepSeek Harness agent forgets everything between sessions. @mem0/dsh-mem0 gives it two Mem0-backed tools, so recall and writes persist across runs against the same memory bank you already use from Claude Code, Codex, and every other connected agent.

Two agent-callable tools: search_memory recalls facts relevant to a query, add_memory stores a fact for future sessions. Both accept per-call userId / agentId / runId scope overrides.
Native Cordis lifecycle: The plugin declares inject = ['tools'] so it waits for the harness tool registry, then registers through ctx.tools.register(). Unmounting the plugin removes the tools automatically.
Managed backend, not a memory file: Server-side extraction, semantic dedup, and conflict resolution, rather than a Markdown file the agent has to maintain itself.
Config: userId is required, apiKey defaults to $MEM0_API_KEY, and host optionally targets a dedicated Mem0 Platform base URL.

See DeepSeek Harness for setup and SDK & Tools for PR links.

<Note> Developer preview. Auto-capture and auto-recall, where memory reaches the context with no explicit tool call, are planned but not yet built. </Note> </Update> <Update label="2026-08-24" description="Strands Agents integration">

Strands Agents: Mem0 as a Native MemoryStore

strands-mem0 plugs Mem0 into AWS's Strands Agents SDK as a native MemoryStore, so recall and writes happen inside the agent loop rather than as tool calls the model has to remember to make.

Automatic recall: The MemoryManager drives the store on every turn, searching Mem0 and injecting the results into the prompt with no tool call required.
Server-side extraction: Because the store implements add_messages, enabling extraction routes raw conversation turns straight to Mem0's extraction pipeline, skipping the extra client-side model call needed to distill facts first.
Hosted or self-hosted: An API key targets the hosted Mem0 Platform; a config dict targets self-hosted Mem0 OSS.
Entity scoping: Accepts user_id, agent_id, run_id, and app_id, with at least one required and invalid combinations rejected at construction rather than on the first write.

See Strands Agents for setup and SDK & Tools for PR links.

</Update> <Update label="2026-08-13" description="Kimi Code plugin">

Kimi Code: Mem0 Joins the Editor Plugin Family

The shared Mem0 editor plugin now covers Kimi Code alongside Claude Code, Cursor, Codex, and Antigravity, running on the same scripts, skills, and memory bank, so context written in one editor is available in the others.

Hosted MCP server: Registers https://mcp.mem0.ai/mcp/, authenticated with MEM0_API_KEY as a bearer token.
Automatic capture and recall: SessionStart loads context through the context-loader skill, and hooks on prompt submit, file reads, Bash output, stop, and pre-compact capture and inject memory without an explicit tool call.
Guardrails: Direct Write / Edit / MultiEdit to memory files is blocked, and metadata defaults are enforced on every Mem0 MCP tool call.
Kimi hook adapter: A shim normalizes Kimi Code's hook contract to the shape the shared scripts already expect, resolving the real project directory and translating the differing prompt, tool-output, and MCP tool-name fields.

See SDK & Tools for version details and PR links.

</Update> <Update label="2026-07-30" description="n8n and Zapier integrations">

Workflow Automation: Mem0 Memory in n8n and Zapier

Mem0 now plugs into two no-code automation platforms, so workflows that used to start from zero on every run can store durable facts and recall them later.

n8n community node: @mem0/n8n-nodes-mem0 adds a Mem0 node with a Memory resource covering Add, Search, Get, Get Many, Update, and Delete. Install it from Settings → Community Nodes on a self-hosted instance, then connect your API key once as a Mem0 API credential. See n8n.
n8n AI Agent tool: Attach the same node to an AI Agent node and it becomes a tool the agent calls on its own, so it can decide when to remember and when to recall.
Zapier app: Add Memory, Search Memories, Get Memories, and Delete Memory actions let any of Zapier's thousands of apps write and read Mem0 context with no code and no server. See Zapier.
One-time connection: Both integrations authenticate with a single Mem0 API key and default to https://api.mem0.ai, with a configurable base URL for self-hosted deployments.

<Note> The Zapier app is not yet listed in Zapier's public App Directory. Email [[email protected]](mailto:[email protected]) for an invite link. </Note> </Update> <Update label="2026-07-13" description="TypeScript provider expansion">

TypeScript OSS SDK: 26 New Providers, Reranking, and Zero-Dependency Imports

TypeScript SDK v3.1.0 is the largest provider release for the OSS SDK so far, closing most of the remaining gap with the Python SDK. Python SDK v2.0.12 ships alongside it with fixes and security patches.

17 new vector stores: Pinecone, Weaviate, Milvus, Chroma, MongoDB, Elasticsearch, OpenSearch, Databricks, AWS Neptune Analytics, S3 Vectors, Azure MySQL, Google Vertex AI Vector Search, Turbopuffer, Upstash Vector, Valkey, Cassandra, and Baidu Mochow.
5 new LLM providers: AWS Bedrock, xAI Grok, Together, vLLM, and Sarvam.
4 new embedding providers: Vertex AI, HuggingFace, FastEmbed, and Together.
Reranking in TypeScript: Four rerankers (Cohere, ZeroEntropy, cross-encoder, and LLM-based) with per-search rerank via a rerank option on search().
Install only what you use: Importing mem0ai/oss no longer pulls in any provider SDK. Provider packages are resolved lazily on first use, so an app that configures only OpenAI and Qdrant does not need the other provider SDKs installed.

See SDK & Tools for version details and PR links.

</Update> <Update label="2026-06-27" description="SDK memory expiration">

SDK Memory Expiration: Expiring Memories Across Python and TypeScript

The latest SDK releases add first-class expiration controls to memory writes, updates, and reads, plus new TypeScript provider coverage for production deployments.

Python client updates: MemoryClient.update() and AsyncMemoryClient.update() now accept expiration_date, including None to clear an existing expiration.
TypeScript client updates: AddMemoryOptions, update(), and Memory now support expirationDate; search() and getAll() can include expired memories with showExpired.
New TypeScript LLM providers: MiniMaxLLM and LiteLLM are now available for OpenAI-compatible MiniMax and LiteLLM proxy deployments.
PGVector deployment flexibility: TypeScript PGVector config now supports connectionString and ssl, so apps can use a managed Postgres URI instead of separate connection fields.

See SDK & Tools for version details and PR links.

</Update> <Update label="2026-06-25" description="Mem0 Plugin v0.2.11">

Mem0 Plugin: Shared Memory for Claude Code, Cursor, Codex, and Antigravity

The shared Mem0 editor plugin is current through v0.2.11:

Automatic context injection: File reads, bash errors, session resume prompts, and startup timelines can retrieve relevant memories automatically.
Project and global scopes: Project-scoped memories remain the default, while global_search supports team-wide recall across users and app scopes.
Coding categories: A 17-category coding taxonomy installs in the background and is cached per Mem0 account.
Reliable capture: Auto-capture, compaction summaries, session summaries, and metadata defaults keep memories scoped and readable.
Editor correctness: Telemetry now reports Claude Code, Cursor, Codex, and Antigravity separately with each editor's real plugin version.

</Update> <Update label="2026-06-25" description="Antigravity Plugin v0.1.3">

Antigravity Plugin: Mem0 for Google Antigravity

Antigravity support in the shared Mem0 editor plugin family is current through v0.1.3:

Self-contained plugin: Includes its own plugin manifest, MCP config, hooks, shared scripts, and skills.
AGENTS.md convention: Uses Antigravity's contextFileName: "AGENTS.md" convention.
Lifecycle hooks: Wires session start, prompt recall, file-read context, memory-tool metadata enforcement, bash-error lookup, post-tool tracking, and stop summaries.
Shared memory layer: Reuses the Mem0 Platform MCP tools and the shared 16-skill command bundle.
Better automatic recall: v0.1.3 adds reranked injected context and clean files_touched metadata in session summaries.
Telemetry correctness: v0.1.2 reports Antigravity as antigravity with the plugin's own version.

</Update> <Update label="2026-06-22" description="OpenCode Plugin v0.2.0">

OpenCode Plugin: Native SDK Memory Tools for OpenCode

@mem0/opencode-plugin adds memory to OpenCode and is current through v0.2.0:

Native SDK tools: Memory tools register through @opencode-ai/plugin and call the mem0ai SDK directly, so the plugin no longer depends on mcp.mem0.ai.
Memory scopes: Operations support project, session, and global scope, with /mem0-scope to change the default.
Automatic context: File-context injection, structured compaction summaries, and a recent-activity timeline surface relevant memories without manual recall.
Auto-dream consolidation: Gated consolidation merges duplicates, drops stale or sensitive entries, and rewrites vague memories.
Skills load in place: The config hook adds bundled skills to skills.paths instead of copying them into user config directories.
Safety controls: Blocks MEMORY.md writes and redacts secrets before storing memories.

</Update> <Update label="2026-06-12" description="Pi Agent Plugin v0.1.2">

Pi Agent Plugin: Persistent Memory for Pi Agent

@mem0/pi-agent-plugin adds semantic memory to Pi Agent and has been updated through v0.1.2:

Agent memory tool: Registers mem0_memory for scoped search, add, get, delete, and delete-all operations.
Slash commands: Adds /mem0-remember, /mem0-search, /mem0-forget, /mem0-tour, /mem0-dream, /mem0-pin, /mem0-scope, and /mem0-status.
Auto-capture: Stores user and assistant memories after agent turns.
Dream consolidation: Merges duplicates, resolves contradictions, and prunes stale memories behind session, time, and memory-count gates.
Project scoping: Uses git-root detection for stable app_id values across monorepos.
Relevant command results: v0.1.2 adds visible command feedback and thresholded, reranked search for search, forget, and pin commands.

</Update> <Update label="2026-06-12" description="OpenClaw v1.0.13">

OpenClaw Plugin: Current Memory Backend for OpenClaw

@mem0/openclaw-mem0 is current through v1.0.13, with the original production-ready memory backend plus newer setup, security, and runtime work:

Skills-based memory architecture: Triage, recall, and dream skills handle extraction, recall, consolidation, and tool guidance.
Chat and CLI setup: Supports chat-based platform setup, openclaw mem0 init, direct API keys, email OTP, autonomous agent setup, and OSS onboarding.
Platform and OSS modes: Works with Mem0 Platform or self-hosted OSS providers including OpenAI, Anthropic, Ollama, Qdrant, and PGVector.
Agent-friendly CLI: All 16 CLI commands support --json for machine-driven setup and diagnostics.
Runtime integration: Exposes OpenClaw memory capability APIs for search manager and backend config status.
Security and compliance: Added path containment checks, sensitive config metadata, dependency overrides, telemetry hashing, and metadata-only registration safety.

</Update> <Update label="2026-06-10" description="Vercel AI SDK Provider v3.0.0">

Vercel AI SDK Provider: Memory-Augmented Generation for AI SDK v6

The Vercel AI SDK provider moved to the v6 provider contract and Mem0 v3 APIs:

AI SDK v6 support: Migrated to LanguageModelV3 / ProviderV3, including v3 stream lifecycle events and content arrays.
Mem0 v3 API support: Memory writes and searches now use /v3/memories/add/ and /v3/memories/search/.
Mem0 sources in responses: generateText and streamText responses include memories as sources with providerMetadata.mem0.memories.
Safer prompt handling: Prompts are cloned before memory injection, avoiding caller-side mutation.
Async storage fix: addMemories is awaited so generated memories are not silently dropped.
Raw memory utilities: Exports searchMemories, retrieveMemories, getMemories, and addMemories for apps that need direct memory control.
Deployment controls: Per-request mem0ApiKey and host support Mem0 Platform, custom API keys, and self-hosted API endpoints.

</Update> <Update label="2026-05-13" description="Temporal Reasoning for Mem0 Platform v3">

Temporal Reasoning: Time-Aware Retrieval for Platform v3

Mem0 Platform v3 can now interpret time-aware memories and queries so assistants retrieve the right information for questions about the past, upcoming plans, and current state.

Search intent parsing: Queries like last week, upcoming, right now, and as of March 2025 now resolve against memory timestamps automatically.
Default v3 behavior: No per-request toggle is needed for v3 writes or searches.
Deterministic testing: Pass reference_date to anchor relative phrases in tests, backfills, and demos.
Stable API shape: Temporal reasoning changes ranking, not the client response contract.

See Temporal Reasoning for usage details.

</Update> <Update label="2026-05-08" description="Memory Decay">

Memory Decay: Recently-Used Memories Surface Higher

Per-project search-time ranking bias that boosts recently-touched memories and gently dampens stale ones. Off by default; opt in per project via the decay field on the project endpoint, or via client.project.update(decay=True) in the SDKs (Python v2.0.2 / TypeScript v3.0.3).

Soft bias, never a filter. The scaling factor stays in 0.3×–1.5×. Decay can reorder candidates but never removes them; anything that surfaced before decay can still surface after.
Reinforcement loop. Every memory returned in a search has its access history updated, so frequently-used facts naturally float to the top over time.
Public score still clamped to [0, 1]. Existing API contract preserved; no client-side changes needed.
v3 search only, fully reversible. See Memory Decay docs.

</Update> <Update label="2026-04-14" description="Mem0 SDK v2.0.0 / v3.0.0">

New Memory Algorithm: State-of-the-Art Accuracy at ~3-4x Lower Cost

Ground-up rewrite of the memory pipeline with 20+ point benchmark improvements:

LoCoMo: 71.4 → 91.6 (+20) for multi-turn conversation recall.
LongMemEval: 67.8 → 93.4 (+26) for long-term memory across sessions.
BEAM (1M tokens): 64.1 on production-scale memory evaluation.
Agent memories: Assistant recall moves from 46% to 100%.
Temporal reasoning: "Where did I live before SF?" improves from 51% to 93%.
Lower token use: Retrieval stays under 7K tokens versus 25K+ for full-context approaches.
ADD-only extraction: Memories accumulate; nothing is overwritten or deleted.
Hybrid retrieval: Semantic search, BM25 keyword search, and entity boost are scored in parallel.
Graph memory (built-in): entities extracted, embedded, and linked across memories, with no external graph store required

Breaking changes: external graph stores removed from OSS (replaced by built-in graph memory), search() defaults changed, deprecated params removed. See migration guide.

</Update> <Update label="2026-04-06" description="Mem0 Skill Graph">

Mem0 Skill Graph: In-Context Documentation for AI Agents

AI coding agents in Claude Code, Cursor, and Codex can now access Mem0 knowledge directly in their workflow without leaving the editor. Three interconnected skills launched:

mem0 Core Skill: Python and TypeScript SDK reference, REST API patterns, and integration guides for LangChain, CrewAI, Autogen, and more.
mem0-cli Skill: Terminal command reference, configuration walkthroughs, and CI/CD recipes.
mem0-vercel-ai-sdk Skill: Vercel AI SDK provider API, memory-augmented generation patterns, and multi-provider setup.

</Update> <Update label="2026-04-06" description="Mem0 CLI v0.2.2">

Official Mem0 CLI: Now on PyPI and npm

A full-featured command-line interface for Mem0, available in both Python and Node.js:

Install: pip install mem0-cli or npm install -g @mem0/cli
Full command suite: add, search, list, get, update, delete, import, config, init, status, entity, event.
Interactive setup: mem0 init supports email verification and direct API key entry.
Runtime coverage: Works with Mem0 Platform and self-hosted OSS modes.
Automation support: Use --json for CI/CD pipelines and agent workflows.
Dual implementation: Same commands and behavior across Python and Node.js.

</Update> <Update label="2026-03-21" description="New Providers">

Apache AGE, Turbopuffer, MiniMax, and pgvector for Node.js

Major expansion of the provider ecosystem:

Apache AGE: New graph store support, bringing the total to 4 graph store backends (Neo4j, Memgraph, Kuzu, Apache AGE). Note: All external graph store backends (Neo4j, Memgraph, Kuzu, Apache AGE) were subsequently removed in v2.0.0 (2026-04-14). Graph memory is now built-in entity linking with no external graph store required; see the v2.0.0 entry above.
Turbopuffer: New vector database provider for Python SDK.
MiniMax: New LLM provider with dedicated AWS Bedrock support.
pgvector for Node.js: PostgreSQL vector support added to the TypeScript OSS SDK.
Reasoning models: reasoning_effort parameter for OpenAI o1/o3-style models.

</Update> <Update label="2026-03-14" description="Mem0 Platform Skill">

Mem0 Platform Skill on skills.sh

First skill launch: a dedicated Mem0 skill providing platform API reference, quickstart patterns, and integration examples directly inside agent sessions. Available on skills.sh for any compatible AI coding agent.

</Update>