VScode extension error - Codex app-server process exited with code 1 and signal null.

Resolved 💬 19 comments Opened Oct 31, 2025 by sergx Closed Nov 4, 2025
💡 Likely answer: A maintainer (dylan-hurd-oai, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

0.4.34

What subscription do you have?

Plus

Which model were you using?

_No response_

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What issue are you seeing?

On VSCode sturtup Codex extension, witch updated 1 hour ago, as i can see in it's props, now gives an error:

An error has occurred
Codex crashed with the following error:

Codex app-server process exited with code 1 and signal null.
Most recent error message:
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files\Graphviz\bin
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files\nodejs\
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\Сергей\.cargo\bin
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate E:\OSPanel6\bin
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate E:\anaconda3
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate E:\anaconda3\Library\mingw-w64\bin
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate E:\anaconda3\Library\usr\bin
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate E:\anaconda3\Library\bin
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate E:\anaconda3\Scripts
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\Сергей\AppData\Local\Microsoft\WindowsApps
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\Сергей\AppData\Local\Programs\Microsoft VS Code\bin
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\Сергей\AppData\Roaming\Composer\vendor\bin
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files\Tesseract-OCR
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files (x86)\Nmap
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate E:\OSPanel6\modules\PHP-8.3\PHP
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\Сергей\AppData\Roaming\npm
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files (x86)\ZBar\bin
<3>WSL (11) ERROR: CreateProcessEntryCommon:334: getpwuid(0) failed 2
<3>WSL (11) ERROR: CreateProcessEntryCommon:496: chdir(/mnt/e/crypto-qr) failed 2
<3>WSL (11) ERROR: CreateProcessEntryCommon:505: execvpe /bin/sh failed 2
<3>WSL (11) ERROR: CreateProcessEntryCommon:508: Create process not expected to return

Please check your config.toml and reload, or visit our documentation for additional help.

Open Config.toml
Reload

Or this:

Codex app-server process exited with code 1 and signal null.
Most recent error message:
<3>WSL (11) ERROR: CreateProcessEntryCommon:505: execvpe /bin/sh failed 2
<3>WSL (11) ERROR: CreateProcessEntryCommon:508: Create process not expected to return

Config.toml is basic:

model = "gpt-5-codex"
model_reasoning_effort = "low"

What steps can reproduce the bug?

Open VSCode

What is the expected behavior?

<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate E:\anaconda3
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate E:\anaconda3\Library\mingw-w64\bin
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate E:\anaconda3\Library\usr\bin
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate E:\anaconda3\Library\bin
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate E:\anaconda3\Scripts
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\Сергей\AppData\Local\Microsoft\WindowsApps
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\Сергей\AppData\Local\Programs\Microsoft VS Code\bin
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\Сергей\AppData\Roaming\Composer\vendor\bin
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files\Tesseract-OCR
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files (x86)\Nmap
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate E:\OSPanel6\modules\PHP-8.3\PHP
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\Сергей\AppData\Roaming\npm
<3>WSL (11) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files (x86)\ZBar\bin
<3>WSL (11) ERROR: CreateProcessEntryCommon:334: getpwuid(0) failed 2
<3>WSL (11) ERROR: CreateProcessEntryCommon:496: chdir(/mnt/e/crypto-qr) failed 2
<3>WSL (11) ERROR: CreateProcessEntryCommon:505: execvpe /bin/sh failed 2
<3>WSL (11) ERROR: CreateProcessEntryCommon:508: Create process not expected to return

Additional information

_No response_

View original on GitHub ↗

19 Comments

dylan-hurd-oai contributor · 8 months ago

@sergx can you try disabling Run in WSL under your VS Code settings? We tested this on an array of windows devices and it should not be attempting to run in WSL if it's uninstalled, but it's possible we missed edge cases.

sergx · 8 months ago
make sure you have WSL installed. Can run: wsl --install in admin powershell

Thank you. I opened powershell, typed wsl -l -v and i saw

  NAME                   STATE           VERSION
* docker-desktop-data    Stopped         2
  docker-desktop         Stopped         2

Then i installed Ubuntu with wsl --install -d Ubuntu and setted it as default wsl with wsl --setdefault Ubuntu
Now all fine

dylan-hurd-oai contributor · 8 months ago

Super helpful - we'll be rolling out a hotfix to make this feature opt-in rather than opt-out, and will follow-up with a proper fix to handle this edge case more gracefully.

Thanks for you patience - let us know if you have feedback on the experience in WSL!

sergx · 8 months ago
@sergx can you try disabling Run in WSL under your VS Code settings? We tested this on an array of windows devices and it should not be attempting to run in WSL if it's uninstalled, but it's possible we missed edge cases.

I noticed this: on my main PC extension just updated while i worked (and it was fine), But in a new VSCode windows just crushed as i described.
But on laptop there was a notification, that Agent can't work without WSL, and still, i just pressed somthing (like "ok, try without WSL", or somthing like it, i did not noticed) and it got crushed on laptop as well.

dylan-hurd-oai contributor · 8 months ago

What's the output of wsl -l -v on your laptop?

sergx · 8 months ago
What's the output of wsl -l -v on your laptop?

C closed the PowerShell, sorry, but 99% it was the same as on main PC:

  NAME                   STATE           VERSION
* docker-desktop-data    Stopped         2
  docker-desktop         Stopped         2

So i made same steps to fix

SPJS16 · 8 months ago

Have similar issue ensured WSL is install and wsl -l -v shows:

<img width="312" height="59" alt="Image" src="https://github.com/user-attachments/assets/81c93306-8eb8-4267-ba2d-794df78318ca" />

However when I go to install the extension from it shows:

<img width="1820" height="126" alt="Image" src="https://github.com/user-attachments/assets/b9b1c5ad-8386-4267-814d-7a3b2f79c625" />

IE: Codex chat session item provider not registered: Me.chat.registerChatSessionItemProvider is not a function

dylan-hurd-oai contributor · 8 months ago

Ah I think this might be the same on-by-default issue. Can you check your VS Code settings?

dylan-hurd-oai contributor · 8 months ago

Codex chat session item provider not registered is an unrelated log - @HJSW14 can you use Help > Toggle Developer Console to see if there are any error logs in there?

You should also be able to resolve this by turning off the setting in your VS Code settings:
<img width="1175" height="434" alt="Image" src="https://github.com/user-attachments/assets/b3bb30f7-5f83-4609-8e1b-91a462897f95" />

sergx · 8 months ago

Not related to this bug, but about this version of extension - 0.4.34.

The Codex Chat history gone. While still it presented in C:\Users\Sergey\.codex\sessions, but in a extension window i can't see it. Just No tasks yet.

UPDATE:
It's because i run in WSL. Then i turn WSL off the chat history is back

dylan-hurd-oai contributor · 8 months ago

Correct - that is currently an intentional part of the WSL migration - you can resume conversations in the same environments, to avoid degrading model performance with context from a different operating system. We can make the cost of enabling this clearer in the dialogs / task history - good feedback!

dylan-hurd-oai contributor · 8 months ago

@HJSW14 we're publishing 0.4.35 now to disable this feature by default - please let us know if you're still seeing issues on the latest version once you can upgrade

buffos · 8 months ago

Sorry if this seems off-topic. Is running the codex-plugin in VS Code incompatible with running Docker Desktop at the same time?
I am in Windows. Once I open the Docker desktop, I have an "error starting conversation."

nos1609 · 8 months ago

Same here, keep loosing my weekly codex limits, 5 new conversation crashes in row

MohamedFahmy1 · 8 months ago

@dylan-hurd-oai Thanks it's solved when i unchecked this

dylan-hurd-oai contributor · 8 months ago

@buffos @nos1609 Docker Desktop compatibility should be resolved in 0.5.36 - can you try the newest pre-release?

buffos · 8 months ago

@dylan-hurd-oai It seems to work fine with 0.5.36

etraut-openai contributor · 8 months ago

Thanks for confirming.

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.