Windows Codex Desktop: node_repl crashes with "windows sandbox failed: spawn setup refresh", breaking Chrome plugin/browser runtime

Resolved 💬 2 comments Opened Jun 6, 2026 by R9182 Closed Jun 7, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Environment

  • OS: Windows
  • Codex Desktop: OpenAI.Codex_26.602.4764.0_x64
  • Chrome plugin bundle: 26.602.40724
  • Runtime bundle observed: 26.521.10419
  • Chrome extension ID: hehggadaopoacecdllhhajmbjkdcmajg
  • node_repl.exe path pattern: %LOCALAPPDATA%\OpenAI\Codex\bin\34ab3e1324cc55b5\node_repl.exe

Problem

The Chrome extension and native messaging manifest appear to be installed correctly, but the browser runtime cannot start because node_repl crashes even on minimal execution.

Error:

windows sandbox failed: spawn setup refresh

What works

  • Chrome is installed and running.
  • Chrome extension is installed and enabled in the Default profile.
  • Native messaging manifest is correct.
  • Headless/new Chrome process automation can open a page and read DOM in another session.

What fails

  • @chrome / Chrome plugin cannot list or claim existing logged-in Chrome tabs.
  • node_repl minimal execution fails before browser runtime starts.

Minimal test attempted inside Codex:

nodeRepl.write('node_repl_ok')

Observed result:

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

Troubleshooting already tried

  • Rebooted Windows.
  • Rebooted Codex.
  • Removed third-party antivirus: Trend Micro / ウイルスバスター.
  • Confirmed Windows Defender Controlled Folder Access is off.
  • Confirmed no Defender blocking events around the failure.
  • Deleted %LOCALAPPDATA%\OpenAI\Codex\bin\.
  • Restarted Codex and confirmed bin was regenerated.
  • Failure still reproduces after regeneration.

Expected

node_repl should start successfully, allowing the Chrome plugin/browser runtime to connect to the existing Chrome session.

Actual

node_repl exits unexpectedly with:

windows sandbox failed: spawn setup refresh

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

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

  • #25357
  • #26645
  • #26617
  • #26163
  • #25511

Powered by Codex Action

R9182 · 2 months ago

Closing this as a duplicate of #25357.

The workaround from #25357 fixed the local reproduction here:

[windows]
sandbox = "unelevated"

After updating %USERPROFILE%\.codex\config.toml, node_repl minimal execution started working again, and Chrome browser automation was able to connect and read the logged-in Green Beans tab.

Thanks.