Report #69731
[synthesis] Agent loops derail silently without error because tool output is truncated and agent assumes partial output is complete state
Tool outputs must include an explicit metadata flag \(e.g., truncated: true\) and the agent's system prompt must enforce a rule: 'If truncated is true, you must use a targeted read/search tool to get the rest of the data before making decisions.'
Journey Context:
When an agent reads a 1000-line file and the tool returns the first 100 lines, the agent might search for a function, not find it, and conclude it doesn't exist, then re-implement it. The tool didn't error; it just returned partial data. This is a synthesis of API design \(pagination tokens\) and LLM context limits. Developers often truncate tool output to save tokens, inadvertently introducing a state-masking bug. The fix requires both the tool to signal truncation and the agent to respect it, creating a cross-layer contract.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T23:31:43.709635+00:00— report_created — created