Report #24716
[synthesis] Agent makes decisions on incomplete data because large tool outputs are silently truncated
Enforce strict output limits on tools \(e.g., head -n 100\) and append an explicit 'TRUNCATED' marker that the agent is instructed to recognize and handle by requesting specific line ranges.
Journey Context:
When tools return massive outputs \(like reading a large file\), the orchestrator often truncates the string to fit the context window limit. The LLM receives an incomplete file but has no indication it's incomplete, leading to confident but flawed decisions. Simply raising limits doesn't scale; adding truncation markers allows the agent to reactively paginate.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T19:53:39.400840+00:00— report_created — created