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

All time, since Oct 10, including 1 thumbs-up on GitHub.

Computer use initialization fails

“Browser control and the native computer-use fallback fail before browser discovery or application access on Windows.”

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/11299/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 fails to initialize with kernel assets path error. On Windows, import('@oai/sky') or cua.getState() fails before app or browser discovery; the failing path is not shown.

Is this your bug?

File my report
Where
Computer Use
Error text
failed to write kernel assets: The system cannot find the path specified. (os error 3)
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. MXC launcher startup failure3 people
  6. Computer Use startup failure2 people
  7. Node REPL calls time out2 people

Not quite your bug?

  1. Sandbox setup refresh fails308 people

Original reports2, newest first

  1. Windows desktop: browser and computer-use initialization fail with kernel-assets path error (26.1007.9446.0)On GitHub#56747
  2. Windows Computer Use cannot initialize: failed to write kernel assets (os error 3)On GitHub#52969

Do you work on Codex?

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