Memory & State
Decide what survives the turn
What should the system still know tomorrow?
13 entries · 2 categories · 3 equations
The arithmetic
Memory systems
Graphiti
Bi-temporal graph where edges carry valid-from and invalid-at, so facts expire
Temporal invalidation is the clearest differentiator against native memory tools.
Mem0
Extracts facts into a vector, graph and KV store scoped by user, session or agent
Zep
Async summarization and entity extraction layered over Graphiti
Cognee
ECL pipeline building an ontology-typed graph alongside a vector index
Hindsight
Retain, recall and reflect over memory banks with fact extraction and an MCP server
LangMem
Extracts and updates memories into a LangGraph store
Recent activity is largely dependency bumps, with no tagged releases.
Letta (ex-MemGPT)
LLM-as-OS paging between main context, recall and archival stores
Core repo took ~5 commits in three months; development moved to sibling repos. Still widely recommended in roundups.
MemOS
OS-style abstraction over plaintext, activation (KV) and parametric memory
Supermemory
Memory API and RAG over user context, with a router SDK and MCP
Native platform state
Anthropic context editing
Server-side clearing of stale tool results and thinking blocks before token counting
Anthropic memory tool
Claude issues CRUD against a /memories directory; you own the storage backend
Stores nothing itself. Budget for path-traversal defenses, per-tenant isolation and retention policy.
Gemini context caching
Explicit cached-content handles or implicit auto-cache on repeated prefixes
OpenAI Responses API state
Server-stored response items chained via previous_response_id, 30-day retention