Bug report: Codex Desktop on Windows cannot start node_repl sandbox, breaking Chrome plugin

Summary

Codex Desktop on Windows can no longer use the Chrome plugin or any node_repl-backed browser automation. The failure occurs before Chrome is used: even a minimal node_repl call 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}

This previously worked on the same machine.

Environment

• OS: Windows Desktop v10.0.26200.8457
• Codex Desktop package: OpenAI.Codex_26.519.11010.0_x64__2p2nqsd0c76g0
• Codex app version shown by winget/MS Store: 26.519.11010.0
• Winget version: v1.28.240
• Chrome plugin cache version regenerated after cleanup: 26.519.81530
• Chrome native host extension ID: hehggadaopoacecdllhhajmbjkdcmajg

What fails

Any call to the node_repl MCP tool fails, including the minimal test:

nodeRepl.write("ok")

Observed result:

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

Because node_repl fails, the Chrome plugin cannot connect to or automate Chrome.

Things already verified

Chrome/plugin side appears healthy after reset:

• Chrome plugin cache regenerated under: C:\Users\Jorge\.codex\plugins\cache\openai-bundled\chrome
• Native host manifest exists: C:\Users\Jorge\AppData\Local\OpenAI\extension\com.openai.codexextension.json
• Native messaging registry key exists: HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension
• Registry value points to: C:\Users\Jorge\AppData\Local\OpenAI\extension\com.openai.codexextension.json

So the remaining issue is not the Chrome extension or native host registration; it is node_repl failing to start its Windows sandbox kernel.

Repair attempts performed

1. Reinstalled the Chrome plugin from Codex UI.
2. Removed/regenerated Chrome plugin cache: C:\Users\Jorge\.codex\plugins\cache\openai-bundled\chrome
3. Removed/regenerated native host manifest: C:\Users\Jorge\AppData\Local\OpenAI\extension
4. Removed/regenerated native messaging registry key: HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension
5. Ran winget upgrade for Codex: result: no newer version available.
6. Ran winget repair for Codex from Microsoft Store.
7. Re-registered the Codex AppX package with:

Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\OpenAI.Codex_26.519.11010.0_x64__2p2nqsd0c76g0\AppxManifest.xml"

The AppX re-registration completed successfully, but node_repl still fails with the same sandbox error.

Relevant logs/results

Successful AppX repair log:

[2026-05-28 15:52:02] Running Add-AppxPackage repair.
[2026-05-28 15:52:02] Repair completed successfully.
[2026-05-28 15:52:02] Relaunching Codex.
[2026-05-28 15:52:02] Codex relaunch requested.

Repeated failing test after repair:

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

Expected behavior

node_repl should start its kernel successfully, and the Chrome plugin should be able to list/control Chrome tabs as it did previously.

Actual behavior

node_repl fails before executing any JavaScript, with windows sandbox failed: spawn setup refresh.

Impact

This blocks all Chrome plugin workflows from Codex Desktop, including authenticated browser automation through the user's existing Chrome session.

Request

Please investigate the Windows sandbox startup path for node_repl in Codex Desktop 26.519.11010.0, especially the spawn setup refresh step. If there is a supported repair command, cache reset, feature flag, or diagnostic bundle needed, please provide the exact steps.