Mem0 SDK Updates Add Safer Cleanup for Superseded Agent Memories
Mem0's Python v2.0.4 and Node v3.0.5 SDK releases add linked-memory deletion controls so superseded agent memories do not resurface after cleanup.
What changed in Mem0's latest SDK releases
Mem0's latest Python and Node SDK releases add an explicit linked-memory cleanup option for agent memory stores. In Python v2.0.4, delete() and async delete() accept delete_linked; in Node v3.0.5, delete() accepts deleteLinked, serialized as delete_linked. The practical effect is that deleting a current memory can also remove older linked memories it superseded, reducing the chance that stale memories resurface later.
Key takeaways
- Mem0 Python SDK v2.0.4 adds
delete_linkedtodelete()and asyncdelete(), defaulting toFalse. - Mem0 Node SDK v3.0.5 adds a matching
deleteLinkedoption, serialized todelete_linkedfor the API. - The option deletes older superseded memories transitively along the v3 linked-memory chain when enabled.
- Releasebot independently lists both releases from May 27, 2026 and summarizes the same linked-memory cleanup behavior.
- This is most useful for long-running agents where outdated preferences, facts, or instructions can otherwise reappear after a newer memory is removed.
Practical LinkLoot angle
Agent memory is only useful if cleanup is predictable. If a memory system keeps older superseded records alive, deleting the visible current memory can accidentally restore outdated context. Mem0's new option gives developers a sharper cleanup decision: preserve history by default, or delete the linked chain when the user's intent is to remove the whole superseded memory trail.
| Cleanup route | Best use | Limitation to verify | Source |
|---|---|---|---|
delete() default | Remove the current memory while preserving linked history | Older superseded memories may still be available to future retrieval | Mem0 release notes |
delete(delete_linked=True) / deleteLinked: true | Remove current memory plus superseded linked memories | Requires confidence that the entire linked chain should be removed | Python and Node releases |
| Manual review queue | Sensitive memories, compliance deletes, user-requested erasure | Slower, but safer for regulated data | Practical workflow |
| Retention policy job | Scheduled cleanup of stale low-value memories | Needs audit logs and rollback strategy | Implementation alternative |
For production agents, treat this as a policy switch rather than just a convenience flag. A support bot deleting an outdated shipping preference may safely remove the chain; a compliance or legal assistant should probably log the chain, confirm the user intent, and only then use linked deletion.
What to verify before you act
Check which Mem0 SDK version your service actually runs, because the Python and Node options landed in separate release tags. Confirm how your application creates linked memories and whether linked deletion maps to user expectations in your product. For privacy-sensitive use cases, verify audit logging before using the transitive delete path, because the new option is designed to remove older superseded records, not merely hide them from retrieval.
Source check
The primary GitHub release for Mem0 Python SDK v2.0.4 confirms the new delete_linked option on delete() and async delete(). The Mem0 Node SDK v3.0.5 release confirms the JavaScript equivalent, deleteLinked, serialized as delete_linked. Releasebot's Mem0 feed corroborates both releases, dates, and the practical purpose: preventing superseded linked memories from resurfacing after deletion.
It lets a delete call remove older memories linked to the current memory, including superseded records in the v3 linked-memory chain.
For broader memory and agent-tool design patterns, see LinkLoot's guide to AI agent tools.