Codex Desktop 26.616.41845: `node_repl/js` fails with missing `sandboxPolicy`, breaking Chrome and Computer Use tools

Resolved 💬 2 comments Opened Jun 20, 2026 by dovvnloading Closed Jun 21, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.616.41845

What subscription do you have?

Pro

What platform is your computer?

windows

What issue are you seeing?

Bug: Codex Desktop node_repl/js fails with missing sandboxPolicy, breaking Chrome and Computer Use

Description

Codex Desktop on Windows is unable to execute any node_repl/js call. The failure happens before user JavaScript runs and blocks the official Chrome and Computer Use tools, since both depend on the shared node_repl runtime.

Version

26.616.41845

Platform

  • OS: Windows
  • Shell: PowerShell
  • App: Codex Desktop
  • Date observed: June 20, 2026

Affected tools / skills

  • mcp__node_repl.js
  • chrome:control-chrome
  • computer-use:computer-use

Error message

Mcp error: -32602: js: codex/sandbox-state-meta: missing field sandboxPolicy

### What steps can reproduce the bug?

```markdown
### Steps to reproduce

1. Open Codex Desktop `26.616.41845` on Windows.
2. Start any thread.
3. Ask Codex to use the bundled Chrome or Computer Use tool.
4. Run any `node_repl/js` call, even a minimal one like:

```js
nodeRepl.write("test");
  1. Observe the error:
Mcp error: -32602: js: codex/sandbox-state-meta: missing field sandboxPolicy

### What is the expected behavior?

```markdown
### Expected behavior

`node_repl/js` should execute JavaScript successfully without a sandbox metadata error.

The bundled Chrome and Computer Use tools should initialize normally and allow Codex to control the connected Chrome session or Windows desktop as intended.

Additional information

The issue appears to be in the shared node_repl/js runtime, not in the Chrome extension or the target website. The Chrome extension showed as connected, but both Chrome control and Computer Use failed before their runtimes could initialize.

node_repl/js_reset did not resolve the issue. Shell, git, file editing, builds, and web search still worked normally.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #29211
  • #29193
  • #29189
  • #29199
  • #29205

Powered by Codex Action

LiamHanX · 2 months ago

I’m seeing the same failure mode on Windows while trying to use the bundled Computer Use workflow.

Environment/context:

  • Platform: Windows, Codex Desktop
  • Target workflow: Computer Use to list/control Windows apps, then inspect a logged-in desktop app for public URLs only
  • The failure occurs before any target app is listed or controlled, so it does not appear target-app-specific.

Observed sequence:

  1. Project instructions were read successfully with normal filesystem tools.
  2. node_repl/js_reset succeeded.
  3. Attempting to initialize Computer Use and call sky.list_apps() failed before listing Windows apps.
  4. After restarting Codex Desktop / retrying in a fresh session, even a minimal JS call failed before user JavaScript executed.

Errors observed:

Package subpath './dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client_base.js' is not defined by "exports" in ...\node_modules\@oai\sky\package.json

Then after restart / retry:

Mcp error: -32602: js: codex/sandbox-state-meta: missing field `sandboxPolicy`

Minimal failing call after restart:

nodeRepl.write('node-ok')

Impact:

  • Computer Use cannot initialize.
  • Windows apps cannot be listed or controlled.
  • The workflow is blocked before any desktop app, browser, login state, or app-specific policy could be involved.

This looks consistent with the issue description: a shared node_repl/js / sandbox metadata problem, plus possibly a Computer Use @oai/sky export mismatch on the pre-restart attempt.