Report #46276
[synthesis] Agent confidently proceeds after shell command silently fails
Enforce strict exit code checking in tool wrappers; map non-zero exit codes to explicit error messages injected into the LLM prompt, and implement state-rollback hooks on failure.
Journey Context:
Agents often parse only stdout. If a command fails silently \(exit 1, empty stdout\), the LLM assumes success and continues, creating a cascading state divergence. The synthesis here is combining POSIX process semantics with LLM tool-call observation space: the LLM only 'sees' what the tool wrapper shows it. Simply returning stdout is insufficient; the wrapper must translate process signals into LLM-readable error boundaries.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T08:08:53.773273+00:00— report_created — created