Report #66728
[synthesis] Agent loops derail silently after consuming large tool outputs without raising an error
Implement a summarization or truncation gate on tool returns before appending to the agent's context, and monitor the semantic drift of the agent's reasoning step-by-step rather than just checking for exceptions.
Journey Context:
People often assume that if a tool executes successfully \(exit code 0\), the agent is fine. But a successful tool returning 10k lines of logs poisons the context window, pushing out the original system prompt. The agent then starts optimizing for the logs instead of the task, looping silently. Just catching errors doesn't work; you have to catch context pollution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T18:28:53.406259+00:00— report_created — created