- Recall relevant past interactions
- Store important user preferences and factual context
- Learn from successes and failures
Stateless vs. Stateful Agents
Most current agents are stateless: they process a query, generate a response, and forget everything. Even with huge context windows, everything resets the next session. Stateful agents, powered by Mem0, are different. They retain context, recall what matters, and behave more intelligently over time.
Where Memory Fits in the Agent Stack
Mem0 sits alongside your retriever, planner, and LLM. Unlike retrieval-based systems (like RAG), Mem0 tracks past interactions, stores long-term knowledge, and evolves the agent’s behavior.
| Capability | Context Window | Mem0 Memory |
|---|---|---|
| Retention | Temporary | Persistent |
| Cost | Grows with input size | Optimized (only what matters) |
| Recall | Token proximity | Relevance + intent-based |
| Personalization | None | Deep, evolving profile |
| Behavior | Reactive | Adaptive |
Memory vs. RAG: Complementary Tools
RAG (Retrieval-Augmented Generation) is great for fetching facts from documents. But it’s stateless. It doesn’t know who the user is, what they’ve asked before, or what failed last time. Mem0 provides continuity. It stores decisions, preferences, and context—not just knowledge.| Aspect | RAG | Mem0 Memory |
|---|---|---|
| Statefulness | Stateless | Stateful |
| Recall Type | Document lookup | Evolving user context |
| Use Case | Ground answers in data | Guide behavior across time |
Types of Memory in Mem0
Mem0 supports different kinds of memory to mimic how humans store information:- Working Memory: short-term session awareness
- Factual Memory: long-term structured knowledge (e.g., preferences, settings)
- Episodic Memory: records specific past conversations
- Semantic Memory: builds general knowledge over time
Why Developers Choose Mem0
Mem0 isn’t a wrapper around a vector store. It’s a full memory engine with:- LLM-based extraction: Intelligently decides what to remember
- Filtering & decay: Avoids memory bloat, forgets irrelevant info
- Costs Reduction: Save compute costs with smart prompt injection of only relevant memories
- Dashboards & APIs: Observability, fine-grained control
- Cloud and OSS: Use our platform version or our open-source SDK version
Core Capabilities
- Reduced token usage and faster responses: sub-50 ms lookups
- Semantic memory: procedural, episodic, and factual support
- Multimodal support: handle both text and images
- Graph memory: connect insights and entities across sessions
- Host your way: either a managed service or a self-hosted version
Getting Started
Mem0 offers two powerful ways to leverage our technology: our managed platform and our open source solution.Quickstart
Integrate Mem0 in a few lines of code
Playground
Mem0 in action
Examples
See what you can build with Mem0