Codex process errored: Codex process is not available

Resolved 💬 6 comments Opened Nov 14, 2025 by ghost Closed Jan 9, 2026
💡 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.40

What subscription do you have?

Chatgpt Plus

Which IDE are you using?

VS Code

What platform is your computer?

_No response_

What issue are you seeing?

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
Check your settings to disable running in WSL if you are seeing compatibility issues
Try downloading a different version of the extension
Click reload to restart the Codex extension, or visit our documentation for additional help.

Open Config.toml
Reload

What steps can reproduce the bug?

iam uninstall and then re install extension,swithing prevoius versions,installed WSL and then disable eventhough same error not resolved

What is the expected behavior?

<img width="1919" height="1106" alt="Image" src="https://github.com/user-attachments/assets/3e7a32b9-1738-4169-a470-45e1f97f9d61" />

Additional information

_No response_

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 9 months ago

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

  • #6479
  • #6435
  • #6062

Powered by Codex Action

CodySig · 7 months ago

@etraut-openai this seems to keep getting flagged as a dupe but seems to be an unresolved issue with the vscode extension. I am running into the same issue. Have tried deleting .codex and reinstalling the vscode extension. If I click "open Config.toml" it opens a blank .toml file. Before I click the button, no Config.toml exists at %USERPROFILE%/.codex

etraut-openai contributor · 7 months ago

@CodySig, can you provide more details? Are you running on Windows? If so, with or without WSL?

Please check out our Windows troubleshooting tips to see if they address your problem.

CodySig · 7 months ago

Apologies for the lack of context. I am running VScode 1.107.1 on Windows 11. I am not using WSL.

Codex extension:
<img width="263" height="162" alt="Image" src="https://github.com/user-attachments/assets/12e36682-8be5-4214-a171-3fa8bf67b8f1" />

I am running locally in chat mode using gpt-5.2-codex with medium thinking. I ask it to help me scope a task, answer some follow up questions with a request for it to help me do some research which then requires network access. I allow it network access for the session then it crashes. I can consistently reproduce the issue each time I delete .codex and re-install the extension, so it doesn't seem to be session specific.

<img width="422" height="567" alt="Image" src="https://github.com/user-attachments/assets/f8a62f42-483a-472d-bcd2-00ec8b292567" />

etraut-openai contributor · 7 months ago

@CodySig, thanks for the additional details. Very helpful. Do you have the experimental Windows sandbox enabled?

When the crash occurs, open the "Output" panel in VS Code (or Cursor) and choose Codex. See if there's any additional log output that might help us determine the cause. Then restart the extension by choosing "Restart Extension Host" from the command palette. Once the extension is running again, issue a simple prompt like "Hi", and then use the "/feedback" command to upload your logs, and post the thread ID here. That will allow me to look at the debug information logged by Codex.

CodySig · 7 months ago

Huh, I re-installed again today once I got back to working on this (after about 11 hours), and it seems to be working completely fine now. I lost my session information because I had permanently deleted the .codex file, but it's working again. I tried this probably 10 times over a few hours before coming to this issue and was able to re-produce it every time. I guess I will just be on the lookout for it happening again. I appreciate the quick response and debugging steps. I will keep that in mind in the future.