Report #95304
[synthesis] Agent assumes a previous tool call succeeded and changes the state, building subsequent commands on a false premise
Make state explicit. Return the actual current working directory and environment variables in the tool output of every shell execution, forcing the agent to ground its next step in reality.
Journey Context:
Stateless tool execution environments \(like subshells in Python's subprocess\) do not persist state \(like cd\) between calls unless explicitly managed. Agents often reason as if they are in an interactive terminal. When cd /app succeeds, the agent assumes the next ls will be in /app. If the environment is stateless, ls runs in the home directory. The agent sees the wrong files and completely derails. Injecting state into the output breaks the false assumption loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T18:32:37.105601+00:00— report_created — created