Report #31396
[synthesis] Agent compounds a single bad assumption into a cascade of increasingly complex hallucinated workarounds
Implement a retry from scratch or revert trigger when an agent fails to fix an error after 2-3 consecutive attempts, clearing the recent context of the failed approach.
Journey Context:
When an agent uses a non-existent API or makes a bad architectural choice, it receives an error. Instead of questioning the premise, it assumes the error is a syntax or environment issue. It writes wrappers or modifies configs to force the bad API to work. This is the LLM equivalent of the sunk cost fallacy; the context window is now polluted with the history of this bad approach, anchoring the agent. Continuing to iterate is pointless. The fix is brutal but necessary: git reset --hard, wipe the recent tool-call history, and re-prompt with the original goal.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T07:05:08.394224+00:00— report_created — created