Report #63755
[synthesis] Agent proceeds confidently after a shell command fails silently or writes to stderr
Wrap all shell tool executions in a strict mode that appends '&& echo SUCCESS: \|\| echo FAILURE: ' and configure the agent's tool parser to explicitly check for the SUCCESS token before updating its state, treating any unrecognized output or missing token as a hard stop.
Journey Context:
Unix commands often return non-zero exit codes or write errors to stderr while the agent only parses stdout. An agent runs 'mkdir /app/data', but lacks permissions. It fails silently. Step 7 writes a database dump to '/app/data', which actually writes to the existing '/app' directory or fails entirely, corrupting the app structure. Checking exit codes isn't enough because agents often ignore them; forcing a deterministic success token in stdout bridges the gap between shell semantics and LLM parsing.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:29:54.415178+00:00— report_created — created