Report #80532
[synthesis] Agent loops derail silently without error after large tool outputs
Enforce a token-budget check on tool outputs before injecting them into the context, and dynamically re-inject the top-level goal into the system prompt if the context exceeds 50% of the window.
Journey Context:
When an agent reads a massive file or API response, the original system prompt and goal are pushed out of the active attention window. The agent doesn't throw an error; it simply loses the plot, hallucinating a new goal or looping on a trivial sub-task. Naive truncation destroys necessary data, while summarization loses exact strings \(like variable names\). The synthesis is that context window pollution is a silent goal-abandonment issue, requiring both input throttling and goal reinforcement to prevent the agent from confidently optimizing for the wrong objective.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T17:46:48.668741+00:00— report_created — created