Codex process errored: Codex process is not available

Resolved 💬 27 comments Opened Nov 10, 2025 by MoonS11 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.56.0

What subscription do you have?

nothing

Which IDE are you using?

vscode

What platform is your computer?

Windows 10 Professional

What issue are you seeing?

I was using the Codex extension in VSCode. When I switched from chat mode to agent mode, it prompted me to re-enter from WSL. After that, Codex showed the message: Codex crashed with the following error:Codex process errored: Codex process is not availableI checked the VSCode output:2025-11-10 08:44:53.862 [error] unable to parse stdout from codex app-server: SyntaxError: Unexpected end of JSON input2025-11-10 08:44:53.862 [error] unable to parse stdout from codex app-server: SyntaxError: Unexpected token 'N', "NX[(WwQ g@b�c�O" is not valid JSON2025-11-10 08:44:53.863 [error] unable to parse stdout from codex app-server: SyntaxError: Unexpected token 'T', "T�y�v^FR�S^B0" is not valid JSON2025-11-10 08:44:53.863 [error] unable to parse stdout from codex app-server: SyntaxError: Unexpected token '

!Image

!Image

!Image

!Image

What steps can reproduce the bug?

Switch from chat mode to agent mode

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

27 Comments

github-actions[bot] contributor · 8 months ago

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

  • #6318
  • #6314
  • #6304
  • #6192
  • #6178

Powered by Codex Action

sademban · 8 months ago

i have been facing this since this morning, is there any fix on this? i opened in wsl it works but when i open with windows it gives me this issue and i tried setting
[general]
run_in_wsl = false

it did not work.

is this erro due to current update

dylan-hurd-oai contributor · 8 months ago

@sademban @MoonS11 can you try disabling the setting in VS Code settings?

<img width="830" height="447" alt="Image" src="https://github.com/user-attachments/assets/cd019181-c401-4376-b336-e8deebcd7f53" />

sademban · 8 months ago

@dyli-oai yes i tried by setting "chatgpt.runCodexInWindowsSubsystemForLinux": false, it started working but when i want to switch to agent mode not agent(full access) which works in wsl. it does not start. why does it have to be this way. is it mandatroy for us to give full-access??

working when turned off:

<img width="802" height="769" alt="Image" src="https://github.com/user-attachments/assets/5035e0d4-be3d-4a07-bd1c-44013e8c4173" />

not working when turned on:

<img width="1342" height="769" alt="Image" src="https://github.com/user-attachments/assets/4b789bb8-23eb-4f27-9c5c-764754dcfc29" />

or am i doing something wrong?? or integration with WSL is having issue

anda88 · 8 months ago

我也遇到了同样的问题。

anda88 · 8 months ago

周六还可以在vscode中正常使用codex 插件(选择run in wsl ),今天就不行了。

bekingjx · 8 months ago

I've got the same problem, I switched to Agent mode then when enabling the WSL connection it brokes up like the screenshot. Now I've switched back and using it with Full Access.
I'm following for the fix.

mcorcos · 8 months ago

not workingggg

L9my · 8 months ago

Same issue for me

VorlonCD · 8 months ago
xingqiux · 8 months ago

I have the same

NolanLXY · 8 months ago

I have the same question, but my friend can work as usual. We have tried many ways to work it out, such as reloading Codex with a different version, reinstalling WSL, and fixing the environment configuration.

tismatic · 8 months ago

I am also having this issue. I set up Codex and WSL on my desktop recently in order to use Agent mode and it worked flawlessly but after repeating the same steps on my laptop I get this issue. I also tried on my work laptop and have the same problem. I've tried many of what other have already tried and did a stare and compare across machines and I can't seem to find any configuration differences.

dylan-hurd-oai contributor · 8 months ago

We've addressed a few bugs with the WSL setting - please try downloading the latest pre-release (0.5.39), or you can turn off the chatgpt.runCodexInWindowsSubsystemForLinux setting.

<img width="1175" height="440" alt="Image" src="https://github.com/user-attachments/assets/a46b4596-057d-4e90-9b41-64b3c511cdc9" />

