›_ Codex Issues
Codex Issues / #39414

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

Open 💬 3 comments Opened Aug 19, 2026 by protpersonal
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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:

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_

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 9 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #39173
  • #39236
  • #39399
  • #39252
  • #39136

Powered by Codex Action

YLVLAW · 9 days ago

Additional verified root-cause evidence:

  • Installed Windows package: OpenAI.Codex_26.814.5167.0_x64; Browser plugin: 26.814.41407.
  • The failure is deterministic and occurs before tab discovery:

Trusted RPC dependency must resolve within a configured trusted code path: .../browser/26.814.41407/scripts/browser-service.mjs

  • The desktop app supplies the broad Codex home directory as a trusted path, but the worker sandbox only permits access to the exact Browser scripts directory and runtime node_modules.
  • The broad path cannot be resolved inside the sandbox and is silently discarded. Consequently, the bundled browser-service.mjs is rejected.
  • The cached and application-packaged service files are byte-identical, ruling out file corruption.
  • In an isolated verifier, trusting the exact Browser scripts directory allowed the same bundled service to initialize and successfully navigate to https://openai.com/.
  • Repairing or reinstalling the same signed build reproduces the failure. This is a Windows packaging/startup trust-path mismatch, not a Chrome profile, extension, website, network, or user-configuration problem.

Suggested fix: pass the exact resolved Browser plugin scripts directory as a trusted root before starting the worker, and ensure every trusted root is accessible inside the worker sandbox. A corrected signed Windows build is required.

rajakhoury · 8 days ago

Same issue here on Windows after updating to 26.814.41407. Chrome control was working before the update.

Error:

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

I just paid 200$ for something i can't use. Excellent customer experience!!!