codex - 💡(How to fix) Fix codex not able to acces chrome

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

newest

What subscription do you have?

chatgpt

What platform is your computer?

windows 11

What issue are you seeing?

Windows Desktop: node_repl/browser bridge crashes with "windows sandbox failed: spawn setup refresh"

Codex Desktop Bug Report: node_repl/browser bridge crashes on Windows Summary Codex Desktop on Windows cannot start the local JavaScript runtime used by browser automation. The failure happens before connecting to Chrome and also affects the in-app browser. A minimal node_repl test crashes, so this is not limited to the Chrome extension.

Environment OS: Windows Codex Desktop install path observed via default node resolution: C:\Program Files\WindowsApps\OpenAI.Codex_26.519.11010.0_x64__2p2nqsd0c76g0\app\resources\node.exe Workspace: C:\Users\caleb\OneDrive - Alternate Heating Systems\Documents\GOOGLE TAG MANAGER Bundled runtime Node: C:\Users\caleb.cache\codex-runtimes\codex-primary-runtime\dependencies\node\bin\node.exe Version: v24.14.0 Chrome plugin cache: C:\Users\caleb.codex\plugins\cache\openai-bundled\chrome\26.519.81530 Browser plugin cache: C:\Users\caleb.codex\plugins\cache\openai-bundled\browser\26.519.81530 Repro Steps In Codex Desktop, call node_repl with a minimal script:

nodeRepl.write('ok') The kernel exits unexpectedly before returning ok.

Actual Result node_repl crashes 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} Expected Result The JavaScript runtime should start and return:

ok Browser Impact Because node_repl cannot start, both browser automation surfaces fail:

Chrome plugin / Codex Chrome Extension Codex in-app browser plugin Chrome Checks Already Performed The Chrome side appears healthy:

Chrome is installed and running. Codex Chrome Extension is installed and enabled in Chrome profile Default. Native host manifest exists and is correct: Manifest: C:\Users\caleb\AppData\Local\OpenAI\extension\com.openai.codexextension.json Registry key: HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension Expected extension ID: hehggadaopoacecdllhhajmbjkdcmajg A fresh Chrome window was opened for profile Default. Chrome plugin was removed and reinstalled. Windows was restarted. After all of the above, the minimal node_repl.write('ok') test still fails with the same windows sandbox failed: spawn setup refresh error.

Notes This looks like a Codex Desktop local runtime/sandbox startup issue rather than a Chrome extension or native messaging setup issue.

What steps can reproduce the bug?

Codex Desktop Bug Report: node_repl/browser bridge crashes on Windows Summary Codex Desktop on Windows cannot start the local JavaScript runtime used by browser automation. The failure happens before connecting to Chrome and also affects the in-app browser. A minimal node_repl test crashes, so this is not limited to the Chrome extension.

Environment OS: Windows Codex Desktop install path observed via default node resolution: C:\Program Files\WindowsApps\OpenAI.Codex_26.519.11010.0_x64__2p2nqsd0c76g0\app\resources\node.exe Workspace: C:\Users\caleb\OneDrive - Alternate Heating Systems\Documents\GOOGLE TAG MANAGER Bundled runtime Node: C:\Users\caleb.cache\codex-runtimes\codex-primary-runtime\dependencies\node\bin\node.exe Version: v24.14.0 Chrome plugin cache: C:\Users\caleb.codex\plugins\cache\openai-bundled\chrome\26.519.81530 Browser plugin cache: C:\Users\caleb.codex\plugins\cache\openai-bundled\browser\26.519.81530 Repro Steps In Codex Desktop, call node_repl with a minimal script:

nodeRepl.write('ok') The kernel exits unexpectedly before returning ok.

Actual Result node_repl crashes 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} Expected Result The JavaScript runtime should start and return:

ok Browser Impact Because node_repl cannot start, both browser automation surfaces fail:

Chrome plugin / Codex Chrome Extension Codex in-app browser plugin Chrome Checks Already Performed The Chrome side appears healthy:

Chrome is installed and running. Codex Chrome Extension is installed and enabled in Chrome profile Default. Native host manifest exists and is correct: Manifest: C:\Users\caleb\AppData\Local\OpenAI\extension\com.openai.codexextension.json Registry key: HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension Expected extension ID: hehggadaopoacecdllhhajmbjkdcmajg A fresh Chrome window was opened for profile Default. Chrome plugin was removed and reinstalled. Windows was restarted. After all of the above, the minimal node_repl.write('ok') test still fails with the same windows sandbox failed: spawn setup refresh error.

Notes This looks like a Codex Desktop local runtime/sandbox startup issue rather than a Chrome extension or native messaging setup issue.

What is the expected behavior?

No response

Additional information

Codex Desktop Bug Report: node_repl/browser bridge crashes on Windows Summary Codex Desktop on Windows cannot start the local JavaScript runtime used by browser automation. The failure happens before connecting to Chrome and also affects the in-app browser. A minimal node_repl test crashes, so this is not limited to the Chrome extension.

Environment OS: Windows Codex Desktop install path observed via default node resolution: C:\Program Files\WindowsApps\OpenAI.Codex_26.519.11010.0_x64__2p2nqsd0c76g0\app\resources\node.exe Workspace: C:\Users\caleb\OneDrive - Alternate Heating Systems\Documents\GOOGLE TAG MANAGER Bundled runtime Node: C:\Users\caleb.cache\codex-runtimes\codex-primary-runtime\dependencies\node\bin\node.exe Version: v24.14.0 Chrome plugin cache: C:\Users\caleb.codex\plugins\cache\openai-bundled\chrome\26.519.81530 Browser plugin cache: C:\Users\caleb.codex\plugins\cache\openai-bundled\browser\26.519.81530 Repro Steps In Codex Desktop, call node_repl with a minimal script:

nodeRepl.write('ok') The kernel exits unexpectedly before returning ok.

Actual Result node_repl crashes 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} Expected Result The JavaScript runtime should start and return:

ok Browser Impact Because node_repl cannot start, both browser automation surfaces fail:

Chrome plugin / Codex Chrome Extension Codex in-app browser plugin Chrome Checks Already Performed The Chrome side appears healthy:

Chrome is installed and running. Codex Chrome Extension is installed and enabled in Chrome profile Default. Native host manifest exists and is correct: Manifest: C:\Users\caleb\AppData\Local\OpenAI\extension\com.openai.codexextension.json Registry key: HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension Expected extension ID: hehggadaopoacecdllhhajmbjkdcmajg A fresh Chrome window was opened for profile Default. Chrome plugin was removed and reinstalled. Windows was restarted. After all of the above, the minimal node_repl.write('ok') test still fails with the same windows sandbox failed: spawn setup refresh error.

Notes This looks like a Codex Desktop local runtime/sandbox startup issue rather than a Chrome extension or native messaging setup issue.