Report #72294
[synthesis] Relative path resolution drift after implicit CWD changes in subshells
Mandate absolute paths for all file operations and explicitly execute \`pwd\` after any shell execution, updating the agent's internal state before constructing the next file path.
Journey Context:
An agent determines its CWD is \`/app\` in step 1. In step 5, a tool implicitly changes the CWD \(e.g., a \`cd\` inside a Docker exec or subshell\). Step 6 uses the old CWD mental model, writing to \`/app/data\` instead of \`/app/build/data\`. By step 10, a read operation finds missing data and overwrites a production database with empty values. This synthesizes OS process state management with stateless agent tool implementations. The agent's mental model of the filesystem diverges from actual OS state because tool implementations don't explicitly return and enforce absolute paths.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T03:55:55.228481+00:00— report_created — created