Skip to main content

Mem0 home page

Search...

Ctrl KAsk AI

Search...

Navigation

Core Concepts

Memory Types

Welcome Mem0 Platform Open Source Cookbooks Integrations API Reference Release Notes

• Documentation

Getting Started

• Overview
• Vibecoding
• Mem0 MCP
• CLI
• Platform vs Open Source
• Quickstart

Core Concepts

• Memory Types
• Add Memory
• Search Memory
• Update Memory
• Delete Memory

Platform Features

• Overview

• Essential Features

• Advanced Features

• Data Management

• Integration Features

Support & Troubleshooting

• FAQs

Migration Guide

• Migrate from Open Source to Platform
• Migrating from v0.x to v1.0.0
• Breaking Changes in v1.0.0
• API Reference Changes

Contribute

• Contribution Hub

On this page

• How Mem0 Organizes Memory
• Key terms
• Short-term vs long-term memory
• How does it work?
• When should you use each layer?
• How it compares
• Put it into practice
• See it live

​ How Mem0 Organizes Memory

Mem0 separates memory into layers so agents remember the right detail at the right time. Think of it like a notebook: a sticky note for the current task, a daily journal for the session, and an archive for everything a user has shared.

Why it matters

• Keeps conversations coherent without repeating instructions.
• Lets agents personalize responses based on long-term preferences.
• Avoids over-fetching data by scoping memory to the correct layer.

​ Key terms

• Conversation memory – In-flight messages inside a single turn (what was just said).
• Session memory – Short-lived facts that apply for the current task or channel.
• User memory – Long-lived knowledge tied to a person, account, or workspace.
• Organizational memory – Shared context available to multiple agents or teams.

Conversation turn

Session memory

User memory

Org memory

Mem0 retrieval layer

​ Short-term vs long-term memory

Short-term memory keeps the current conversation coherent. It includes:

• Conversation history – recent turns in order so the agent remembers what was just said.
• Working memory – temporary state such as tool outputs or intermediate calculations.
• Attention context – the immediate focus of the assistant, similar to what a person holds in mind mid-sentence.

Long-term memory preserves knowledge across sessions. It captures:

• Factual memory – user preferences, account details, and domain facts.
• Episodic memory – summaries of past interactions or completed tasks.
• Semantic memory – relationships between concepts so agents can reason about them later.

Mem0 maps these classic categories onto its layered storage so you can decide what should fade quickly versus what should last for months.

​ How does it work?

Mem0 stores each layer separately and merges them when you query:

1. Capture – Messages enter the conversation layer while the turn is active.
2. Promote – Relevant details persist to session or user memory based on your user_id, session_id, and metadata.
3. Retrieve – The search pipeline pulls from all layers, ranking user memories first, then session notes, then raw history.

import os

from mem0 import Memory

memory = Memory(api_key=os.environ["MEM0_API_KEY"])

# Sticky note: conversation memory
memory.add(
    ["I'm Alex and I prefer boutique hotels."],
    user_id="alex",
    session_id="trip-planning-2025",
)

# Later in the session, pull long-term + session context
results = memory.search(
    "Any hotel preferences?",
    user_id="alex",
    session_id="trip-planning-2025",
)

Use session_id when you want short-term context to expire automatically; rely on user_id for lasting personalization.

​ When should you use each layer?

• Conversation memory – Tool calls or chain-of-thought that only matter within the current turn.
• Session memory – Multi-step tasks (onboarding flows, debugging sessions) that should reset once complete.
• User memory – Personal preferences, account state, or compliance details that must persist across interactions.
• Organizational memory – Shared FAQs, product catalogs, or policies that every agent should recall.

​ How it compares

Layer	Lifetime	Short or long term	Best for	Trade-offs
Conversation	Single response	Short-term	Tool execution detail	Lost after the turn finishes
Session	Minutes to hours	Short-term	Multi-step flows	Clear it manually when done
User	Weeks to forever	Long-term	Personalization	Requires consent/governance
Org	Configured globally	Long-term	Shared knowledge	Needs owner to keep current

Avoid storing secrets or unredacted PII in user or org memories—Mem0 is retrievable by design. Encrypt or hash sensitive values first.

​ Put it into practice

• Use the Add Memory guide to persist user preferences.
• Follow Advanced Memory Operations to tune metadata and graph writes.

​ See it live

• AI Tutor with Mem0 shows session vs user memories in action.
• Support Inbox with Mem0 demonstrates shared org memory.

Explore Memory Operations

See a Cookbook

Was this page helpful?

YesNo

Suggest edits Raise issue

Quickstart\ \ Previous Add Memory\ \ Next

Ctrl+I

Assistant

Responses are generated using AI and may contain mistakes.

Suggestions

When should I use session memory?What are the memory layers?

Contact support