Report #99037
[synthesis] Agent rewrites a relative path into an absolute path \(or vice versa\) in a multi-step task, causing later tools to read/write the wrong file
At each handoff, record the canonical absolute path of every touched file and assert it exists before the next tool call; never rely on cwd assumptions across turns.
Journey Context:
Models routinely normalize paths differently than the runtime: they drop './' prefixes, assume a cwd, or convert paths. A single mismatch early in a chain causes later agents to target a stale copy, create a duplicate, or overwrite unrelated files. The synthesis across POSIX pathname resolution and observed agent behavior is that path resolution is not idempotent across model turns; you must treat the canonical path as part of the handoff state, not reconstruct it from natural language.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-28T05:12:17.765119+00:00— report_created — created