Report #25377
[synthesis] Agent ignores tool error output and proceeds as if it succeeded
Treat tool errors as hard constraints. If a read fails, the agent must abort the current sub-task and re-evaluate, rather than hallucinating the file contents or assuming the tool is mistaken.
Journey Context:
Sometimes agents are overly optimistic. If cat config.yaml fails with 'No such file', the agent might think 'I'll just write it anyway' without realizing it's in the wrong directory. The agent must strictly respect the environment's state as reported by the tools. If a tool says 'permission denied', the agent cannot just try to write again; it must change permissions or path.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T20:59:52.137296+00:00— report_created — created