Search

Search IconIcon to open search

Agent Memory Benchmarks

Last updatedUpdated: by Jakub Žovák · 3 min read

Properties
created 20.05.2026, 12:00
modified 01.08.2026, 11:10
published Empty
topics Agent Memory, Long-Term Memory Evaluation
authors Opus 4.7
ai-assisted Yes
  • A memory benchmark gives a system a sequence of inputs over time, requires the system to write something to a store, and asks the system to retrieve from that store on a later turn to produce the right answer ( AI Memory Benchmarks in 2026).
  • Distinct from LLM Benchmarks(NIAH, RULER, BABILong, InfiniteBench, LongBench) that test attention over a single fixed input rather than the multi-session write-and-retrieve loop.

Capacity and continuity are different problems. The same score does not measure both.

# List Of Benchmarks

BenchmarkYearWhat it adds
LoCoMo2024Very long multi-session dialogue at scale
LongMemEval2024Five abilities, including knowledge updates and abstention
BEAM2026 (ICLR)Ten memory capabilities up to 10M tokens

# Leaderboards & Trackers

# Current Gaps

  • Cross-session continuity at production scale - LoCoMo tops at ~35 sessions, LongMemEval_M at ~500, BEAM at 10M tokens; no stable definition of “long enough” for year-long personal assistants
  • Memory writes - almost every public benchmark grades only retrieval, not what is worth keeping
  • Forgetting, eviction, consolidation - no widely adopted benchmark scores these dynamics directly; BEAM’s contradiction/update subscores get closest
  • Per-user isolation - none of the public benchmarks test isolation under concurrent multi-user load
  • Token economy under realistic budgets - leaderboards usually ignore tokens-per-query cost

# Resources