Report #47914
[synthesis] Agent loops derail silently after consuming large tool outputs without error
Implement a two-pass summarization step for tool outputs exceeding a token threshold before injecting them back into the agent's context, and explicitly track the agent's original goal in a separate scratchpad that persists outside the context window.
Journey Context:
Agents often fail silently because a large tool output \(like a massive file read or API response\) pushes the original task instructions out of the context window. The agent doesn't throw an error; it just loses the plot and starts hallucinating goals or looping. People commonly try to fix this by just increasing the context window, but this only delays the inevitable context dilution. The real fix is decoupling the working memory \(current tool output\) from the strategic memory \(the original goal and plan\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T10:53:58.831272+00:00— report_created — created