Windows regression that completely disables both the built-in Browser and Chrome control.

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

ChatGPT/Codex desktop app: 26.814.41407

What subscription do you have?

Pro

What platform is your computer?

Windows 11 x64

What issue are you seeing?

I am reporting a reproducible Windows regression that completely disables both the built-in Browser and Chrome control.

Environment:

• ChatGPT/Codex desktop app: 26.814.41407
• Bundled Browser plugin: 26.814.41407
• Bundled Chrome plugin: 26.814.41407
• Chrome extension: 1.2.27259.19709

Exact error:
“Trusted RPC dependency must resolve within a configured trusted code path:
.../openai-bundled/browser/26.814.41407/scripts/browser-service.mjs”

The failure occurs before tab discovery. Codex cannot inspect or control either the built-in browser or Chrome. This functionality worked correctly for me before the 26.814 update.

I have already:

• Repaired and reinstalled the desktop application.
• Removed and re-added the Chrome plugin.
• Reinstalled the official Chrome extension.
• Restarted Chrome, Codex, and Windows.
• Tested with new local Work and Codex chats.
• Confirmed that the desktop app and bundled plugins are version-matched.
• Confirmed that the Chrome side panel loads.
• Tested both Browser and Chrome separately.

None of the documented troubleshooting steps resolves the problem. Please do not redirect this report to the generic reinstall procedure; that procedure has already been completed repeatedly and the failure persists.

This appears consistent with these public reports:

• https://github.com/openai/codex/issues/39136
• https://github.com/openai/codex/issues/39173
• https://github.com/openai/codex/issues/39236

This regression is blocking a real production workflow: editing authenticated WordPress content through an existing Chrome session. The cloud browser is not an equivalent workaround because it does not share the local authenticated Chrome profile and the site’s security verification blocks that environment.

Please escalate this to the Windows Browser/Chrome integration team, confirm whether the defect is acknowledged, and provide the version number or expected release containing the fix. A corrected build is needed; further reinstalls of the same version do not address the trusted RPC configuration failure.

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a01861-1131-75e0-a22b-685dc4af7e24

What is the expected behavior?

No response

Additional information

No response

No source file, test, or entry point is named in the report. Start by tracing the Windows Browser/Chrome integration and the trusted RPC path, then reproduce the failure with the listed app and plugin versions. Done means both the built-in Browser and Chrome control work again without the trusted code path error.