MemoryAtlas

Benchmarks

Published results, grouped by benchmark. Each row keeps its backbone LLM, embedder, source, and a trust badge — because a memory score is only as meaningful as the pipeline and the party that measured it. The context-window baseline shows how far naive prompt-stuffing gets.

Read these as conditional, not as a ranking. Rows are ordered by score so you can scan them, but a benchmark measures a whole pipeline — so two rows with different backbones, embedders, or sources are notapples-to-apples, and vertical order is not “better to worse.” The same framework can swing tens of points between a vendor self-report and an independent run — mem0 lands at 49 and 94 on LongMemEval depending on who ran it. Only rows sharing a config compare directly, which is exactly the gap a single fixed-config run is meant to close.
IndependentA neutral party ran it.
Self-reportedThe framework's own vendor reported it.
UnverifiedSource is neutral but not yet reproduced.

LoCoMo

32K-context era (ACL 2024) · 1,982 questions

Long-term, multi-session conversational recall (single-hop, multi-hop, open-domain, temporal).

Caveats

  • Average context length is modest by 2026 standards; a 'dump everything into the prompt' baseline now scores competitively.
  • Does not explicitly score knowledge updates.
FrameworkValueBackboneTrustSource
ByteRover
96.1accuracy
Gemini 3 Flash (curation/query) + Gemini 3.1 Pro (justifier)Self-reportedByteRover team (Nguyen et al.)
Zep (Graphiti)
94.7accuracy
gpt-5.4 (reasoning=medium)Self-reportedZep
Mem0
92.5accuracy
Self-reportedMem0
ByteRover
92.2accuracy
Gemini 3 Flash (curation/judge) + Gemini 3 Pro (answer/justifier, best run)Self-reportedByteRover
Honcho
89.9accuracy
Self-reportedHoncho (Plastic Labs)
MIRIX
85.38accuracy
gpt-4.1-miniSelf-reportedMIRIX (Wang & Chen)
Memori
81.95accuracy
Self-reportedMemori (MemoriLabs)
MemOS
75.8accuracy
GPT-4o-miniSelf-reportedMemOS (MemTensor et al.)
LiCoMemory
67.2accuracy
gpt-4o-miniSelf-reportedLiCoMemory (Huang et al., HKUST/Huawei/CUHK-SZ/WeBank)
Mem0
66.88accuracy
IndependentHindsight/Vectorize (competitor re-run)
LiCoMemory
62.99accuracy
Llama-3.1-70B-Instruct-TurboSelf-reportedLiCoMemory (Huang et al., HKUST/Huawei/CUHK-SZ/WeBank)
Mem0
54.68accuracy
gpt-4o-miniIndependentLiCoMemory (Huang et al., HKUST et al.) — competitor re-run
A-MEM
48.59accuracy
gpt-4o-miniIndependentLiCoMemory (Huang et al., HKUST et al.) — competitor re-run
A-MEM
48.38accuracy
gpt-4o-miniIndependentMIRIX (Wang & Chen) — competitor re-run
Zep (Graphiti)
44.76accuracy
gpt-4o-miniIndependentLiCoMemory (Huang et al., HKUST et al.) — competitor re-run

LongMemEval

32K-context era (2024) · 500 questions

Multi-session recall including knowledge updates across ~500 questions.

Caveats

  • Like LoCoMo, large modern context windows weaken it as an isolation test of memory.
  • LongMemEval-S (~103k tokens) fits inside a 128k context window, so a full-context baseline can solve much of it without memory — 'borderline' saturation risk per Jiang et al., 'Anatomy of Agentic Memory' (arXiv:2602.19320, 2026).
FrameworkValueBackboneTrustSource
Mnemosyne
98.9recall
Self-reportedMnemosyne OSS
agentmemory
95.2recall
Self-reportedrohitg00 (agentmemory authors)
Mem0
94.4accuracy
Self-reportedMem0
Hindsight
91.4accuracy
Gemini 3 ProSelf-reportedHindsight (Vectorize)
Honcho
90.4accuracy
Self-reportedHoncho (Plastic Labs)
Zep (Graphiti)
90.2accuracy
gpt-5.4 (reasoning=medium)Self-reportedZep
RetainDB
79accuracy
gpt-5.4Self-reportedRetainDB
MemOS
77.8accuracy
GPT-4o-miniSelf-reportedMemOS (MemTensor et al.)
LiCoMemory
73.8accuracy
gpt-4o-miniSelf-reportedLiCoMemory (Huang et al., HKUST/Huawei/CUHK-SZ/WeBank)
Zep (Graphiti)
71.2accuracy
GPT-4oIndependentHindsight/Vectorize (competitor re-run)
LiCoMemory
69.2accuracy
Llama-3.1-70B-Instruct-TurboSelf-reportedLiCoMemory (Huang et al., HKUST/Huawei/CUHK-SZ/WeBank)
Zep (Graphiti)
63.8accuracy
gpt-4o-miniSelf-reportedZep AI (Rasmussen et al.)
Mem0
62.6accuracy
gpt-4o-miniIndependentLiCoMemory (Huang et al., HKUST et al.) — competitor re-run
Zep (Graphiti)
58.6accuracy
gpt-4o-miniIndependentLiCoMemory (Huang et al., HKUST et al.) — competitor re-run
A-MEM
55accuracy
gpt-4o-miniIndependentLiCoMemory (Huang et al., HKUST et al.) — competitor re-run
Mem0
49accuracy
GPT-4oIndependentZep (competitor harness)
MIRIX
43.49accuracy
GPT-4o-miniIndependentMemOS (MemTensor) — competitor re-run

BEAM (100K)

ICLR 2026

Long-term memory across ~100K-token conversations — BEAM's smallest published tier.

Caveats

  • 100K tokens fits inside modern context windows, so a full-context baseline is viable at this tier — BEAM's context-window-rot escape applies mainly to the 1M/10M tiers.
  • Self-reported runs at this tier use different judge models (e.g. Hindsight: Llama-4-Maverick; Mnemosyne: DeepSeek V4 Flash), so cross-system comparisons of LLM-as-judge scores are weak.
FrameworkValueBackboneTrustSource
Mnemosyne
372latency-ms
Self-reportedMnemosyne OSS
Mnemosyne
65.2accuracy
Llama 3.3 70B (via NVIDIA API)Self-reportedMnemosyne OSS
Mnemosyne
20recall
Self-reportedMnemosyne OSS

BEAM (1M)

ICLR 2026

Long-term memory across ~1M-token conversations spanning multiple domains.

Caveats

  • Built specifically to escape the context-window-rot that affects LoCoMo/LongMemEval.
FrameworkValueBackboneTrustSource
Mnemosyne
493latency-ms
Self-reportedMnemosyne OSS
Mem0
64.1accuracy
Self-reportedMem0
Context-window baseline
64.1accuracy
UnverifiedMem0 (benchmark summary)
Mnemosyne
20recall
Self-reportedMnemosyne OSS

BEAM (10M)

ICLR 2026

Long-term memory stressed to ~10M-token scale.

Caveats

  • Hardest tier; scores drop sharply, exposing real retention limits.
FrameworkValueBackboneTrustSource
Hindsight
64.1accuracy
Self-reportedHindsight (Vectorize)
Mem0
48.6accuracy
Self-reportedMem0
Mnemosyne
35latency-ms
Self-reportedMnemosyne OSS
Mnemosyne
20recall
Self-reportedMnemosyne OSS
Cognee
0.67accuracy
Self-reportedcognee maintainers (README Benchmarks section)