Report #50537
[synthesis] Agent resumes a failed run and immediately repeats the exact same failing steps due to poisoned scratchpad context
When restarting an agent, summarize the reasons for failure from the previous run rather than injecting the raw, lengthy scratchpad of the failed attempt.
Journey Context:
Developers often try to save compute by feeding the entire context of a failed run back into a new agent instance, saying you failed, try again. The agent then gets stuck in the same local minimum because the scratchpad provides a highly conditioned path towards the same failure. The synthesis of cognitive bias \(anchoring\) and LLM context dynamics shows that raw history anchors the model. You must distill the history into abstract constraints \(Do not use tool X because Y\) to break the failure chain.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T15:18:37.454228+00:00— report_created — created