Benchmarks

Memory accuracy you can trust

Durmem is tested on three key AI memory benchmarks: one for consistency as facts change, one for recall across long histories, and one for memory over real agent work. Together they ask whether an agent can recover the right current context when it matters.

STALE
Consistency
86.1%

Changing-history memory. Same-cohort reference run: CUPMem at 78.7%.

LongMemEval
Recall
89.3%

Long-horizon memory QA. Published full-context comparator: GPT-4o at 60.6%.

Context: Some vendors publish results in the mid-to-high 90s, often after heavy benchmark-specific optimization. Durmem did not engage in benchmark-specific tuning; this score reflects its general memory system.

AMA-Bench
Trajectories
75.6%

Memory over realistic agent work. Published full-context comparator: GPT-5.2 at 72.3%.

Comparison summary

The table keeps the homepage figures in one place and shows reference points from the same disclosed cohort or the corresponding benchmark papers. It is not a cross-suite ranking: cohorts and model backbones may differ.

BenchmarkDurmem cohort resultReference pointsWhat the benchmark stresses
STALE86.1%Same 141-scenario cohort: CUPMem 78.7%, GPT-4o-mini without memory 8.7%, Mem0 8.3%, LiCoMemory 7.6%, Zep 6.0%.Whether memory stays current as facts change, including stale premises and cascading conflicts.
LongMemEval89.3%Published full-context reference: GPT-4o 60.6%.Long-horizon questions over human history, including updates and temporal reasoning.
AMA-Bench75.6%Published references on their reported evaluation: GPT-5.2 full-context 72.3%, AMA-Agent 57.2%, MemoRAG 46.1%.Whether agents can use memory from prior tool use, task steps, preferences, and outcomes.

Durmem figures are from disclosed evaluation cohorts: 141 of 400 STALE scenarios, 149 LongMemEval questions, and 43 of 208 AMA-Bench cases. STALE references above use Durmem's same 141-scenario cohort; other reference numbers are published results, not systems re-run by Durmem. Cohorts and model backbones may differ, so these are context rather than a whole-field ranking.

Three different tests of useful memory

A single retrieval score cannot tell the whole story. These benchmarks cover three failure modes an agent encounters in practice: believing something obsolete, losing facts in a long history, and forgetting what happened while another agent was working.

STALE: stay correct as facts change

Each scenario contains an earlier fact and a later update that makes it obsolete. The benchmark checks whether the agent identifies the current state, rejects questions built on stale premises, and adapts its response to the new reality.

  • 141 of 400 scenarios in a stratified cohort
  • Direct and cascading conflicts
  • Three scored dimensions per scenario

LongMemEval: remember across sessions

Questions draw on long, multi-session human histories. Success requires more than finding a sentence: the agent must connect evidence across sessions, order events in time, and honor later knowledge updates.

  • 149 questions in a stratified cohort
  • Six question categories
  • Multi-session and temporal reasoning

AMA-Bench: remember agent work

Instead of human conversation, AMA-Bench uses agent trajectories: actions, tool outputs, observations, state changes, and outcomes. It measures recall, causal inference, state updating, and state abstraction across six domains.

  • 43 of 208 cases in a stratified cohort
  • Four memory categories across six agent domains
  • Structured memory only, without the raw trajectory

How to read these results

Each evaluation uses a disclosed stratified cohort rather than claiming a full-suite run. The cohorts preserve the relevant conflict types, question categories, agent domains, and memory skills, but sampling uncertainty still applies.

Durmem answers from the structured memory it built during ingestion; it does not receive the original conversation or trajectory at question time. STALE reference scores are Durmem's same-cohort reruns; LongMemEval and AMA-Bench references are published paper figures, not systems re-run by Durmem.

Sources

STALE: Chao et al., arXiv:2605.06527.
LongMemEval: Wu et al., arXiv:2410.10813.
AMA-Bench: arXiv:2602.22769.

Try Durmem with your agent

Connect a hosted store, ask your agent to describe it, then use Durmem in the coding workflow you already have open.

Request access Open install guide