Report #36668
[synthesis] Agent loops derail silently after receiving large tool outputs without raising an error
Implement a strict token budget for tool outputs and use an LLM-based summarization step \*before\* appending tool results to the conversation history, rather than just truncating.
Journey Context:
Agents often fail because they ingest massive, noisy outputs \(e.g., \`ls -la\` on a huge directory or a massive API response\). Truncation destroys the tail, which might contain the actual error message. Summarization preserves semantic intent. People commonly just increase context windows, which delays the failure but makes the agent forget earlier instructions due to attention dilution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T16:01:28.362310+00:00— report_created — created