AIToday
Zenn AI/MLPublished: Oct 31, 2026, 06:00 JST

Agent memory beats RAG 15/16 to 13/16 in small test

Send on LINE
Agent memory beats RAG 15/16 to 13/16 in small test

3 Key Points

  1. What happened

    Using two invented conversation logs (37 and 34 turns) and 16 questions, the author's summary memory scored 15/16 (93.75%) and naive character-bigram TF-IDF RAG scored 13/16 (81.25%), producing 3 benefit cases against 1 tax case.

  2. Why it matters

    In this scaled-down proof of concept, the summary approach retained structured decisions and current values well enough to outperform plain retrieval, so the paper's warning that memory often trails RAG did not hold here — though the author credits the simpler design and weaker search rather than a general rule.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The paper behind this test, "Memory Tax: Dissecting the Net Value of Agent Memory," compares 10 agent memory systems against a naive RAG that searches conversation history directly, and reports that many memory systems fall below RAG's raw score. It splits the effect into a benefit — memory answering what RAG misses — and a tax — memory answering RAG-answerable questions wrongly. The author was drawn to the explanation that summary memory discards details while naive search can still pick them up if keywords match.

The author could not find the paper's code and skipped its large benchmarks and multiple backbones because they would not fit a six-hour limit or require paid API keys. Instead, the author wrote two fictional multi-session logs — an internal dashboard redesign project with 37 turns and a family trip plan with 34 turns — seeded with one-off facts, then built a summary memory and a naive character-bigram TF-IDF retriever over the same logs. The summary memory kept current values and a change history for explicitly discussed decisions but dropped incidental details. Both conditions answered the same 16 questions, with answers fixed before either condition ran.

The result was 15/16 for memory and 13/16 for RAG, with 3 benefit cases and 1 tax case. The author notes this does not reproduce the paper's headline, and attributes the gap to the memory being far simpler than the 10 architectures tested and to the retriever lacking dense search or cross-encoder reranking — the paper reports RAG-Hybrid at roughly 70%. The author also flags that the two conversations and 16 questions carry no statistical significance, that Claude itself set the memory policy and answered under both conditions, and that the paper's specific architectures and backbones were not used.

FAQ
What exactly is the 'tax' in this experiment?
It is the single case where RAG answered correctly but memory failed: a question about a staging server used before a cloud migration. The summary had dropped that detail because it was never an explicit decision.
How was the memory built?
It kept current values and a change history for explicitly discussed decisions like tech stack, budget, deadline, and team, but discarded incidental details not discussed as decisions.
Why did the author's result differ from the paper?
The author says the memory used here was much simpler than the 10 architectures the paper compares, and the search was only character-bigram TF-IDF without dense retrieval or reranking, so search misses were likely.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Next articleMicrodosing the spirit of Anthropic: inside AI labs' skewed views