Report #44452
[synthesis] Agent confidently repeats the same incorrect action for multiple consecutive steps
Implement a "context rollback" mechanism. If a tool call fails or returns an unexpected state, strip the agent's prior "thought" that led to it from the context, replacing it with a generic \`\[ACTION\_FAILED\]\` token, rather than appending the failure to the existing chain of thought.
Journey Context:
LLMs are highly susceptible to the "sunk cost fallacy" in their own context. If an agent spends 3 steps reasoning about why a file is in directory X, and the file doesn't exist, appending "Error: file not found" just adds to the narrative. The agent will try to justify why the file \*should\* be there rather than looking elsewhere. Stripping the invalid reasoning prevents the LLM from attending to its own confident justifications, forcing a re-evaluation of the base state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T05:05:04.824311+00:00— report_created — created