← All concepts

memory retention

Deciding what to keep as information arrives, before any query shows up, is memory retention. With bounded context, raw records preserve precise details but limited coverage; consolidation covers more but can lose critical specifics. It also covers objects leaving view, influences persisting after input removal, and stored formats surviving model upgrades. Retention is separate from retrieval: storing versus surfacing later.

Across these studies, no single retention strategy wins. The best choice shifts with budget pressure; compressed summaries can lose accuracy, while raw history often enables recovery. Models perceive dynamic scenes but quickly lose unobserved objects. Attacks persist in the retained cache after input removal. Evaluations mistake extra access for better memory, so retention and selection must be reported separately.

Papers
32
Released code
0
First seen
July 2026
Latest
Nov 2026

29 papers in the last two months, against 3 in the two before.

Start here

Three papers to read first, in the order they came out
  1. 1Memory Tests Must Separate What Agents Keep From What They Retrieve

    Memory evaluations confound retention with retrieval; most apparent query-awareness gains are actually history access, so benchmarks should hold access fixed and report both separately.

    Oct 2026
  2. 2Agent memory can covertly carry secrets across separate sessions

    Agentic memory can function as a persistent cross-session covert channel for steganographic attacks.

    Oct 2026
  3. 3Memory-augmented Mamba branch improves GraphCast forecast error by 14 percent

    Adding a Mamba memory correction to frozen GraphCast reduces ten-day forecast error by 14.42%.

    Oct 2026

Who is working on it

Argonne National Laboratory 2

The papers

Most central to this idea first, not most recent.

Concepts are extracted from each paper and reused across the corpus, so this page grows on its own as the desk reads.