I’m still unable to use the Codex in-app browser or browser control on Windows ARM64, despite the related forum thread being marked resolved.
Environment:
-
Windows ARM64
-
Codex desktop package:
26.924.1866.0(ARM64) -
Bundled browser/runtime version:
26.924.20706 -
The app reports that it is up to date.
Observed behavior:
-
Browser runtime initialization fails before any browser tab or website can be accessed:
Trusted RPC dependency must resolve within a configured trusted code path: .../browser/26.924.20706/scripts/browser-service.mjs -
After fully quitting Codex and creating a new task to read the title of
example.comwith the in-app browser, browser discovery still failed. The task retried and reset the connection, then reported that it had used a separate read-only web lookup instead. -
A subsequent browser inventory attempt returned:
Browsers: Error: nodeRepl.fetch request failed
The referenced browser-service.mjs exists under the configured trusted root. The failure occurs before Gmail authentication or page access, and it is reproducible with a public page (example.com). Reinstalling and starting a fresh task have not resolved it.
This resembles the earlier Windows trusted-RPC report, but I cannot confirm whether the newer nodeRepl.fetch request failed error has the same underlying cause. Could the team check whether the reported fix covers ARM64 builds, and what diagnostics would help distinguish these failures?
