Fetching from the wire…
Public story · 2026-07-17 · high
A tabular bandit decides when agents retrieve, reuse, or forget memory, using only pass or fail feedback, no pretraining required.
Why now: Agent memory management is turning into its own research problem as agents run longer, and this paper is among the first to treat the retrieve-or-forget decision as something to learn instead of hardcode.
MemCon frames agent memory management as a Markov Decision Process, per the paper. An online policy decides when to retrieve a memory, reuse a saved plan, re-query after getting stuck, or consolidate and forget.
Across 6 benchmarks, 3 agent frameworks, and 3 model backbones, the policy lifted task success by up to 15.2 points, according to the paper. It also cut token use 5 to 20%. That's a rare pairing. Most memory fixes buy accuracy with more tokens, or save tokens by losing accuracy.
The policy isn't a trained model. It's a tabular contextual bandit with UCB exploration, and it only needs binary success or fail signals from finished tasks to update. No pretraining step, no labeled memory dataset.
The paper doesn't say how the policy holds up once an agent's memory store grows well past what these six benchmarks tested. It also doesn't say whether UCB exploration adds latency to retrieval decisions inside a live agent loop.
The no-pretraining part is the detail I'd weigh more than the 15-point headline number. A big accuracy jump is easy to lose once you change benchmarks or swap backbones. A bandit that learns from pass/fail signals and skips training is what actually survives being dropped into an already-running agent stack. It doesn't ask for a training set first.
Each link below shares sources, entities, or timing with this story.
arXiv 2608.05906 keeps a dual-polarity memory of verified corrections and observed dead ends for Text-to-SQL repair: 66.34% to 69.79% on Spider, 47.35% to 48.44% on BIRD. Then the authors say the quiet part: paired analysis supports the Spider gain but is weak on BIRD, MERIT i...
SpecFirst splits the loop in two: a spec agent probes the binary and fuses observations with documentation into a structured specification, then a separate synthesis agent codes against that fixed reference. Test pass rates rose 6.9-21.3% and binary exploration coverage 9.4-18...
MemSyco-Bench points out that memory benchmarks test whether memories are correctly stored, retrieved, and updated, never whether the retrieved memory should have influenced the decision at all. Its five tasks check whether agents can reject memory as factual evidence, respect...
CAFE (arXiv 2608.24794) makes corrective feedback an in-trajectory intervention the agent chooses to request, using one shared-parameter model alternating between search-agent and critic roles. Online RL shapes request returns from a prompt-level call-versus-skip success gap;...
Agents share transport and can call each other's tools but have no way to reconcile a fact phrased two ways (arXiv 2608.16357). Every incoming claim passes a five-outcome procedure (insert, merge, relate, conflict, reject) decided from scoped claim-key identity, embedding simi...
arXiv 2607.23982 adapts Holmström's team moral-hazard model into a game where an agent can keep an immediate local reward or pay a query cost to surface a hidden safety fact that mainly helps another agent's downstream decision. Base behavior splits into two failure modes: pre...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.