[Windows 26.814] In-app Browser control fails because browser-service.mjs is rejected as outside the trusted code path
What version of the Codex App are you using (From “About Codex” dialog)?
26.814.41407
What subscription do you have?
Pro
What platform is your computer?
Windows 11 x64
What issue are you seeing?
This is an independent reproduction of #39414.
The built-in browser opens normally and I can use the signed-in website myself, but Codex cannot inspect or control the tab. Browser control fails before tab discovery with 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
This functionality worked on 18 August 2026 and failed on 19 August 2026. The failure blocks work in existing authenticated browser sessions.
Open Codex Desktop 26.814 on Windows 11 x64.
Open a website in the built-in browser and sign in.
Ask Codex to inspect or control the current in-app browser tab.
Codex attempts to initialise Browser control.
Initialisation fails before tab discovery with the trusted RPC dependency error shown above.
Restart Codex, reopen the same task and retry.
The same failure occurs.
What steps can reproduce the bug?
Feedback ID: 01a018b7-84b1-7c03-87c3-a032aafab47d
What is the expected behavior?
Codex should connect to the existing signed-in in-app browser tab and be able to inspect the page, click controls and initiate authorised downloads.
The browser tab itself should remain usable, and restarting Codex should correctly reload the Browser control service.
Additional information
The website remains visible and usable manually. The failure is specifically in the connection between Codex and Browser control.
Codex has been restarted multiple times.
The problem also persists in a fresh task.
The bundled Browser plugin and the Browser service file are present and version-matched at 26.814.41407.
Codex generates a trusted-service mapping that points to browser-service.mjs, but its own browser helper then rejects that same file as outside the trusted code path.
A targeted trusted-path correction was overwritten when Codex restarted.
No reinstall or restart has resolved the problem.
This is the same failure described in #39414 and appears related to #39136, #39173 and #39236.
This is blocking a real authenticated production reporting workflow. A separate cloud browser is not an equivalent workaround because it does not share the existing authenticated session.
7 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Independent reproduction on Windows x64.
Environment:
26.814.5167.026.814.414079PLM9XGG6VKSThe in-app browser opens and the webpage remains usable manually, but Codex cannot inspect or control the tab. Initialization fails with:
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.mjsTroubleshooting attempted:
browser-client.mjsandbrowser-service.mjsexistThe failure persists after reinstall. No logs are attached.
Update: browser control is working again after the latest desktop update, but the first launch showed what appears to be a plugin-cache timing issue.
Environment:
26.814.5517.026.814.4195726.814.41407What happened:
Cannot find module 'C:\Users\<user>\.codex\plugins\cache\openai-bundled\browser\26.814.41957\scripts\browser-service.mjs'26.814.41957, but the local plugin cache initially contained only26.814.41407.26.814.41957cache directory appeared automatically. SHA-256 checks confirmed thatplugin.json,browser-client.mjs, andbrowser-service.mjsexactly matched the files bundled in the installed Codex package.26.814.41957Browser client.No browser code was manually modified or overwritten. This suggests the updated plugin cache finished populating after the app had already started, while the existing Browser control session retained the earlier missing/stale module state.
I can't update to the new version you mentioned, I'm assuming rolling updates? I'm still on:
Codex Desktop:
26.814.41407Browser:
26.814.41407With browser not working, (internal, or chrome plugin etc.)
Do we have any idea when broader user base will get the newer version with fixed browser work ? Really needing that feature at this moment
There is a temporary workaround while waiting for the update.
Before I received the newer version, Codex could operate the visible in-app browser using Windows computer control instead of the broken Browser control plugin. It controlled the mouse and keyboard visually, so it was slower and occasionally needed manual help, but it allowed work in the existing authenticated browser session.
You can ask Codex:
“Use Windows computer control to operate the browser visually. Do not use the Browser plugin.”
This does not fix the underlying fault, but it may keep the browser usable until the updated version reaches you.
Thank you for that suggestion, I haven't experimented with full computer control yet, but that makes sense and I'll give it a go in the meantime. Appreciate the response
I have just received the update, and can confirm browser bug is fixed.