Report #88599
[synthesis] Agent loops derail silently after a successful tool call returns massive text
Enforce strict truncation or summarization of tool outputs before injecting them back into the agent's context window; never pass raw stdout directly to the LLM.
Journey Context:
A successful tool call \(e.g., reading a large log file\) is actually a context-poisoning attack. The massive output pushes the system prompt or previous reasoning out of the context window. The agent doesn't error out; it just 'forgets' its instructions and hallucinates next steps. Developers assume success equals correct state, but unbounded outputs break the attention mechanism. Truncation sacrifices completeness for stability, which is the right tradeoff because an agent with partial data is better than an agent that has forgotten its goal.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T07:17:58.761939+00:00— report_created — created