memory-systemslisted

# 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 memor