Codex App for Windows fail to startup in WSL Agent mode
Open 💬 6 comments Opened Apr 9, 2026 by lifei
💡 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)?
26.406.31014
What subscription do you have?
free
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
When using the setting "runcodexinwindowssubsystemforlinux": true, the app always stuck in the login UI.
I have to modify the file $env:USERPROFILE\.codex\.codex-global-state.json to remove the following code:"runcodexinwindowssubsystemforlinux": true.
It fails to startup in VSCode extension too.
What steps can reproduce the bug?
- Go to settings page, switch
Agent environmenttoWindows Subsystem for Linux. - Exit the App and restart it.
- Stuck in the login UI.
- open
$env:USERPROFILE\.codex\.codex-global-state.json, and remove the following code:
"runcodexinwindowssubsystemforlinux": true
- Open the App again, and it runs fine.
What is the expected behavior?
_No response_
Additional information
_No response_
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
when stuck in the login UI, can not login or enter key, no any response.
I have review both two issues above. I think either of them is a duplicate.
I am also running into this. I tried moving my
.codexfolder over from windows to WSL since the docs say they should be identical but that didn't work. I also tried running and logging in via CLI in WSL first before launching codex to make sure at least the auth was there but it still lead to this broken Codex state.Same issue for me... codex cli works in WSL, $CODEX_HOME set to my windows home .codex folder so they are in sync..
Change the agent to WSL and all I get on restart is a login window that stalls if I re-enter my API key and click continue.....
Only way to fix is kill and set runcodexinwindowssubsystemforlinux=false... 👎