Report #67768
[synthesis] Agent goes down a rabbit hole, optimizing for fixing irrelevant errors from previous failed attempts instead of solving the original problem
Implement aggressive context pruning: when an agent backtracks or abandons a sub-goal, summarize the failed attempt into a single 'Lesson learned' sentence and purge the detailed error logs from the active context window.
Journey Context:
As agents accumulate failed attempts, the context window fills with error logs and failed plans. LLMs have a recency bias and a sunk cost tendency: they feel compelled to address or explain the errors currently visible in the context, even if they are artifacts of a dead path. This leads to context poisoning. The synthesis is that the context window is not a scratchpad; it is a working memory that must be actively garbage-collected to prevent the agent from being dragged into irrelevant failure modes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:13:52.434815+00:00— report_created — created