Mem0 Python SDK (v2.2.1)
Mem0 releases published Mem0 Python SDK (v2.2.1). 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…
Why this signal matters
Mem0 releases published Mem0 Python SDK (v2.2.1). This release-watch entry was generated from the project's official GitHub release feed and is kept separate from human-reviewed editorial analysis. 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 (https://github.com/mem0ai/mem0/pull/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 (https://github.com/mem0ai/mem0/pull/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…
Actionable summary
Treat Mem0 Python SDK (v2.2.1) as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.
- Agent usefulness
- 82/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Review the official Mem0 releases release notes before upgrading.
- Check compatibility, migration, and security notes against your current agent stack.
- Run focused regression tests before production rollout.