Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-07-21 · high
Terminal-Bench 2.0 scores jumped 8.3 points when timing beat retrieval on injecting reminders.
Why now: Covered in the July 21 briefing on long-run agent decay.
A second agent decides when to inject a reminder into a first agent's long task, lifting Terminal-Bench 2.0 scores 8.3 points, per the arXiv paper 'Remember When It Matters' (2607.08716).
That's a rare hard number on a real failure mode: agents burying or dropping instructions given at the start once a task runs long. Anyone running unattended agents past a few dozen steps, coding agents, support loops, or ops automation, has probably hit this already.
One agent does the task. A second, dedicated memory agent watches it work.
No fixed timer. No passive bank waiting to be queried. Reminders land only at the moment they matter.
The gain held on a second benchmark, τ²-Bench, at 6.8 percentage points. It showed up for both weak and strong action agents, evidence the fix targets a structural gap, not a weak model's shortfall.
The paper's own comparison is the interesting part: selective, timed injection beat both a passive memory bank and always-on injection. I'd have bet on always-on being safer. It lost anyway, apparently because constant reminders bury the one that matters under noise.
It bolts onto an existing agent framework rather than replacing it, which is good news if you've already got one built. I want to know what running a second agent watching the first costs in tokens or latency, something the paper doesn't say.
Each link below shares sources, entities, or timing with this story.
Shared entities / Same source domain / Shared topic / Earlier coverage
Both cover Bench, Terminal; reported by the same outlet (arxiv.org); overlapping topics (agent, beat, behavioral, context).
Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Both cover Bench, Terminal; reported by the same outlet (arxiv.org); overlapping topics (action, agent).
Shared entities / Same source domain / Shared topic / Earlier coverage
Both cover Bench, Terminal; reported by the same outlet (arxiv.org); overlapping topics (agent, context).
Shared entities / Same source domain / Earlier coverage / Tension
Both cover Bench, Terminal; reported by the same outlet (arxiv.org); earlier Bench coverage from 2026-06-18.
Shared entities / Shared topic / Earlier coverage / Tension
Both cover Bench, Terminal; overlapping topics (agent, context); earlier Bench coverage from 2026-05-14.
Shared entity: Bench / Same source domain / Shared topic / Earlier coverage
Both cover Bench; reported by the same outlet (arxiv.org); overlapping topics (agent, context, memory).
Both cover Bench; reported by the same outlet (arxiv.org); overlapping topics (agent, existing, memory).
Shared entity: Terminal / Same source domain / Shared topic / Earlier coverage
Both cover Terminal; reported by the same outlet (arxiv.org); overlapping topics (agent, context, memory).