5 people reported
All time, since Oct 8, including 2 thumbs-up on GitHub.
Browser control fails with trusted Node process exiting on Windows
“The failure happens before any browser inventory, tab handle, or page contents are returned.”
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/9593/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
Fails before any page state is returned; a minimal node_repl test fails the same way, and restarts did not help.
Is this your bug?
File my report- Where
- Browser control
- Error text
trusted Node process exited unexpectedly; kernel reset, rerun your request- Versions
- 26.1007.71326
- Platforms
- Windows
- How bad
- Some reports say it blocks them completely.
Part of: Browser/Computer Use runtime won't start8 bugs
- MXC launcher browser init failure38 people
- Browser control fails at startup with sandbox-exec TIOCSTI error19 people
- MXC sandbox startup failure11 people
- Computer use initialization fails3 people
- MXC launcher startup failure3 people
- Computer Use startup failure2 people
- Node REPL calls time out2 people
Not quite your bug?
- Sandbox setup refresh fails308 people
Original reports3, newest first
- Windows desktop 26.1007.71326: trusted Node worker exits despite successful direct runtime testsOn GitHub#54288
- Windows Codex: browser control and node_repl fail with “trusted Node process exited unexpectedlyOn GitHub#53999
- Windows: browser control trusted Node child exits before connecting to EdgeOn GitHub#52377