Open call: test your agent memory layer on an adversarial coding benchmark

I built AMB, an open and preregistered benchmark for memory layers in coding agents.

Most memory benchmarks test whether a system retrieves a relevant chunk. AMB tests whether that memory actually helps an agent complete real coding work, or causes a worse change.

Claude Code runs inside a sandboxed repository, and executable tests grade the resulting artifact. The benchmark is adversarially constructed with absent, stale, superseded, contradictory, adjacent, and irrelevant memories.

The current public feed contains 195 pre-authored session transcripts. A separate hard corpus record scales to 4,900 documents, including 196 real documents and 4,704 synthetic distractors, with roughly 143,000 chunks.

I am inviting small memory vendors to test their systems. There is no participation fee. Vendors can review the adapter contract, run with their own credentials, and publish their configuration and results. Negative results are welcome.

The current suite mainly measures the read path. It does not yet measure whether a memory layer learns from the agent’s own work across sessions, and no multi product ranking has been published.

Repository:

What would you want this benchmark to measure before trusting its results?

The execution-based evaluation sounds much more useful than measuring retrieval alone. I’d also include a no-memory baseline and a small leakage check, then report stale, contradictory, and irrelevant memory failures separately. That would make the results easier to interpret.

Thanks, I changed the benchmark in that direction. It now evaluates whether Claude completes the coding task and passes an executable checker, rather than scoring retrieval alone. I added a bare arm with no memory layer, plus a protocol arm with the shared instructions but no memory surface, so I can separate memory from generic prompting.

I also added leakage audits and sandbox isolation checks. The benchmark now reports absent, stale, contradictory, irrelevant, and present memory conditions separately.