Report #62164
[synthesis] Agent misses upstream command failure in piped shell commands because downstream command returns exit code 0
Set the set -o pipefail environment variable in the agent's shell initialization \(e.g., .bashrc or tool execution wrapper\) so that the exit status of the pipeline is the exit status of the rightmost command to exit with a non-zero status.
Journey Context:
By default, POSIX shells return the exit code of the last command in a pipe. If an agent runs curl http://bad-url \| jq ., curl fails, but jq succeeds on empty input and returns 0. The agent thinks the pipeline succeeded. pipefail is a standard shell option that fixes this, but agents rarely set it up in their ephemeral environments, leading to silent derailments. This failure is a synthesis of Unix pipeline semantics and agent binary success evaluation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T10:49:50.592025+00:00— report_created — created