mem0 Release Notes

Bug Fixes:

• Core: add() (Memory and AsyncMemory) no longer reports records the vector store rejected as successful ADD events. Only records that were actually inserted are written to history, entity-linked, and returned. If none of the extracted memories could be inserted, add() now raises VectorStoreError instead of returning memories that were never stored (#7066)
• Core: Restore the context-manager protocol on Memory (with Memory() as m:) and AsyncMemory (async with AsyncMemory() as m:), which closes the instance on exit (#7354)
• LLMs: The AWS Bedrock Anthropic path now returns the first Converse content block that carries text instead of always reading content[0]. Claude reasoning models can emit a reasoningContent block before the text block, which previously made the call fail with a KeyError (#6369)
• Vector Stores: Turbopuffer filters now apply every operator (eq, ne, gt, gte, lt, lte, in, nin). Only gte and lte were read before, so any other operator was silently dropped and the query returned unfiltered results. An unsupported operator now raises ValueError (#6564) …

Bug Fixes:

• Config (OSS): ConfigManager no longer injects OpenAI's default baseURL and model into non-OpenAI LLM providers. The defaults now apply only to openai and openai_structured, so a DeepSeek, xAI, or other provider config without an explicit baseURL or model falls back to that provider's own defaults and env vars (DEEPSEEK_API_BASE, XAI_API_BASE, ...) instead of pointing at OpenAI with an OpenAI model name (#7350)
• Vector Stores: Turbopuffer filters now apply every operator (eq, ne, gt, gte, lt, lte, in, nin). Only the range operators were read before, so eq, ne, in, and nin were silently dropped. A "*" value now matches anything instead of nothing, an array value is treated as in, and an unsupported operator throws (#6578)
• Vector Stores: Turbopuffer search() with euclidean_squared now maps the unbounded squared distance to 1 / (1 + distance) instead of 1 - distance, which went negative and inverted ranking for any distance above 1 (#6580) …

New Features:

• Client: Add User Profiles to MemoryClient and AsyncMemoryClient: get_profile(), generate_profile(), get_profile_settings(), update_profile_settings(), sample_profiles(), and get_profile_job(). A profile is a structured, always-current JSON summary of one user, shaped by a JSON Schema you configure per project and filled by an LLM from that user's memories. Generation is asynchronous. Every job POST carries an Idempotency-Key; to retry a lost request without starting a second job, pass the same idempotency_key on each attempt (#7340)

Bug Fixes:

• Vector Stores: Guard against None timestamps in the Valkey vector store's insert() and update() paths. created_at and updated_at fields that were present in the payload but set to None previously passed the "created_at" not in payload / "updated_at" in payload checks and raised TypeError when datetime.fromisoformat() received None. Both paths now use .get() with a truthiness check so None values fall through to the default, matching the Redis provider's behavior (#6993)

New Features:

• Client: Add User Profiles to MemoryClient: getProfile(), generateProfile(), getProfileSettings(), updateProfileSettings(), sampleProfiles(), and getProfileJob(). A profile is a structured, always-current JSON summary of one user, shaped by a JSON Schema you configure per project and filled by an LLM from that user's memories. Generation is asynchronous. Every job POST carries an Idempotency-Key; to retry a lost request without starting a second job, pass the same idempotencyKey on each attempt (#7340)

Improvements:

• Search: The memory policy, mem0_memory tool description, and prompt guidelines no longer ask the agent to search before answering anything that may depend on earlier context or to run several searches per question. They now ask for a search before repeating investigation or when earlier decisions, fixes, commands, or results may help (#7420)
• Skills: context-loader makes one search instead of 2-4 parallel searches, and uses the search skill description from the other coding-agent plugins (#7420)
• Automatic recall: Injected memories are introduced as "Mem0 found these relevant memories from earlier work in this repository:", the same heading as the Python plugins. The old heading called them a shallow first pass and told the agent to search again (#7420)

Improvements:

• Search: The search_memories tool description no longer asks the agent to search proactively or to run several searches for multi-part questions. It now asks for a search before repeating investigation or when earlier decisions, fixes, commands, or results may help, the same wording as the other coding-agent plugins (#7420)
• Session context: Removed two system-context lines that told the agent to run 2 parallel searches before responding and 2-4 parallel searches for non-trivial tasks (#7420)
• Skills: /mem0-search and /mem0-context-loader make one search_memories call instead of 2 and 2-4 parallel calls. /mem0-context-loader now uses the search skill description from the other coding-agent plugins instead of asking to load at every new task or context switch (#7420)

Improvements:

• Search: The search_memory tool description no longer asks the agent to search proactively before answering anything that may depend on earlier context. It now asks for a search before repeating investigation or when earlier decisions, fixes, commands, or results may help (#7420)
• Automatic recall: Injected memories are introduced as "Mem0 found these relevant memories from earlier work:". The old heading called them a shallow first pass and told the agent to search again with mem0_memory, a tool DeepSeek does not have (#7420)

Improvements:

• Client: Requests now carry three surface-identity headers so the platform can tell which product made a call. X-Mem0-Source names the surface and X-Application the host app it runs inside, both set-once so a wrapper that already declared its identity keeps it. X-Mem0-Client is append-only and carries name/version per layer, outermost first, so a plugin calling this SDK reports the whole chain rather than only the last speaker. MEM0_SOURCE, MEM0_APPLICATION and MEM0_CLIENT_STACK set them from the environment for wrappers that cannot pass options (#7326)
• Client: The client stack is bounded by dropping whole entries rather than slicing characters, and this SDK's own entry is the reserved one. Truncating the joined string could sever an identifier mid-name and the platform parsed the fragment as a real client (#7326)

Improvements:

• Client: Requests now carry X-Mem0-Source, X-Application and X-Mem0-Client, matching the Python SDK. The first two are set-once so an outer wrapper keeps its identity; the third is append-only and reports the whole layer chain. Read from MEM0_SOURCE, MEM0_APPLICATION and MEM0_CLIENT_STACK when set (#7326)
• Client: The SDK version in X-Mem0-Client is injected at build time rather than hardcoded, so it cannot go stale at the next release (#7326)

Changes:

• Telemetry: The PostHog source tag changed from the literal "plugin" to OPENCODE_PLUGIN, and project_hash is now salted. Saved PostHog insights filtering on source = "plugin" will stop matching new events; historical data is unaffected (#7322)
• Config: A new keyFingerprint key appears in the install-count deduplication logic; installs are now counted once per key rather than on every activation (#7325)

Changes:

• Config: Added keyFingerprint to the config schema for install-count deduplication; installs are now counted once per key rather than on every activation (#7325)
• Telemetry: Events are no longer delivered twice, and the plugin_version field now reflects the plugin that produced the event (#7323, #7324, #7358)

Changed:

• Reuses shared conversation preparation, memory formatting, project/session/global scope utilities, and telemetry while preserving Pi's native extension API and @mem0/pi-agent-plugin package name.
• Pi loads the built dist/entry.js extension instead of executing source TypeScript from an installed package. Builds also publish the library entry point and declarations.

Removed:

• Removed Dream consolidation and pin commands, skills, configuration, types, and exports. The remaining commands are remember, search, forget, tour, scope, and status. Update integrations that import removed APIs or invoke removed commands.

Fixes:

• Global memory tool scope requires the user to select /mem0-scope global or configure a global default first. Empty and wildcard identities are rejected.
• Memory update and delete accept the mem0:<uuid> and [mem0:<uuid>] citations displayed in tool results, as well as raw IDs.
• Shared capture preparation filters conversation roles and redacts content; telemetry removes sensitive keys inside nested structures.

#7203

Changed:

• Moved the source from integrations/mem0-plugin/.opencode-plugin/ to integrations/opencode-plugin/, retaining the @mem0/opencode-plugin package name and native OpenCode hooks.
• Reuses shared conversation preparation, redaction, scoping, and telemetry. Builds a self-contained Bun/ESM dist/index.js and publishes its TypeScript entry declaration.
• Global memory tool scope requires the user to enable it in plugin settings first; empty and wildcard identities are rejected.
• Retains the seven commands for context loading, search, remember, forget, scope, status, and tour; bundled skills continue loading through OpenCode's native configuration.

Removed:

• Removed auto-Dream consolidation, its gates and state handling, and the Dream and pin skills/commands. Existing configurations and workflows that use these features must be updated.

Builds:

• Updated build and publish paths for the relocated source directory; the existing release tag prefix and publishing workflow filename are unchanged.

#7203

Changed:

• Reuses shared conversation preparation, redaction, and telemetry while retaining OpenClaw's native memory backend, tools, CLI, and Platform/OSS modes.
• Continues to publish a self-contained ESM package under @mem0/openclaw-mem0; the plugin manifest and package version now agree.

Removed:

• Removed Dream consolidation: automatic scheduling and locking, openclaw mem0 dream, Dream configuration, the memory-dream skill, and Dream-state public artifacts. Triage, recall, and memory/entity artifacts remain available. Update configurations or integrations that use the removed Dream surface.

Fixes:

• openclaw mem0 status handles an unconfigured installation without crashing and directs users to setup.
• Removed OpenClaw's separate 2,000-character extraction cutoff. Selected user and assistant messages retain their full redacted text; recent-message selection, earlier summary selection, and noise filtering still apply.
• Telemetry removes sensitive properties recursively and uses the shared failure-safe delivery implementation.

#7203