Browser control fails: trusted RPC dependency outside configured trusted code path

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

26.814.5167.0

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What issue are you seeing?

Browser control fails in the Codex desktop app before it can inspect or interact with any page.

Full error:

Trusted RPC dependency must resolve within a configured trusted code path:
C:\Users<REDACTED>.codex\plugins\cache\openai-bundled\browser\26.814.41407\scripts\browser-service.mjs

Environment:

• Codex desktop version: 26.814.5167.0
• Bundled/cached browser plugin version: 26.814.41407
• Platform: Microsoft Windows NT 10.0.22631.0 x64
• OpenAI Support case: 13410185

Affected functionality:

• In-app browser control
• Chrome browser control through the ChatGPT extension
• New and existing Codex tasks
• Tasks with and without a repository

Steps to reproduce:

1. Open Codex desktop on Windows.
2. Start a brand-new task.
3. Ask Codex to inspect or control the in-app browser.
4. Browser runtime initialization immediately fails with the trusted-path error above.

Expected behavior:

Codex should connect to the in-app browser and inspect or interact with the open page.

Actual behavior:

Browser runtime initialization fails before any browser action occurs.

Troubleshooting already completed:

• Fully quit and restarted Codex, including background processes.
• Updated/reinstalled the desktop application.
• Confirmed no newer Windows package update is currently offered.
• Reproduced the issue in brand-new tasks.
• Confirmed the issue is not repository-specific.
• Confirmed it affects both in-app and Chrome browser control.
• Avoided modifying browser-service.mjs or applying unsupported trust-path workarounds.

Please confirm whether desktop version 26.814.5167.0 is incorrectly selecting browser plugin 26.814.41407. Please provide either a corrected compatible browser plugin or an officially supported signed rollback procedure.

No repository, browser profile, OAuth, or application configuration changes are required to reproduce the defect.

What steps can reproduce the bug?

Feedback ID: 019fc814-1c38-7b53-b1e5-e5cbe8d4a5e7

What is the expected behavior?

Codex should initialize the trusted bundled browser runtime and connect to the selected in-app browser or Chrome session.

It should then be able to inspect the open page, navigate, click, type, and take screenshots within the normal browser-control permission boundaries.

The desktop application and bundled browser plugin should select mutually compatible versions and trusted runtime paths.

Additional information

Feedback ID: 019fc814-1c38-7b53-b1e5-e5cbe8d4a5e7

1. Install or update Codex desktop on Windows to version 26.814.5167.0.
2. Fully quit and reopen Codex.
3. Start a brand-new task without opening a repository.
4. Open an in-app browser tab.
5. Ask Codex: “Test browser control now.”
6. Codex attempts to initialize the bundled browser-control runtime.
7. Initialization immediately fails with:

Trusted RPC dependency must resolve within a configured trusted code path:
C:\Users<REDACTED>.codex\plugins\cache\openai-bundled\browser\26.814.41407\scripts\browser-service.mjs

The same failure occurs when attempting to control Chrome through the ChatGPT browser extension.

The problem reproduces in both new and existing tasks and is not dependent on a repository, token usage, or context-window usage.

Environment:

Codex desktop version: 26.814.5167.0
Cached browser plugin version: 26.814.41407
Platform: Microsoft Windows NT 10.0.22631.0 x64
OpenAI Support case: 13410185

Troubleshooting performed:

• Fully quit and restarted Codex, including background processes.
• Updated/reinstalled the desktop app.
• Confirmed no newer Windows package update is offered.
• Reproduced the issue in brand-new tasks.
• Confirmed the failure affects both in-app browser and Chrome control.
• Confirmed the failure occurs before any page interaction.
• Did not modify browser-service.mjs.
• Reverted an ineffective local configuration experiment.
• Did not alter the Chrome profile or repository files.

Please verify whether desktop build 26.814.5167.0 is incorrectly selecting browser plugin build 26.814.41407.

A corrected compatible browser plugin or an officially supported signed rollback procedure is requested.

Begin by reproducing the failure on Windows Codex desktop 26.814.5167.0 with cached browser plugin 26.814.41407, then inspect the reported browser-service.mjs path and the desktop/plugin version-selection boundary. Done means the bundled browser runtime initializes without the trusted-path error and both in-app and Chrome browser control can perform the reported actions.