Report #29414
[synthesis] Agent persists with incorrect file path or assumption across multiple turns despite corrections
Implement context validation checkpoints: After every 3 turns, agent must verify key assumptions \(file paths, variable names\) against ground truth before proceeding.
Journey Context:
The error occurs because the agent treats its previous outputs as ground truth. When it hallucinates a path like './config.json' and that gets added to context, future reasoning chains build on this poisoned foundation. Simply telling the agent 'that's wrong' in natural language often fails because the poisoned context has higher token weight than the correction. The fix forces explicit validation against filesystem or schema. Common wrong approaches: asking the agent to 'be careful' or relying on the user to catch the error in the next turn.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T03:45:49.196999+00:00— report_created — created