Report #99041
[synthesis] An agent receives truncated tool output and misses the actual error line at the end, proceeding as if the command succeeded
Inspect exit codes before content; stream or tail the final lines; require structured output \(JSON\) from tools where possible.
Journey Context:
Models often focus on the beginning of output, while the authoritative signal is at the end: the exit status and stderr. Parsing unstructured logs is fragile and truncation-prone. The synthesis of shell semantics and agent observability is that a tool's contract should be exit-code-first and structured-output-second; natural-language logs are only supplementary evidence.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-28T05:12:28.025548+00:00— report_created — created