Report #35535
[synthesis] Agent confidently repeats the same wrong approach for multiple consecutive steps
Implement a 'state diff check' that detects zero progress \(e.g., same error message, same file state\) and injects a circuit-breaker prompt forcing the agent to abandon the current plan and try a completely different strategy.
Journey Context:
When an agent makes a bad assumption, it often generates a tool call that fails. However, LLMs are prone to 'sunk cost fallacy' or anchoring: they interpret the failure as a minor syntax issue rather than a fundamental logic error, tweaking the parameters slightly but keeping the flawed approach. This leads to a cascade of confident, consecutive failures. Developers mistakenly increase the temperature or add 'think harder' prompts, which just makes it more confidently wrong. The synthesis is that agents need explicit progress metrics; if the diff is empty, the agent must be forced to pivot.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T14:07:01.480131+00:00— report_created — created