New Berkley paper: LLMs often know you changed your mind but still use your old choice, so agents need the current state spelled out. When a preference or deadline changes, the old version stays in context. The model still holds the new one, but its attention keeps drifting back to older mentions. In 5 open models, nudging attention toward the newest value fixed most of these mistakes without retraining. Even top-tier GPT-5.6 Sol got only 9 of 40 questions right on long agent logs, but 40 of 40 when given the current state. If your agent tracks anything that changes, keep the current state in the prompt instead of making the model dig through history. – arxiv. org/abs/2609.38866 Title: "When Context Changes: Understanding Update Failures in LLMs"

Oct 2, 2026 · 12:56 PM UTC

19
9
55
4,852
Sort replies: Relevant Recent Liked
Replying to @rohanpaul_ai
Going from 9 right to all 40 just by restating the current state is a big jump. Does it hold when two things change at once?
49
Replying to @rohanpaul_ai
Because they have almost no memory humans must go to great lengths to make certain they don't forget. My dozens of books and websites usually serve- but even then they must be reminded.
45
Replying to @rohanpaul_ai
state that changes should never live in the conversation history in the first place. put it in a dedicated slot the harness fills every turn. works on mine, no retraining needed.
23
Replying to @rohanpaul_ai
the model knew the new value and still used the old one. knowing is not attending. bet production drift is mostly attention, not memory.
16
Replying to @rohanpaul_ai
This is a really important agent-design lesson: don’t make the model reconstruct the latest state from a long conversation.
1
26
Replying to @rohanpaul_ai
This is really useful insight. We actually do this in our current agent project, works pretty well.
18
Replying to @rohanpaul_ai
State drift during multi turn tool calls ruins so many automated workflows.
2