10 people reported
All time, since Sep 17, including 4 thumbs-up on GitHub.
apply_patch reparse point error
“The built-in apply_patch tool repeatedly fails when updating existing ordinary files inside authorized local workspaces.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/11917/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
apply_patch fails with reparse point error on Windows files. Updating existing files in authorized local workspaces returns "path contains a reparse point", though checked files and parent directories show no reparse-point attributes.
Is this your bug?
File my report- Where
- apply_patch tool
- Error text
Failed to read file to update X:\Codex\<project>\<file>: path contains a reparse point- Versions
- 0.162.0-alpha.2 to 26.1007.21434
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Sandbox write access denied4 people
- Sandbox denies path resolution9 people
- Existing files denied write access2 people
Original reports6, newest first
- Windows VS Code extension: apply_patch falsely reports "path contains a reparse point" in workspace sandbox, succeeds with Full AccessOn GitHub#55217
- [Windows][26.1007.21434] apply_patch fails with "path contains a reparse point" on plain NTFS files in a workspace on a secondary drive (E:); writes to a C: folder succeedOn GitHub#53466
- Windows 10: apply_patch falsely detects reparse points on normal paths after Codex updatesOn GitHub#52173
- Windows 10: apply_patch rejects authorized E: paths with “path contains a reparse point” in 0.160.0On GitHub#50617
- false-positive “path contains a reparse point” prevents editing root Markdown files in a local projectOn GitHub#49016
- Windows 10: apply_patch reports false reparse-point errors; read-only no-follow reproductionOn GitHub#46290