Windows App: WSL file links and built-in browser preview do not work for WSL projects

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

Version 26.623.61825

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Feedback ID: 019f12f4-80ce-7d41-bd4e-8ea3e29bc26e

I am using Codex Windows App with a project running in WSL2 Ubuntu.

Codex shows interactive file links using Linux/WSL absolute paths, for example /home/nv/code/NtkDocs/AGENTS.md. When I click these links in the Windows Codex App, nothing opens. The app does not seem to translate the WSL path to a Windows-accessible path such as \\wsl.localhost\Ubuntu\home\nv\code\NtkDocs\AGENTS.md.

The built-in Codex browser / web page preview is also not usable for this WSL project. As a result, I cannot reliably verify the web version of the app from inside Codex, even though the project is intentionally developed and tested in WSL to match the Linux/VPS production environment.

What steps can reproduce the bug?

1. Use Codex Windows App version 26.623.61825 on Windows with WSL2 Ubuntu.
2. Open or attach a Codex workspace located inside WSL, for example /home/nv/code/NtkDocs.
3. Confirm the same project is accessible from Windows Explorer through \\wsl.localhost\Ubuntu\home\nv\code\NtkDocs.
4. Ask Codex to modify or reference a file in the workspace so that it produces an interactive file link, for example /home/nv/code/NtkDocs/AGENTS.md.
5. Click the interactive file link in the Codex Windows App.
6. Observe that nothing opens.
7. Start a web app/dev server inside WSL and try to use the built-in Codex browser / web page preview to verify it.
8. Observe that the built-in preview is not usable for checking the WSL-hosted web app.

What is the expected behavior?

Codex Windows App should support WSL-aware file and browser workflows.

File links like /home/nv/code/NtkDocs/... should open through a valid Windows/WSL mapping such as \\wsl.localhost\Ubuntu\home\nv\code\NtkDocs\....

Code files should be routed to the configured “Open in” target, such as VS Code Remote WSL.

Non-code files such as .docx, .pdf, .jpeg/.png, and exports should open via Windows Explorer/default apps through the WSL UNC path.

Built-in browser/web preview should be able to access and test web apps served from inside WSL, or clearly provide the correct localhost/WSL forwarding URL.

Additional information

This breaks the normal development loop in Codex:

• I cannot open generated files from Codex links.
• I cannot preview/check the web app through the built-in Codex browser.
• I cannot verify generated UI or document outputs without manually translating paths or leaving Codex.
• This is especially painful for document-generation workflows with .docx, .pdf, .jpeg/.png, and exports.

Manual workaround: convert paths like /home/nv/code/NtkDocs/path/to/file.pdf to \\wsl.localhost\Ubuntu\home\nv\code\NtkDocs\path\to\file.pdf and open them outside Codex.

For browser checks, I have to leave Codex and open the app manually in a normal Windows browser, if the WSL port is reachable.

Ideally the WSL path mapping and browser preview routing should be automatic when the session is attached to WSL, or configurable per project.