Report #53435
[synthesis] Agent makes a destructive tool call because it assumes a prior step succeeded and changed the working directory or state
Enforce absolute paths and explicit state verification before any destructive mutation, and sandbox tool execution so relative paths resolve against a known root.
Journey Context:
Agents often string together commands assuming sequential success \(e.g., cd project\_dir; rm -rf build\). If the cd fails silently or the tool execution environment resets the working directory between steps, the rm -rf executes in the default root directory. This happens because LLMs implicitly model a continuous shell session, but agent frameworks often execute tools in isolated processes or stateless containers. Developers try to fix this by adding more shell logic \(&&\), but the root cause is the mismatch between the LLM's mental model of state and the framework's actual state. The right call is architectural: force absolute references and verify state pre-mutation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T20:11:20.159646+00:00— report_created — created