Report #95443
[synthesis] Why does an agent lose instruction adherence and derail silently after reading large files?
Truncate or summarize tool outputs \*before\* injecting them into the context, and enforce a strict 'context budget' per tool call, even for successful results.
Journey Context:
Developers assume that if a tool call succeeds, the output is 'good' and safe to ingest. However, large outputs \(like reading a 1000-line log file\) dilute the attention mechanism of the model. The agent stops attending to the original system prompt or goal and starts attending to the noise in the log. Failed calls \(which return short errors\) rarely cause this. The synthesis is that successful, verbose tool outputs are often more dangerous than concise errors because they silently erode instruction adherence without triggering a retry loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T18:46:42.913028+00:00— report_created — created