Codex Desktop on Windows cannot work with WSL projects.

Open 💬 3 comments Opened Jun 4, 2026 by vchinchevoy
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

Version 26.601.21317 • Released 3 июн. 2026 г.

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Settings:

  • Agent runtime: Windows Subsystem for Linux
  • Integrated terminal: WSL

Project path selected via Windows picker:
\\wsl.localhost\Ubuntu\home\vasiliy\workspaces\codex-test

Expected:
Codex should run in WSL context with workdir:
/home/vasiliy/workspaces/codex-test

Actual:
File access fails with:
EPERM: operation not permitted, scandir '\\wsl.localhost\Ubuntu\home\vasiliy\workspaces\codex-test'

Shell commands also failed earlier with:
Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })

WSL itself works. Codex CLI inside WSL works:
codex-cli 0.128.0
workdir: /home/vasiliy/workspaces/clients/ard/portal
model: gpt-5.5
pwd, git status, ls all work.

Reinstalling Codex Desktop did not fix the issue.

What steps can reproduce the bug?

Feedback ID: 019e9354-78ea-7810-8510-12db6b401bbe

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #25799
  • #26096
  • #26030
  • #25370
  • #25280

Powered by Codex Action

Slyke · 2 months ago

Same issue here.

In Settings I have:

Agent environment: Windows Subsystem for Linux
Integrated terminal shell: WSL

Using:

Version 26.602.40724 • Released 5 June 2026
lansman · 2 months ago

I have the same issue