VS code extension: Codex not opeing
Resolved 💬 18 comments Opened Nov 6, 2025 by Abhilash842 Closed Nov 11, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the VS Code extension are you using?
0.4.35
What subscription do you have?
Plus
Which IDE are you using?
VS Code
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Updated the codex extensions 24hrs back and it shows loading and has not loaded yet without throwing any error
<img width="356" height="836" alt="Image" src="https://github.com/user-attachments/assets/c5a1c915-d3ec-4924-a379-3a1de78802a0" />
What steps can reproduce the bug?
Updated the VS code extension and it's been in the same state since then
What is the expected behavior?
The codex should start atleast
Additional information
_No response_
18 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I am also facing this issue since yesterday.
If you restart the extension host (or quit and restart VS Code), does the extension load? Or does it get into the same state?
It goes into the same state, tried restart, tried wsl upgrade, nothing works.
There are some errors in the developer console but not sure if they are related to codex
Do you suspect this started when you upgraded to 0.4.35? (I know that VS Code automatically updates extensions, so it's not always obvious when the update occurred.) If you have reason to believe it's related to 0.4.35, could you please downgrade to 0.4.34 to confirm? You could also try switching to the latest prerelease version (0.5.35) which has some newer bug fixes.
I Actually switched to an earlier version which was released 2 weeks back and it's working fine
It get's back to same state
Worked with pre release version
had same issue, changed to "chatgpt.runCodexInWindowsSubsystemForLinux": false, in settings> settings.json and worked.
Happened to me as well. Re-enable the wsl, looks like the update unchecked the WSL on myside.
Hi folks - we've fixed a few bugs with this setting. Please retry on the latest pre-release (0.5.39).
If you are unable to work with WSL, you can disable
runCodexInWindowsSubsystemForLinuxto restore a working extension.<img width="1200" height="446" alt="Image" src="https://github.com/user-attachments/assets/28b1acf3-7505-44e9-8471-796d252915cb" />
@dylan-hurd-oai if you disable runCodexInWindowsSubsystemForLinux then you can't run it in Agent mode.
<img width="412" height="462" alt="Image" src="https://github.com/user-attachments/assets/8395b78e-09e4-4acd-8b31-d8e283fd5538" />
That is correct. Can you try updating to 0.5.39 to see if that fixes your issue with starting in WSL?
<img width="910" height="449" alt="Image" src="https://github.com/user-attachments/assets/fe804c5f-f2fb-4e8f-8fd7-d11c4557971b" />
I don't see that version available on my VS Code. I've also checked for updates and it says that there is no update available.
@dylan-hurd-oai Found the version. It now works. Thank you!
Awesome, thanks for confirming the fix! For anyone else on visiting this issue: 0.5.39 is a pre-release version, so you can try switching to it by selecting
Switch to Pre-Release Version.<img width="1046" height="332" alt="Image" src="https://github.com/user-attachments/assets/3dc42909-d96c-4adb-9eaa-935a5348bec7" />
We'll be promoting this fix to a mainline version first thing tomorrow. Thank you for patience while we fix these issues.
Closing this issue for tracking purposes. If you're still seeing bugs, please open a new issue with a detailed report and we'll investigate.
This worked for me cheers mate