Summary
When models run on Windows hosts, they occasionally hallucinate standard POSIX paths (such as /home/user/... or /tmp/...) in arguments to read_file, glob, and grep. These paths fail with raw OS-level errors (e.g. GetFileAttributesEx <workdir>\home: The system cannot find the file specified).
Problem
- In
internal/tools/, path resolution on Windows interprets leading /home/... relative to the current working drive or repository root, causing missing-path errors.
- The model wastes turns retrying non-existent directories rather than adjusting to workspace-relative or Windows paths.
Proposed Solution
- Platform hints on failure: When a tool on Windows receives a
/home/... or root-like POSIX path that does not exist, provide an actionable error hint clarifying the workspace root and host OS.
- Path normalization: Strip synthetic
/home/user/<repo> prefixes when they match workspace-relative targets.
Summary
When models run on Windows hosts, they occasionally hallucinate standard POSIX paths (such as
/home/user/...or/tmp/...) in arguments toread_file,glob, andgrep. These paths fail with raw OS-level errors (e.g.GetFileAttributesEx <workdir>\home: The system cannot find the file specified).Problem
internal/tools/, path resolution on Windows interprets leading/home/...relative to the current working drive or repository root, causing missing-path errors.Proposed Solution
/home/...or root-like POSIX path that does not exist, provide an actionable error hint clarifying the workspace root and host OS./home/user/<repo>prefixes when they match workspace-relative targets.