Repository navigation
Windows Codex Desktop 26.616.5445: Browser Use fails because node_repl/js metadata is missing sandboxPolicy #29241
Description
What version of the Codex App are you using?
26.616.5445.0
What subscription do you have?
Pro
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Browser Use is not working in Codex Desktop on Windows.
The in-app browser / Browser Use bridge cannot be controlled because the Node REPL JavaScript tool fails before executing any JavaScript. Any browser automation attempt fails during bootstrap with:
Mcp error: -32602: js: codex/sandbox-state-meta: missing field `sandboxPolicy`
A minimal JavaScript call also fails with the same error:
nodeRepl.write('ping')js_reset succeeds and returns:
js kernel reset
So the Node REPL tool surface appears to be partially available, but the js execution tool itself fails before user code runs.
Bundled plugin versions present locally:
- browser: 26.616.41845
- chrome: 26.616.41845
- computer-use: 26.616.41845
This appears to be a Codex Desktop / app-server / MCP metadata issue. The browser client cannot start because the expected sandboxPolicy field is missing from codex/sandbox-state-meta.
What steps can reproduce the bug?
- Open Codex Desktop on Windows.
- Use Browser Use / the in-app browser automation feature.
- Attempt to open or inspect any website through Browser Use.
- Browser Use fails during runtime bootstrap before navigation.
- Run a minimal Node REPL JavaScript call:
nodeRepl.write('ping')- The call fails immediately with:
Mcp error: -32602: js: codex/sandbox-state-meta: missing field `sandboxPolicy`
- Run
js_reset; it succeeds, butjsexecution still fails afterward with the same error.
What is the expected behavior?
Browser Use should attach to the in-app browser, allow navigation, and support normal browser automation actions such as DOM inspection, screenshots, clicking, typing, and page verification.
At minimum, node_repl/js should execute a simple JavaScript call like:
nodeRepl.write('ping')If required sandbox metadata is missing, Codex Desktop should provide the expected sandboxPolicy field or return a clear actionable error explaining how to repair the local app state.
Additional information
Shell and file tools in the same Codex thread continue to work normally. The failure is isolated to node_repl/js execution and anything depending on it, including Browser Use.
Activity
github-actions commentedon Jun 20, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
sandboxPolicy#29193Powered by Codex Action
abran28 commentedon Jun 20, 2026
Confirming this regression on Windows/Codex Desktop.
Broken build:
26.616.41845openai-bundled/browser/26.616.41845Failure:
node_repl/jsfails before JavaScript executes.Impact:
node_repl/jscontrol path fails at metadata validation.Workaround confirmed:
26.616.32156restoresnode_repl/jsand the in-app Browser.This looks like a regression in the app-server/tool-call metadata path in
26.616.41845, not a project/server/plugin-cache issue.TUSKWOOD commentedon Jun 20, 2026
Mee too:
Codex Desktop Browser Use is broken.
Exact error:
Mcp error: -32602: js: codex/sandbox-state-meta: missing field
sandboxPolicyImpact:
@browser / in-app browser control cannot run. A minimal node_repl/js call fails before JavaScript executes, so this is not caused by the target website or local project.
Related open issues:
#29193
#29219
#29241
This appears related to a Desktop/app-server/node_repl metadata mismatch after Codex Desktop 26.616.x / 26.619.x.
RajaShawaiz commentedon Jun 21, 2026
Confirmed resolved on my Windows Codex Desktop install after updating to
26.616.6631.0.Verification:
node_repl/jsnow executes a minimal call successfully:nodeRepl.write('ping')returnsping.26.616.51431.Closing this as resolved.