tismatic · 8 months ago
We've addressed a few bugs with the WSL setting - please try downloading the latest pre-release (0.5.39) or you can turn off the chatgpt.runCodexInWindowsSubsystemForLinux setting. <img alt="Image" width="1175" height="440" src="https://private-user-images.githubusercontent.com/220976066/512486047-a46b4596-057d-4e90-9b41-64b3c511cdc9.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjI4MzAxMjgsIm5iZiI6MTc2MjgyOTgyOCwicGF0aCI6Ii8yMjA5NzYwNjYvNTEyNDg2MDQ3LWE0NmI0NTk2LTA1N2QtNGU5MC05YjQxLTY0YjNjNTExY2RjOS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUxMTExJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MTExMVQwMjU3MDhaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03Y2FjMjZiNDhkZTQwMDM3M2JiOTY0NDA0MzhmNTIyZmJmMTI0MWE2MTM4NTA1ODIyODUzZDVkYTdkOTk5NTM5JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.XFWpErcb3orS7EvDBw_elM2DddCmzxWPyeos3ULsYJ0">

This seems to be working after installing the latest pre-release as you suggested!

ShaungBhone · 8 months ago

<img width="1202" height="491" alt="Image" src="https://github.com/user-attachments/assets/35dc7b21-c569-4fe6-b0fa-dbb823881c1f" />
"chatgpt.runCodexInWindowsSubsystemForLinux": false

tismatic · 8 months ago

I should also note that the latest pre-release also allowed me to run in WSL mode as well without having to disable it.

Gabriel31173 · 8 months ago

@dylan-hurd-oai the pre-release did not fix the problem for me. Now wsl agent mode works when I start VS code but after 30min-1hr I suddenly get the same error shown in the original post. Not sure what’s happening and if some timed event still has the bug, but it happened while it was processing an agent request I made.

dylan-hurd-oai contributor · 8 months ago

@BaconGabe thanks for reporting! I'd like to dig into this, but it sounds like a new problem. Can you open a new issue with details about the specific error you're seeing? I'm going to close this issue for cleanliness.

If you're still seeing issues related to WSL, please open a new Github Issue and we'll dig into it.

jisam-isa · 8 months ago

is this for all? or is specific people

Gabriel31173 · 8 months ago

@dylan-hurd-oai I'll create the issue if I see it again for some reason it hasn't happened since yesterday and I didn't change anything

topsailhemp-gif · 8 months ago

I am having the same issue on my new Surface Pro. None of the solutions above worked.

NewbyZ · 8 months ago

I fix doing that:

in CMD:
notepad %APPDATA%\Code\User\settings.json

change:
"chatgpt.runCodexInWindowsSubsystemForLinux": true

for:
"chatgpt.runCodexInWindowsSubsystemForLinux": false

Gabriel31173 · 8 months ago
I fix doing that: in CMD: notepad %APPDATA%\Code\User\settings.json change: "chatgpt.runCodexInWindowsSubsystemForLinux": true for: "chatgpt.runCodexInWindowsSubsystemForLinux": false

@topsailhemp-gif @NewbyZ this will fix the error, but you still wont be able to use agent mode (WSL needed). still good to know just so you can get something working

jisam-isa · 8 months ago
> I fix doing that: > in CMD: notepad %APPDATA%\Code\User\settings.json > change: "chatgpt.runCodexInWindowsSubsystemForLinux": true > for: "chatgpt.runCodexInWindowsSubsystemForLinux": false @topsailhemp-gif @NewbyZ this will fix the error, but you still wont be able to use agent mode (WSL needed). still good to know just so you can get something working

Fixed my issue following this.. Many thx..

Z996Zh · 8 months ago

I encountered the same error. I installed the codex plugin in cursor and configured it in the Linux docker. My computer unexpectedly restarted. After that, when I entered the codex plugin, an error was reported
An error has occurred
Codex crashed with the following error:

Codex process errored: Codex process is not available
Some things to try:

Check your config.toml for invalid settings
Try updating your IDE settings
Try downloading a different version of the extension
Click reload to restart the Codex extension, or visit our documentation for additional help.

I don't know how to recover it.

phrxst · 7 months ago

Solution on the duplicate ticket fixed it for me. https://github.com/openai/codex/issues/6479#issuecomment-3557955842