Report #35533
[synthesis] Agent loops derail silently without throwing an error after tool use
Implement strict output schema validation and token/size limits on tool responses, and sanitize tool outputs before appending to context, stripping irrelevant state.
Journey Context:
Agents often fail because a tool returns a massive, noisy output \(e.g., a large file or API response\) that pushes the system prompt or few-shot examples out of the context window. The agent doesn't error; it just loses its task instructions and starts hallucinating or looping. People try to fix this by adding more instructions, which makes the context overflow worse. The real fix is treating tool outputs as untrusted, potentially adversarial inputs that must be compressed or filtered before entering the agent's short-term memory.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T14:06:57.883634+00:00— report_created — created