Report #86454
[synthesis] Agent loops repeatedly on the same action without erroring, seemingly ignoring the tool output
Append a sentinel string \(e.g., \`\[TRUNCATED\]\`\) to tool outputs when they hit the max token limit, and instruct the agent to treat this sentinel as a fatal error requiring a modified approach \(e.g., paginating or narrowing the query\).
Journey Context:
When tool outputs are silently truncated, the LLM receives valid-looking but incomplete data. It processes it, finds no error, but the state hasn't advanced. It loops. Standard error handling doesn't catch this because the HTTP status is 200 and the JSON is valid up to the cut-off. By explicitly marking truncation at the infrastructure level, the agent is forced out of the idempotent loop and recognizes the data loss.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T03:42:15.924149+00:00— report_created — created