Skip to content
zensation

Research overview

Three tracks, architecture and agenda

Publications

Preprints, software, identifiers

Methodology

Operational standards and validation

Research ethics

Fundamental rights and compliance

Resources

Code, data, citation, open science

Adopt AI

Neutral roadmap & interactive simulation

Public sector & funding

Collaborations in the public sector

Protecting public spaces

Track B — rights-preserving early warning

Applied AI · knowledge work

Track C — memory for knowledge work

Technology

The architecture behind every application

Playground

Run the open memory core live

Work with usAboutOpen SourceBlog
EN·DE
Contact
zensation
Research overviewPublicationsMethodologyResearch ethicsResources
Adopt AIPublic sector & fundingProtecting public spacesApplied AI · knowledge workTechnologyPlayground
Work with usAboutOpen SourceBlogContact
Blog
Analysis

The memory tax: why agent memory needs a path back to the source

Alexander Bering
Alexander Bering
October 30, 2026 · 3 min read

On 25 October 2026, Memory Tax: Dissecting the Net Value of Agent Memory (arXiv 2610.34073) appeared, by researchers at the University of Illinois Urbana-Champaign, Tsinghua University, Renmin University, the University of Waterloo and Verdent.ai. It asks a question the debate about agent memory often skips: what does a memory system add over plain retrieval from the raw history?

What was measured. Eleven systems of four kinds (flat stores, tiered lifecycles, graphs, trained policies) were run against a plain retrieval baseline on LongMemEval-s, PersonaMem-v2 and MINT-Eval, each with three language models. On LongMemEval-s, none of the eleven systems scored above two-round retrieval with any of the three models. The authors call the loss the memory tax: questions retrieval answers and memory does not. Its counterpart is the memory benefit: questions only memory solves. A system pays off when the benefit outweighs the tax.

Dot plot in petrol design. Title: Eleven memory systems, 33 measurements, none above. For eleven memory systems with three language models each, on LongMemEval-s, the gap to plain two-round retrieval over the raw history is plotted. Retrieval is a line at zero; all 33 dots lie below it, by 1.2 to 40.4 percentage points. Bottom: the authors' remedy, keep the path back to the source. Source: He et al., Memory Tax, arXiv 2610.34073, 2026, Table 1.

Chart: LongMemEval-s, Table 1 of He et al. (2026). Each dot is one system with one model, measured against plain two-round retrieval; with GPT-5.6 Luna on a sample of 20 percent of the questions.

Where the tax comes from. Two sources are well documented. Summarising loses information: in a sample, one system had no memory unit at all for 38 percent of the facts. And preserved information gets harder to find, because it is fragmented, diluted or rephrased. The authors also note that several widely used benchmarks favour plain retrieval, which leaves memory little room to show its benefit there.

The remedy. The paper's simplest proposal: keep a light path back to the source, search the raw history next to the memory and rank both result lists together. In their experiment this lowered the tax across several systems.

The limits of the study. The authors state them themselves: the choice of systems is representative, not exhaustive, and further tuning of individual systems might improve their scores. The benchmarks are static, offline and in English. With the largest of the three models, LongMemEval-s ran on a stratified sample of 20 percent of the questions to limit cost.

What the brain does. Neuroscience has described this principle for decades. In the complementary learning systems account, the hippocampus stores single episodes quickly while the neocortex slowly learns what is general (McClelland, McNaughton and O'Reilly, 1995). Under the transformation hypothesis, the detailed and the generalised version of a memory can coexist, and the task decides which one is retrieved (Winocur and Moscovitch, 2011). The brain does not replace the episode with its summary; it keeps the summary beside it.

How ZenBrain does it. In ZenBrain the episode stays when consolidation turns it into a fact, and the fact stays linked to its episode. A recall searches episodes and facts together and ranks every hit on one scale from 0 to 1. It is the paper's remedy built into the architecture rather than added as a separate path.

Sources: He et al. (2026), arXiv:2610.34073v1 · McClelland, McNaughton, O'Reilly (1995), Psychological Review 102(3), doi:10.1037/0033-295X.102.3.419 · Winocur, Moscovitch (2011), Journal of the International Neuropsychological Society 17(5), doi:10.1017/S1355617711000683 · ZenBrain on GitHub (Apache 2.0).

Share on XShare on LinkedIn

Related Articles

The Data Is Right There. Nobody Can Reach It.

A broadcaster in St. Louis has been locked out of its own archive since March. The files were not deleted. The reason is not one a backup solves.

The Narrow Band

Why a working system sits on a narrow edge — and why, with AI, small errors don't add up, they compound. Precision isn't optional.

You Can't Host Trust

"Hosted in the EU" is reassuring, "open weights" sounds good. What your AI does with your data is only auditable if the layer that touches your data is open.

zensationIndependent AI research lab · Kiel
ResearchPublicationsMethodologyResearch ethicsResourcesMemory architecturesBenchmarksAgent memory comparedAdopt AIPublic sectorProtecting public spacesApplied AITechnologySystem explorerPlaygroundEigenraumWork with usOpen SourceAboutBlogChangelog
GitHubLinkedInarXivZenodoORCIDScholarSemantic ScholarHuggingFacenpmDiscussions

© 2026 Alexander Bering / ZenSation Enterprise Solutions

RSSPrivacy PolicyLegal NoticeAccessibility