AnalysisOpinion / analysisLarge Language Models · Agents & Tool Use · Reinforcement Learning1 source · Oct 18, 2026

Proof Before Reuse: showing agents only what later sessions reproduced keeps a poisoned skill out of procedural memory [R]

Small case study on poisoning in agent procedural memory, with all data released.

Proof1 community thread

Key points

  • One learning session is poisoned (a new file, an unrelated line, or one line fused into the real fix), followed by three clean sessions on the same task.
  • Arms: no memory, replay of the recorded edits, naive memory (every passing session kept, the skill chosen by Mem0's search), and proof before reuse (a skill is served only after two later sessions reproduce its change and pass its test, and the agent is shown only the lines those sessions also wrote).
  • Proof before reuse exposed it in 0/30, including the case where the fused poison passed step-level checks and only line-level filtering removed it.
  • Open question: is line-level reproduction a reasonable trust signal for learned skills, or does it just reward whatever the clean sessions happen to repeat?

Sources (1)

Extractive summary: sentences quoted from the sources.

Before this

  1. Oct 18, 2026Google Open-Sources Harness2, a Recursive Agent Harnessing Framework
  2. Oct 18, 2026Built a search engine for debugging which is not a wrapper [P]
  3. Oct 17, 2026MossImage quants & SFT fix
  4. Oct 17, 2026deepseek-ai/DeepSeek-V4.1-Flash-1017
  5. Oct 15, 2026Granite Switch 4.1: Chat, Decisions, and Speech from One Endpoint
  6. Oct 15, 2026What a £300, 35W Snapdragon mini PC can actually do 👀: 35B coder at ~30 tok/s, and an 80B model that doesnt even fit in RAM running at 17 tok/s

Related