Back to directory

ATM-Bench

A benchmark for evaluating whether an AI agent or memory system can answer personal, evidence-grounded questions about roughly four years of a person's own multimodal history, including images, videos and emails.

ATM-Bench

ATM-Bench measures long-term, personalized, referential memory: questions that refer to something the user has previously said, seen or done, which the answering system must retrieve and ground in the right piece of evidence rather than guess. It ships baseline implementations for retrieval methods and several ported third-party memory systems, and separately benchmarks general-purpose coding and agent systems, including Claude Code, Codex, OpenCode, Pi, OpenClaw and Antigravity, run through per-question, isolated evaluation harnesses, with an accompanying leaderboard and per-run cost estimates.

A harder subset of the benchmark is distributed as a Harbor dataset, so any Harbor-compatible agent can be run against a fixed set of difficult questions in per-question isolated containers.

It is written in Python and released under the MIT license, accompanying a published research paper.

More in Agent memory

See all 450
  • A long technical guide to AI agent memory: why stateless LLMs need it, the different memory architectures from vector stores to knowledge graphs, and how Cognee implements one as an open-source memory layer.

  • A local, file-based long-term memory layer for a personal AI that never summarizes conversations, keeping every line with a timestamp and searching by time first and words second, rather than retrieving only similar-seeming chunks.

  • NEOTH

    deepwiki.com

    A local-first personal AI daemon in Rust with five memory tiers, consent-gated tools, a WASM plugin sandbox, multi-provider model routing and signed audit logs, aimed at people who want both a daily assistant and a serious coding helper.