Browser client realpath EPERM

“No page read, screenshot, click, or navigation occurred in this test.”

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/12871/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

Quiet. No reports in the last two weeks, down from 3 a week at the mid-October peak.

Browser client import fails with realpath EPERM on Windows. Importing the bundled browser-client.mjs fails before Browser setup or the Chrome/Edge extension handshake, under MXC/AppContainer sandbox.

Is this your bug?

File my report

Where: Browser plugin
Error text: EPERM: operation not permitted, realpath
Versions: 26.1007.21434
Platforms: Windows
How bad: Some reports say it blocks them completely.

Part of: Workspace file access denied in sandbox4 bugs

Sandbox denies path resolution9 people
Nested folder writes denied2 people
Existing files denied write access2 people

Not quite your bug?

MXC launcher browser init failure38 people
Browser and Computer Use fail3 people

Original reports4, newest first

Oct 14, 2026[Windows] Browser bootstrap fails with native realpath EPERM under MXC/AppContainerOn GitHub#53967
Oct 12, 2026Windows Codex Desktop: built-in Browser fails with EPERM during realpath under MXCOn GitHub#53332
Oct 11, 2026Windows: Browser tool fails to load in MXC (realpath EPERM), neither Chrome nor Edge worksOn GitHub#53045
Oct 7, 2026Windows: native Chrome/Browser client fails with EPERM realpath before extension handshake (26.1002.51308)On GitHub#51669