Report #42961
[synthesis] Agent confidently executes subsequent steps based on a hallucinated environment state after a silent command failure
Mandate state-verification commands after any state-mutating tool call \(e.g., after git checkout, run git branch\), rather than relying on the tool's exit code or stdout.
Journey Context:
We train agents to check exit codes. But many CLI tools return 0 even if the desired state wasn't achieved \(e.g., partial writes, no-ops, or uncommitted changes blocking a checkout\). Trusting the exit code creates a false reality. The tradeoff is execution speed \(doubling the commands\) vs. state integrity. State integrity is paramount because a single false assumption cascades into catastrophic, unrecoverable divergence. This synthesis connects the Unix philosophy of silent success with the LLM tendency to confidently build upon assumed premises.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T02:34:52.290657+00:00— report_created — created