In the Codex Windows Desktop App, file read and edit operations fail entirely, while the same operations work correctly in Codex CLI.

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.609.41114 • Released 2026. 6. 13.

What subscription do you have?

plus

What platform is your computer?

Microsoft Windows11 x64

What issue are you seeing?

Summary

In the Codex Windows Desktop App, file read and edit operations fail entirely, while the same operations work correctly in Codex CLI.

The issue is stable and fully reproducible. Files are visible and accessible via shell commands in the terminal, but the app's internal tools cannot read or modify them. The problem persists even when a terminal is opened from within the same directory inside the app.

Environment

• Product: Codex Windows Desktop App
• Platform: Windows [버전] x64
• Reproduces in: Windows local workspace
• Does not reproduce in: Codex CLI (direct terminal)

What steps can reproduce the bug?

Steps to Reproduce

1. Open the Codex Windows Desktop App.
2. Open or create a workspace with existing files.
3. Ask Codex to read or edit any file in the working directory.
4. Observe that the operation fails — the app reports it cannot access the file.
5. Open a terminal in the same directory and run the same operation manually — it succeeds.

What is the expected behavior?

The Codex Windows Desktop App should be able to read and edit files in the working directory, consistent with the behavior of Codex CLI in the same environment.

Additional information

Things Already Tried

The issue persisted after all of the following:

1. Re-login
2. Reinstalling the app
3. Deleting config.toml and reinstalling
4. Deleting all related registry entries and the .codex folder, then reinstalling
5. Forcing commands via PowerShell and verifying responses

None of the above resolved the issue.

Additional Notes

This appears to be a filesystem access inconsistency between the Windows Desktop App and the CLI. The app and CLI seem to handle file system permissions differently — the CLI accesses files directly, while the app may route through an internal layer (possibly WSL path mapping, similar to #25860) that breaks file resolution.