Memory Systems

Memory System Design

Memory provides the persistence layer that allows agents to maintain continuity across sessions and reason over accumulated knowledge. Simple agents rely entirely on context for memory, losing all state when sessions end. Sophisticated agents implement layered memory architectures that balance immediate context needs with long-term knowledge retention. The evolution from vector stores to knowledge graphs to temporal knowledge graphs represents increasing investment in structured memory for improved retrieval and reasoning.

When to Use

• Building agents that must persist knowledge across sessions
• Choosing between memory frameworks (Mem0, Zep/Graphiti, Letta, LangMem, Cognee)
• Needing to maintain entity consistency across conversations
• Implementing reasoning over accumulated knowledge
• Designing memory architectures that scale in production
• Evaluating memory systems against benchmarks (LoCoMo, LongMemEval, DMR)
• Building dynamic memory with automatic entity/relationship extraction and self-improving (Cognee)

When NOT to Use

• Coordinating multiple agents or agent handoffs (use multi-agent-patterns)
• Designing individual tools or tool interfaces (use tool-design)
• Setting up hosted agent infrastructure or sandboxed VMs (use hosted-agents)
• General database design or data modeling (not specific to agent memory)
• Caching strategies for API responses (that's application-level caching, not agent memory)

Decision Tree

What memory problem are you solving?
│
├─ Agent loses state between sessions
│  ├─ Simple facts/preferences? → File-system memory (JSON + timestamps)
│  ├─ Need semantic search? → Mem0 or vector store with metadata
│  ├─ Need entity tracking + relationships? → Zep/Graphiti (temporal KG)
│  └─ Need agent self-management of memory? → Letta or Cognee
│
├─ Choosing a framework
│  ├─ Fastest path to production? → Mem0 (managed infra, broad integrations)
│  ├─ Enterprise + temporal reasoning? → Zep/Graphiti (bi-temporal model)
│  ├─ Full agent introspection? → Letta (self-editing memory tiers)
│  ├─ Multi-hop reasoning + customizable pipeline? → Cognee (semantic graph)
│  └─ Already on LangGraph? → LangMem (tightest integration)
│
├─ Retrieval problems
│  ├─ Direct factual queries? → Semantic (embedding similarity)
│  ├─ "Tell me about X" queries? → Entity-based (graph traversal)
│  ├─ Facts change over time? → Temporal (validity filter)
│  └─ Best overall accuracy? → Hybrid (semantic + keyword + graph)
│
└─ Not sure if you need structured memory
   ├─ Single-session agent? → No, context window is enough
   ├─ Multi-session but simple facts? → File-system first, upgrade later
   └─ Complex reasoning across sessions? → Yes, start with Mem0, add graph when needed

Core Concepts

Memory spans a spectrum from volatile context window to persistent storage. Key insight from benchmarks: tool complexity matters less than reliable retrieval — Letta's filesystem agents scored 74% on LoCoMo using basic file operations, beating Mem0's specialized tools at 68.5%. Start simple, add structure (graphs, temporal validity) only when retrieval quality demands it.

Detailed Topics

Production Framework Landscape

Zep's Graphiti engine builds a three-tier knowledge graph (episode, semantic entity, community subgraphs) with a bi-temporal model tracking both when events occurred and when they were ingested. Mem0 offers the fastest path to production with managed infrastructure. Letta provides the deepest agent control through its Agent Development Environment. Cognee produces multi-layer semantic graphs — it layers text chunks and entity types as nodes with detailed relationship edges, building interconnected knowledge engine. Every core piece (ingestion, entity extraction, post-processing, retrieval) is customizable.

Benchmark Performance Comparison

Zep achieves up to 18.5% accuracy improvement on LongMemEval while reducing latency by 90%. Cognee outperformed Mem0, Graphiti, and LightRAG on HotPotQA multi-hop reasoning benchmarks across Exact Match, F1, and human-like correctness metrics. Letta's filesystem-based agents achieved 74% on LoCoMo using basic file operations, outperforming specialized memory tools — tool complexity matters less than reliable retrieval. No single benchmark is definitive; treat these as signals for specific retrieval dimensions rather than rankings.

Memory Layers (Decision Points)

Retrieval Strategies

Zep's hybrid approach achieves 90% latency reduction (2.58s vs 28.9s) by retrieving only relevant subgraphs. Cognee implements hybrid retrieval through its 14 search modes — each mode combines different strategies from its three-store architecture (graph, vector, relational), letting agents select the retrieval strategy that fits the query type rather than using a one-size-fits-all approach.

Memory Consolidation

Consolidate periodically to prevent unbounded growth. Invalidate but don't discard — preserving history matters for temporal queries. Trigger on memory count thresholds, degraded retrieval quality, or scheduled intervals. See implementation reference for working consolidation code.

Anti-Patterns

Practical Guidance

Choosing a Memory Architecture

Start simple, add complexity only when retrieval fails. Most agents don't need a temporal knowledge graph on day one.

1. Prototype: File-system memory. Store facts as structured JSON with timestamps. Good enough to validate agent behavior.
2. Scale: Move to Mem0 or vector store with metadata when you need semantic search and multi-tenant isolation.
3. Complex reasoning: Add Zep/Graphiti when you need relationship traversal, temporal validity, or cross-session synthesis. Graphiti uses structured ties with generic relations, keeping graphs simple and easy to reason about; Cognee builds denser multi-layer semantic graphs with detailed relationship edges — choose based on whether you need temporal bi-modeling (Graphiti) or richer interconnected knowledge structures (Cognee).
4. Full control: Use Letta or Cognee when you need agent self-management of memory with deep introspection.

Integration with Context

Memories must integrate with context systems to be useful. Use just-in-time memory loading to retrieve relevant memories when needed. Use strategic injection to place memories in attention-favored positions (beginning/end of context).

Error Recovery

• Empty retrieval: Fall back to broader search (remove entity filter, widen time range). If still empty, prompt user for clarification.
• Stale results: Check valid_until timestamps. If most results are expired, trigger consolidation before retrying.
• Conflicting facts: Prefer the fact with the most recent valid_from. Surface the conflict to the user if confidence is low.
• Storage failure: Queue writes for retry. Never block the agent's response on a memory write.

Examples

Example 1: Mem0 Integration

from mem0 import Memory

m = Memory()
m.add("User prefers dark mode and Python 3.12", user_id="alice")
m.add("User switched to light mode", user_id="alice")

# Retrieves current preference (light mode), not outdated one
results = m.search("What theme does the user prefer?", user_id="alice")

Example 2: Temporal Query

# Track entity with validity periods
graph.create_temporal_relationship(
    source_id=user_node,
    rel_type="LIVES_AT",
    target_id=address_node,
    valid_from=datetime(2024, 1, 15),
    valid_until=datetime(2024, 9, 1),  # moved out
)

# Query: Where did user live on March 1, 2024?
results = graph.query_at_time(
    {"type": "LIVES_AT", "source_label": "User"},
    query_time=datetime(2024, 3, 1)
)

Example 3: Cognee Memory Ingestion and Search

import cognee
from cognee.modules.search.types import SearchType

# Ingest and build knowledge graph
await cognee.add("./docs/")
await cognee.add("any data")
await cognee.cognify()

# Enrich memory 
await cognee.memify()

# Agent retrieves relationship-aware context
results = await cognee.search(
    query_text="Any query for your memory",
    query_type=SearchType.GRAPH_COMPLETION,
)

Guidelines

1. Start with file-system memory; add complexity only when retrieval quality demands it
2. Track temporal validity for any fact that can change over time
3. Use hybrid retrieval (semantic + keyword + graph) for best accuracy
4. Consolidate memories periodically — invalidate but don't discard
5. Design for retrieval failure: always have a fallback when memory lookup returns nothing
6. Consider privacy implications of persistent memory (retention policies, deletion rights)
7. Benchmark your memory system against LoCoMo or LongMemEval before and after changes
8. Monitor memory growth and retrieval latency in production

Integration

This skill builds on context-fundamentals. It connects to:

• multi-agent-patterns - Shared memory across agents
• context-optimization - Memory-based context loading
• evaluation - Evaluating memory quality

References

Internal references:

• Implementation Reference - Detailed implementation patterns, production framework references (Mem0, Graphiti, Cognee)

Related skills in this collection:

• context-fundamentals - Context basics
• multi-agent-patterns - Cross-agent memory

External resources:

• Zep temporal knowledge graph paper (arXiv:2501.13956)
• Mem0 production architecture paper (arXiv:2504.19413)
• Cognee optimized knowledge graph + LLM reasoning paper (arXiv:2505.24478)
• LoCoMo benchmark (Snap Research)
• MemBench evaluation framework (ACL 2025)
• Graphiti open-source temporal KG engine (github.com/getzep/graphiti)
• Cognee open-source knowledge graph memory (github.com/topoteretes/cognee)
• Cognee comparison: Form vs Function — graph structure comparison and HotPotQA benchmarks across Mem0, Graphiti, LightRAG, Cognee