Codex Windows App failed to start after switching to WSL mode
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.803.10989.0
What subscription do you have?
Plus
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Codex Desktop fails to start when WSL is selected as the execution environment.
The WSL codex app-server process is successfully started by the Desktop application and remains running, but the initialization handshake times out.
Running the same app-server binary manually inside WSL works correctly.
The handshake also works when the app-server is launched manually from Windows through wsl.exe:
'{"method":"initialize","id":1,"params":{"clientInfo":{"name":"test","version":"1"}}}' |
wsl.exe -d Ubuntu -- <codex-binary> -c features.code_mode_host=true app-server --analytics-default-enabled
This successfully returns an initialization response.
So the problem only occurs when Codex Desktop launches and communicates with the app-server in WSL.
What steps can reproduce the bug?
- Install Codex Desktop on Windows.
- Select WSL/Ubuntu as the execution environment.
- Restart/start Codex Desktop.
- Wait for initialization.
What is the expected behavior?
It starts
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the startup failure with Codex Desktop using WSL/Ubuntu, then compare its app-server launch and initialize handshake with the working manual wsl.exe command described in the issue. Done means the Desktop app completes initialization and starts normally in WSL mode; validate against the listed reproduction steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100