Repository navigation
Windows Codex node_repl/js fails: missing sandboxPolicy in codex/sandbox-state-meta #29274
Description
Bug Report: Windows Codex node_repl/js fails with missing sandboxPolicy
Summary
On Windows, both Codex stable and Codex beta fail immediately when invoking node_repl/js. This breaks @Chrome, @Browser, and @Computer, because all of them depend on the Node REPL MCP tool.
Error
tool call error: tool call failed for `node_repl/js`
Caused by:
Mcp error: -32602: js: codex/sandbox-state-meta: missing field `sandboxPolicy`
Environment
- OS: Windows
- Codex app: Stable and Beta both affected
- Beta path observed:
C:\Program Files\WindowsApps\OpenAI.CodexBeta_26.616.5445.0_x64__2p2nqsd0c76g0\app\Codex (Beta).exe - Affected tool:
node_repl/js - Affected features:
@Chrome,@Browser,@Computer - Codex home:
C:\Users\HerbertExtrem\.codex
Minimal Reproduction
In a new Codex thread, ask Codex to run a minimal Node REPL test:
nodeRepl.write(JSON.stringify({ ok: true, cwd: nodeRepl.cwd }, null, 2));Expected:
{
"ok": true,
"cwd": "..."
}Actual:
tool call error: tool call failed for `node_repl/js`
Caused by:
Mcp error: -32602: js: codex/sandbox-state-meta: missing field `sandboxPolicy`
Reset Attempts Already Tried
The issue reproduces after restarting:
- Codex app
- Windows PC
- Codex login session
The issue also reproduces after regenerating the relevant local Codex runtime/plugin state. These paths were backed up and renamed so Codex could recreate them:
C:\Users\HerbertExtrem\.codex\config.toml
C:\Users\HerbertExtrem\.codex\chrome-native-hosts-v2.json
C:\Users\HerbertExtrem\.codex\plugins\cache
C:\Users\HerbertExtrem\AppData\Local\OpenAI\Codex\runtimes
The latest repair run completed and logged:
Renamed: C:\Users\HerbertExtrem\.codex\chrome-native-hosts-v2.json
Renamed: C:\Users\HerbertExtrem\.codex\plugins\cache
Renamed: C:\Users\HerbertExtrem\AppData\Local\OpenAI\Codex\runtimes
Repair complete.
After Codex recreated these folders/files, node_repl/js still failed with the same missing field sandboxPolicy error.
Configuration Detail
Freshly generated C:\Users\HerbertExtrem\.codex\config.toml contains a node_repl MCP registration similar to:
[features]
js_repl = false
[mcp_servers.node_repl]
args = []
command = 'C:\Users\HerbertExtrem\AppData\Local\OpenAI\Codex\runtimes\cua_node\a89897d3d9baa117\bin\node_repl.exe'
startup_timeout_sec = 120
[mcp_servers.node_repl.env]
NODE_REPL_NATIVE_PIPE_CONNECT_TIMEOUT_MS = "1000"
NODE_REPL_NODE_MODULE_DIRS = 'C:\Users\HerbertExtrem\AppData\Local\OpenAI\Codex\runtimes\cua_node\a89897d3d9baa117\bin\node_modules'
NODE_REPL_NODE_PATH = 'C:\Users\HerbertExtrem\AppData\Local\OpenAI\Codex\runtimes\cua_node\a89897d3d9baa117\bin\node.exe'
CODEX_HOME = 'C:\Users\HerbertExtrem\.codex'
BROWSER_USE_AVAILABLE_BACKENDS = "chrome,iab"Manually changing js_repl = false to js_repl = true did not resolve the issue; Codex regenerated or restored js_repl = false on restart.
Why this looks like an app/plugin bug
The runtime and plugin caches were fully regenerated, and the failure still happens before any browser-specific code runs. The app appears to start/register node_repl, but the MCP call metadata passed to node_repl/js is missing codex/sandbox-state-meta.sandboxPolicy.
This blocks all browser and GUI automation features that depend on the Node REPL bridge.
Requested Help
Please check whether the Windows Codex app is failing to include sandboxPolicy in codex/sandbox-state-meta for node_repl/js MCP calls, especially when Browser/Chrome/Computer Use plugins register the Node REPL MCP server.
Activity
github-actions commentedon Jun 20, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
node_repl/jsfails with missingsandboxPolicy, breaking Chrome and Computer Use tools #29212sandboxPolicy#29193Powered by Codex Action
RatziFatzi02 commentedon Jun 21, 2026
i found the same Problem on my side. im not very into the tech on this module. but updating to the newest version did break it for me
ID-jasmine commentedon Jun 21, 2026
I have the same issue. It started after the update.
danieldilly commentedon Jun 21, 2026
New release just fixed it!
Ben2248 commentedon Jun 21, 2026
FIXEDDDDDD
HerbertExtrem commentedon Jun 21, 2026
Yep thx, latest update fixed it 👍