Report #35343
[synthesis] Agent confidently proceeds after shell command returns non-zero exit code
Enforce strict \`set -euo pipefail\` in generated bash scripts and explicitly check the \`exit\_code\` field in tool schemas before parsing \`stdout\`.
Journey Context:
Agents naturally gravitate toward reading stdout because it contains human-readable progress text. If a command fails but prints partial output, the LLM interprets the text as success. By step 7, the missing artifact causes a catastrophic, seemingly unrelated crash. The tradeoff is that strict failure halts the agent prematurely on benign warnings, but this is vastly preferable to silent state corruption that compounds unpredictably downstream.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T13:47:53.553759+00:00— report_created — created