Windows Codex app: Chrome, Browser, and Computer Use plugins fail because node_repl request is missing sandboxPolicy

Codex version / environment

• Codex Windows app build: 26.616.41845 (app package resources show OpenAI.Codex_26.616.5445.0_x64)
• Plugin versions: Chrome, Browser, and Computer Use 26.616.41845
• Windows native agent using PowerShell
• Permission mode: managed / guardian approvals
• Thread ID: 019ee8d5-8c49-7273-b8cd-5059cef2b725
• Observed on June 20–21, 2026 (America/Los_Angeles)

Problem

Codex cannot control Chrome, the in-app browser, Edge through Computer Use, or any Windows app through Computer Use. All three plugins are installed and enabled, but the shared node_repl execution bridge rejects every request before plugin bootstrap runs.

Even the following minimal request fails:

nodeRepl.write('runtime-ok')

Error:

tool call failed for `node_repl/js`
Mcp error: -32602: js: codex/sandbox-state-meta: missing field `sandboxPolicy`

Because this happens with a minimal JavaScript call, it is not caused by Chrome state, website permissions, login state, selectors, or the extension UI.

Earlier related failure

The same machine and plugin execution path previously failed on June 15, 2026 with:

node_repl kernel exited unexpectedly
windows sandbox failed: runner error: CreateProcessAsUserW failed: 5

The newer failure now occurs earlier during request metadata validation.

Configuration checks

• chrome@openai-bundled: enabled
• browser@openai-bundled: enabled
• computer-use@openai-bundled: enabled
• BROWSER_USE_AVAILABLE_BACKENDS = "chrome,iab"
• Plugin scripts exist, including scripts/browser-client.mjs and scripts/computer-use-client.mjs
• Plugin/runtime versions are aligned at 26.616.41845
• Chrome and Edge processes are running
• Multiple node_repl and extension-host processes can start

Additional Chrome observation

chrome-native-hosts-v2.json contains current and older runtime registrations, including build 26.616.41845, but no com.openai.codexextension Native Messaging Host entry appears under the standard Chrome or Edge registry paths. This may be a second issue, but plugin execution currently fails before Chrome connection troubleshooting can run.

Troubleshooting already attempted

• Restarted Codex and browsers
• Removed/re-added or re-enabled the Chrome plugin/extension
• Started new Codex threads
• Confirmed plugin installation and version paths
• Retried both full Chrome bootstrap and a minimal node_repl call

Expected behavior

node_repl/js should receive valid sandbox metadata and execute the minimal call. Browser and Computer Use plugin bootstrap should then be able to connect to their respective backends.

Suspected layer

The Codex app/tool-call bridge appears not to attach the required sandboxPolicy field to codex/sandbox-state-meta, possibly due to a mismatch between the Windows app, agent/app server, or node_repl runtime metadata schema.