Fetching from the wire…
Public story · 2026-08-16 · high
The approach cut token use 48.9% while lifting task success 10.7 points across three agent benchmarks.
Why now: Covered in the August 16 briefing, while full-trajectory replay is still the default way agents store memory.
A new memory design lifted AI agent task success 10.7 points and cut token use 48.9% across WebArena, WorkArena, and AppWorld, per the paper. Token cost scales with context size, and the standard approach, replaying an agent's full trajectory, means context grows with every finished task. For teams running agents in production, that's the line item to watch.
The alternative stores a reusable procedure instead of the raw trace. It keeps the variable bindings that made the procedure work, the conditions under which it applies, and a check to confirm it worked. It swaps full-trajectory replay for query-conditioned structured memory, pulling up only the relevant procedure instead of the whole history.
Direct trace reuse gets worse as traces get longer, the paper found. An agent's memory degrading the longer it runs is a structural problem, not a bug to patch later.
Full-trajectory replay is still the default memory design in most agent frameworks. This paper says that default works against itself as trajectories grow, so production agents can get worse at their job the longer they run. Watch for tasks that don't break down into procedures with fixed applicability conditions, since the paper doesn't test that case.
Each link below shares sources, entities, or timing with this story.
Shared entities / Same source / Shared topic / Earlier coverage
Both cover AppWorld, Store, WebArena, WorkArena; cite the same source (arXiv); overlapping topics (applicability, appworld, binding, condition).
Shared entities / Same source / Shared topic
Both cover AppWorld, WorkArena; cite the same source (arXiv); overlapping topics (applicability, appworld, binding, condition, cutting).
Shared entity: AppWorld / Same source domain / Shared topic / Earlier coverage
Both cover AppWorld; reported by the same outlet (arxiv.org); overlapping topics (appworld, memory).
Shared entity: Replace / Same source domain / Earlier coverage / Tension
Both cover Replace; reported by the same outlet (arxiv.org); earlier Replace coverage from 2026-08-03.
Shared entity: Direct / Same source domain / Earlier coverage / Downstream implication
Both cover Direct; reported by the same outlet (arxiv.org); earlier Direct coverage from 2026-07-28.
Shared entity: Replace / Same source domain / Earlier coverage / Tension
Both cover Replace; reported by the same outlet (arxiv.org); earlier Replace coverage from 2026-03-22.
Shared entity: Direct / Same source domain / Earlier coverage / Downstream implication
Both cover Direct; reported by the same outlet (arxiv.org); earlier Direct coverage from 2026-03-12.
Shared entity: AppWorld / Same source domain / Earlier coverage
Both cover AppWorld; reported by the same outlet (arxiv.org); earlier AppWorld coverage from 2026-08-12.