[macOS arm64] Browser and Chrome plugins still fail trusted RPC check on 26.820.60940

What version of the Codex App are you using (From “About Codex” dialog)?

26.820.60940 (build 7119)

What subscription do you have?

ChatGPT Enterprise / organizational account

What platform is your computer?

Darwin 25.5.0 arm64 arm (macOS 26.5.2, build 25F84)

What issue are you seeing?

Summary

The trusted-code-path browser initialization failure reported in #39136 still occurs on the current macOS arm64 build. Both the built-in Browser plugin and external Chrome control fail before a controllable browser session is created.

Actual result

Both initialization paths return:

Trusted RPC dependency must resolve within a configured trusted code path:
file:///Users/<redacted>/.codex/plugins/cache/openai-bundled/browser/26.820.60940/scripts/browser-service.mjs

Installed components

• ChatGPT/Codex Desktop: 26.820.60940 (build 7119)
• Browser plugin: 26.820.60940
• Chrome plugin: 26.820.60940
• Computer Use plugin: 1.0.1000816
• Google Chrome: 151.0.7922.175
• ChatGPT Chrome extension: 1.2.27268.51612

The Desktop, Browser, and Chrome plugin versions are aligned. The application code signature validates successfully, plugin ownership/permissions look normal, and only the current Browser/Chrome plugin versions are cached. Restarting the app, reconnecting/reinstalling the Chrome extension, and reproducing from a fresh task did not resolve it.

Impact

Neither built-in Browser automation nor Chrome control can be used. The failure happens during runtime initialization, before browser discovery or extension communication.

What steps can reproduce the bug?

1. Install/update the macOS arm64 ChatGPT/Codex Desktop app to 26.820.60940.
2. Confirm bundled Browser and Chrome plugins are both 26.820.60940.
3. Start a fresh task.
4. Ask Codex to initialize either the built-in Browser or external Chrome control.
5. Initialization immediately fails with the trusted RPC dependency error above, before documentation, tab listing, or navigation can occur.

Reproduced consistently in a fresh task: 01a03b26-7406-7283-96f7-d7a85217223b.

What is the expected behavior?

The Browser runtime should initialize successfully. The built-in Browser should be controllable, and Chrome control should connect to the installed ChatGPT Chrome extension and inspect existing tabs.

Additional information

This appears to be a macOS arm64 continuation or regression of #39136. The exact trusted-RPC-path failure remains open for Windows in #39486, but that report uses older 26.814 components and is labeled Windows-only. The macOS report #39591 is related but describes a different failure (trusted Node process exited unexpectedly). This report captures the exact trusted-RPC-path rejection on newer, version-aligned macOS components 26.820.60940.

Start by reproducing Browser and Chrome initialization on macOS arm64 with version 26.820.60940, then trace trusted RPC dependency resolution for the reported browser-service.mjs path. Done means both the built-in Browser runtime and Chrome control initialize successfully without the trusted-code-path error.