Windows: Codex browser opens but agent control fails with "Trusted RPC dependency" error #39435

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

26.814.41407

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

The Codex in-app browser opens and loads websites normally, but Codex cannot control any browser tab. Browser control fails before the agent can connect to the tab, affecting both the in-app browser and Edge browser control.

Error:
Trusted RPC dependency must resolve within a configured trusted code path:
file:///C:/Users/USER/.codex/plugins/cache/openai-bundled/browser/26.814.41407/scripts/browser-service.mjs

I fully restarted Codex, opened new browser tabs, reopened Threads, allowed browser access, and tried Edge, but the same error occurs every time.

What steps can reproduce the bug?

This is a browser-control issue, so there is no application code snippet to provide.

Steps to reproduce:

1. Launch the Codex desktop app on Windows.
2. Open the built-in browser and navigate to any website (for example, https://www.threads.com/).
3. Ask Codex to inspect or interact with the current browser tab.
4. Browser control fails before Codex can connect to the tab.

Expected result:
Codex should connect to the open tab and be able to inspect or interact with it after website access is allowed.

Actual result:
The browser UI loads pages normally, but Codex returns this error:

Trusted RPC dependency must resolve within a configured trusted code path:
file:///C:/Users/USER/.codex/plugins/cache/openai-bundled/browser/26.814.41407/scripts/browser-service.mjs

I also reproduced the issue after restarting Codex, opening a new browser tab, and trying Edge browser control.

Session ID, token limit usage, and context window usage: not applicable. The failure occurs before the browser control session can be established.

What is the expected behavior?

After browser access is allowed, Codex should successfully connect to the currently open browser tab and be able to inspect, click, type, upload files, and otherwise interact with the page.

The built-in browser and Edge browser control should work without requiring a trusted-path error workaround.

Additional information

No response