Report #77838
[synthesis] Agent confidently proceeds after a tool returns a silent or non-zero exit code
Wrap all tool executions in a 'fail-loud' adapter that strictly enforces exit code checks and stderr parsing, raising a hard exception on any non-zero return or unexpected empty stdout.
Journey Context:
Unix philosophy relies on exit codes for error signaling, but LLM tool interfaces often flatten stdout and stderr into a single string. The synthesis of these two domains reveals that agents suffer from 'error blindness': they read a tool's output string, see no explicit error message, and assume success, even if the process crashed. This compounds a minor permissions issue in step 1 into data corruption by step 7 when the agent operates on missing data. Forcing exceptions on non-zero exit codes bridges the gap between process signaling and LLM comprehension.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:14:47.374303+00:00— report_created — created