mem0ai breaking changes
Every breaking API change we have recorded in mem0ai on npm: 86 breaking changes in 1 version. Below are its newest version, removals and renames first, each with its source.
Newest change April 16, 2026
On this page
3.0.0
- Removed
FeedbackPayload.feedback_reason
FeedbackPayload.feedback_reason was removed in mem0ai 3.0.0 npmjs.com - Removed
FeedbackPayload.memory_id
FeedbackPayload.memory_id was removed in mem0ai 3.0.0 npmjs.com - Removed
Memory.agent_id
Memory.agent_id was removed in mem0ai 3.0.0 npmjs.com - Removed
Memory.app_id
Memory.app_id was removed in mem0ai 3.0.0 npmjs.com - Removed
Memory.created_at
Memory.created_at was removed in mem0ai 3.0.0 npmjs.com - Removed
Memory.memory_type
Memory.memory_type was removed in mem0ai 3.0.0 npmjs.com - Removed
Memory.run_id
Memory.run_id was removed in mem0ai 3.0.0 npmjs.com - Removed
Memory.updated_at
Memory.updated_at was removed in mem0ai 3.0.0 npmjs.com - Removed
Memory.user_id
Memory.user_id was removed in mem0ai 3.0.0 npmjs.com - Removed
MemoryClient._validateOrgProject
MemoryClient._validateOrgProject was removed in mem0ai 3.0.0 npmjs.com
And 76 more in this version.
Check your code
These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.
Put your code on continuous management.
Scan a public repository now, or give your agent one line.
See how out of date your code is.
Tell your agent what changed since it was trained.
claude mcp add --transport http since https://api.since.dev/mcp