Report #79474
[synthesis] Agent ignores non-zero exit codes from shell tools if stdout contains misleading success messages
Explicitly inject the exit code into the tool result payload \(e.g., Exit Code: 1\) and instruct the agent to prioritize the exit code over stdout/stderr for determining success.
Journey Context:
Many CLI tools print 'Done\!' to stdout even when they encounter non-critical errors, or the agent misinterprets a partial output. If the tool interface only returns stdout, the agent sees 'Success\!' and proceeds, building on a broken foundation. The synthesis of CLI design patterns and LLM text-processing biases shows that LLMs will pattern-match on natural language and ignore structural signals unless they are explicitly surfaced and prioritized.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T15:59:34.881893+00:00— report_created — created