[Windows 26.814] Browser and Chrome control stopped after morning component update

Summary

Browser control worked normally on the morning of August 18, 2026, then both the built-in Browser and Chrome control stopped working at approximately 11:00 a.m. Pacific. Both now fail before browser discovery with the same trusted RPC path error.

This appears to be an independent reproduction of #39136 and related reports, with local timestamps that may help identify the rollout window.

Environment

• Windows 11 x64
• Codex desktop package: OpenAI.Codex_26.814.5167.0_x64
• Browser plugin: 26.814.41407
• Chrome plugin: 26.814.41407
• Chrome extension/native-host integration installed and enabled

Error

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

Timeline in Pacific time

• Browser control worked during the morning of August 18.
• Local desktop logs first show Browser release 26.814.41407 active at approximately 8:56 a.m.
• The cached Browser and Chrome 26.814.41407 component directories were created at approximately 9:40 a.m.
• The failure was first noticed at approximately 11:00 a.m.
• A new projectless task produced the same error, so the failure is not confined to one existing task or project folder.

This timing is consistent with a staged component/update rollout followed by failure when a new browser-control worker initialized.

Troubleshooting already completed

• Restarted Codex and Chrome.
• Restarted Windows.
• Used Windows App Repair.
• Verified that browser-service.mjs exists and is readable.
• Verified that the installed Browser and Chrome client files match by SHA-256.
• Verified the configured trusted browser-client hash against the installed file.
• Verified that the rejected service path is under the configured trusted .codex root.
• Retested from a fresh projectless task.
• Tested the Browser service independently with the required trusted environment; the service loads successfully outside the failing task path.

The failure occurs before browser discovery, tab access, site authentication, or Chrome-extension communication. This makes the target website, Chrome profile, and extension permissions unlikely to be the immediate cause.

Expected behavior

The version-matched bundled Browser service should be accepted as trusted, allowing both the built-in Browser and Chrome integrations to initialize normally.

Related reports

• #39136
• #39173
• #39212
• #39236
• #39252
• #39253

No browser contents, cookies, credentials, or client information are included in this report.