Its theme's rank, 14 days: 45 on the Codex sheet
2 people reported

All time, since Sep 29.

Computer Use startup failure

“Shell execution through the separately approved escalation path continues to work; Computer Use does not initialize.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/14877/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Computer Use and browser runtime fail to initialize on Windows. node_repl kernel exits with code 1 before any window inspection or input, even after js_reset and app restart, while approved shell execution still works.

Is this your bug?

File my report
Where
Computer Use runtime
Error text
kernel_stderr_tail: windows sandbox failed: permission path cannot be represented losslessly
Versions
26.924.22138
Platforms
Windows
How bad
Stops work: a core feature can't be used.

Part of: Browser/Computer Use runtime won't start8 bugs

  1. MXC launcher browser init failure38 people
  2. Browser control fails at startup with sandbox-exec TIOCSTI error19 people
  3. MXC sandbox startup failure11 people
  4. Browser control fails with trusted Node process exiting on Windows5 people
  5. Computer use initialization fails3 people
  6. MXC launcher startup failure3 people
  7. Node REPL calls time out2 people

Not quite your bug?

  1. Browser and Computer Use fail3 people

Original reports2, newest first

  1. Windows app 26.1021.31345: Chrome and Computer Use startup fails with permission path cannot be represented losslesslyOn GitHub#56924
  2. Windows Computer Use node_repl exits before @oai/sky initialization: permission path cannot be represented losslesslyOn GitHub#49370

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.