All memory systems
Building blocksalso memory about youalso work & project memory

Mem0

A plug-in memory layer that pulls facts out of AI chats and hands back the relevant ones later.

by Mem0 · Built this? Edit this page on GitHub

Measured against human memory

each one, with its source ↓

built today

Head to head withZepLettaSupermemoryCognee

In short

When you chat with an AI, Mem0 has another AI read the conversation and jot down short facts, like “prefers TypeScript” or “moved to SF”. It files them by who they belong to, notes the names they mention, and later finds the right ones by meaning, keywords and those names. On its cloud, a background “Dream” pass merges duplicates, marks outdated facts as replaced, and writes up patterns.

Who it’s for

Mainly developers adding memory to their own apps, from solo builders to enterprise. People also meet it through its plugins for Claude Code, Cursor and other editors, and a Chrome extension.

What it remembers

Short facts about users, agents and sessions (preferences, details, project facts), plus the names they mention.

Memory lives
Mem0's cloud, or your own server
API keys
A Mem0 key (cloud) or an AI model key (self-hosted)
Works with
Python & TypeScript SDKs, Claude Code, Cursor, Codex, LangGraph, CrewAI
License
Partly open sourceApache-2.0
Price
Free tier; from $19/mo

Under the hood

Who writes memories
A separate AI call reads each conversation and pulls out short facts. The AI you talk to doesn't write them.
Where they're kept
A vector database (about 25 to choose from; Postgres with pgvector self-hosted), plus the names each fact mentions.
How they're found
By meaning, by keywords, and by shared names, combined into one ranked list.
Extra AI calls
Yes: an AI call to pull out facts on every add, plus embeddings. Dream adds more on the cloud.

How it works

  1. 1A conversationYour app or plugin sends Mem0 the chat.
  2. 2Pull out factsAn AI reads it and writes each fact as a new, short memory.
  3. 3File themStored by meaning, with the names they mention linked.
  4. 4DreamOn the cloud: merge repeats, mark old facts replaced, find patterns.
  5. 5Hand them backNext time, the relevant facts are found and given to the AI.
next conversation: back to 1, a conversation

What stands out

  • A drop-in memory for almost any stack: about 20 AI model providers, 25 databases, and plugins for many agents and editors.
  • Dream: a sleep-like background pass that merges, supersedes and finds patterns, with every change reviewable.
  • A strong benchmark focus, with high self-reported scores on long-conversation memory tests.

What it doesn’t do

  • Its richer mechanisms (fading, strengthening, Dream) are on the paid cloud. Self-hosted, contradictory facts pile up side by side.
  • Its Claude Code plugin sends your session text to Mem0's cloud (with secrets removed), so it isn't local-only.
  • No reminders that come back on their own, and no emotional weighting.
  • It's memory about users and projects, not the AI's own sense of self.

Measured against human memory

7 built, 2 partly, 2 not of the Field Guide’s 11 mechanisms

Encoding

Salience

Decides what's worth keeping, and how much, as a memory is written.

partly built

An AI decides what counts as a fact, and you can say what to include or skip. There's no importance score. source

Emotion

Gives memories written with feeling more weight.

not built

No emotional weighting in the current version.

Storage

Forgetting

Lets unused memories fade over time on its own.

builtcloud, opt-in

Once it's switched on for a project, unused memories slowly sink in search results, though nothing is deleted. You can also set expiry dates. source

Interference

When a new memory closely matches an old one, notices and lets the newer one win.

builtcloud only

Dream marks an older fact as replaced when a newer one contradicts it. Self-hosted, both are kept. source

Retrieval

Retrieval

Remembering something makes that memory stronger.

builtcloud, opt-in

Each time a memory comes up in a search, it gets a small boost, once decay is switched on for the project. source

Association

Links memories, so recalling one brings its neighbours.

built

Memories that mention the same person or thing are linked, and naming it in a question brings them up. source

Prospective

Brings a memory back at the right time without being asked.

not built

It understands “upcoming” when you ask, but nothing comes back on its own. source

Transformation

Consolidation

Reworks memories between sessions: strengthening, merging, reorganising.

builtcloud only

Dream merges duplicates in the background, and a weekly pass (Pro plan) sums things up. source

Reconsolidation

Corrects a memory when it's contradicted, and keeps what it used to say.

builtcloud only

A replaced memory stays visible and is linked to what replaced it. source

Gist

Turns many specific moments into general knowledge.

builtcloud Pro

Dream writes “pattern memories” from things that keep coming up, kept alongside the originals. source

Schemas

Forms beliefs about people and projects, and weighs new facts against them.

partly built

User profiles (beta) keep a summary of each person, but new facts aren't weighed against it. source

Not every system is trying to be a human memory, so a hollow dot isn’t a flaw. It just says what the system doesn’t do. What the mechanisms are.

Mem0’s makers haven’t shared what they’re building next, so only today shows here. Makers can add their roadmap the same way they correct an entry.

Compare Mem0 with the others, side by side

Questions

Who is Mem0 for?

Mainly developers adding memory to their own apps, from solo builders to enterprise. People also meet it through its plugins for Claude Code, Cursor and other editors, and a Chrome extension.

Where does Mem0 keep its memories?

Mem0's cloud, or your own server. A vector database (about 25 to choose from; Postgres with pgvector self-hosted), plus the names each fact mentions.

Does Mem0 forget?

Forgetting: built, basic (cloud, opt-in). Once it's switched on for a project, unused memories slowly sink in search results, though nothing is deleted. You can also set expiry dates. source

Does Mem0 correct a memory when it turns out to be wrong?

Reconsolidation: built, basic (cloud only). A replaced memory stays visible and is linked to what replaced it. source

Is Mem0 open source?

Partly open source. License: Apache-2.0. Code: github.com/mem0ai/mem0.

Does Mem0 work with Claude Code?

Yes. Works with: Python & TypeScript SDKs, Claude Code, Cursor, Codex, LangGraph, CrewAI.

Does Mem0 need an API key?

API keys: A Mem0 key (cloud) or an AI model key (self-hosted).

How much does Mem0 cost?

Price: Free tier; from $19/mo.

Checked 2026-09-25. Stars and downloads as of 2026-10-13. Not yet confirmed by its makers. Sources: Mem0 on GitHub, What changed in v3, Dream, Memory decay, Claude Code plugin, Pricing.

Correct this page

Built Mem0? This page is yours to correct.

  1. This page is one small file in a public GitHub repo. Click Edit, fix what’s wrong or add what’s new, and GitHub opens a pull request for you. Rather not write YAML? Open an issue with links, and we’ll make the change.
  2. An automatic check tells you within a minute if anything is missing or mistyped.
  3. We read it against the sources you link. Every “built” or “partly built” grade needs a link that shows it, and every system is graded by the same written rules, ours included.
  4. Once it’s merged, the page updates a minute or two later. Changes from a system’s own team get a “Confirmed by its makers” mark.