codex - 💡(How to fix) Fix Windows Codex Desktop: node_repl fails with “windows sandbox failed: spawn setup refresh”, breaking Chrome plugin and in-app Browser

What version of the Codex App are you using (From “About Codex” dialog)?

26.521.10419

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 11

What issue are you seeing?

Codex Desktop on Windows cannot start node_repl, which breaks both browser automation paths:

1. The Google Chrome plugin cannot connect to Chrome.
2. The Codex in-app Browser cannot start.
3. Even a minimal node_repl call fails before executing any JavaScript.

Observed error:

node_repl kernel exited unexpectedly node_repl diagnostics: {"kernel_status":"running","kernel_stderr_tail":"windows sandbox failed: spawn setup refresh","reason":"stdout_eof","stream_error":null}

I tested this after restarting Codex Desktop and after reinstalling/updating the Chrome plugin/extension.

Important: Chrome extension and native host appear healthy.

Local checks show:

• Chrome is installed and running.
• Codex Chrome Extension is installed and enabled.
• Extension ID: hehggadaopoacecdllhhajmbjkdcmajg
• Extension version detected: 1.1.5_0
• Selected Chrome profile: Profile 1
• Native messaging host registry key exists: HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension
• Native host manifest path: C:\Users\Usuario\AppData\Local\OpenAI\extension\com.openai.codexextension.json
• Native host check reports correct: true.

Because a minimal node_repl call also fails, this does not appear to be a Chrome extension problem, a website problem, or a native messaging host registration problem. It appears to be a Codex Desktop Windows sandbox / node_repl startup failure.

What steps can reproduce the bug?

1. Open Codex Desktop on Windows.

2. Ensure Chrome is running and the Codex Chrome Extension is installed/enabled.

3. Try to use the Chrome plugin from Codex.

4. The plugin fails before it can list or control Chrome tabs.

5. Try to use the Codex in-app Browser.

6. The in-app Browser also fails before it can open a page.

7. Try a minimal node_repl call:

   nodeRepl.write("ok")

8. The node_repl kernel exits immediately with:

   node_repl kernel exited unexpectedly node_repl diagnostics: {"kernel_status":"running","kernel_stderr_tail":"windows sandbox failed: spawn setup refresh","reason":"stdout_eof","stream_error":null}

Troubleshooting already attempted:

• Restarted Codex Desktop.
• Reinstalled the Chrome plugin from Codex.
• Updated/reinstalled the Codex Chrome Extension.
• Confirmed Chrome is running.
• Opened Chrome with the selected profile.
• Retried both Chrome plugin and in-app Browser.
• Same error persists.

What is the expected behavior?

node_repl should start successfully.

The Codex Chrome plugin should be able to connect to the installed Codex Chrome Extension and list/control Chrome tabs.

The Codex in-app Browser should also start successfully and allow Codex to open and inspect pages.

If the Windows sandbox cannot start, Codex should show a clear actionable error or supported workaround instead of failing with “windows sandbox failed: spawn setup refresh”.

Additional information

This looks similar to several existing public reports:

• https://github.com/openai/codex/issues/24963
• https://github.com/openai/codex/issues/25012
• https://github.com/openai/codex/issues/24098
• https://github.com/openai/codex/issues/24926

Those reports also mention:

• node_repl failing before executing minimal JavaScript.
• Browser and Chrome plugin becoming unusable.
• “windows sandbox failed: spawn setup refresh”.
• Possible relationship to the Windows elevated sandbox path.
• Some users reporting that changing Windows sandbox mode from “elevated” to “unelevated” may work around the problem.

Could the Codex Desktop / Windows sandbox team please confirm:

1. Whether this is a known Codex Desktop Windows regression.
2. Whether changing [windows] sandbox = "unelevated" is currently a supported workaround.
3. Whether there is a diagnostic bundle or log file I should attach.
4. Whether a Codex Desktop update is expected to fix this.