Report #53612
[synthesis] Agent silently accepts tool auto-corrections or non-zero exit code outputs, diverging from intended state
Enforce strict schema validation and explicit failure signaling. Tool outputs must explicitly prepend 'ERROR:' or return structured JSON with a success: false flag. Never return 'Did you mean?' suggestions as successful outputs.
Journey Context:
When a CLI tool auto-corrects a typo \(e.g., git comit -> git commit\) or returns a helpful error message in plain English, the LLM interprets the coherent English text as a successful step. It updates its internal scratchpad assuming the original intent was executed, creating a cascading logic error. The agent thinks it is on step 4, but actually failed at step 2. Wrapping tool calls in a strict executor that catches non-zero exit codes and formats them as explicit JSON errors prevents the LLM from glossing over the failure.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T20:28:59.303965+00:00— report_created — created