Windows desktop auto-update breaks Chrome and Computer Use with Trusted RPC path errors

Summary

After the Codex Windows desktop app automatically updated its bundled Chrome, Browser, and Computer Use components, both Chrome control and Computer Use began failing during initialization with Trusted RPC path/module validation errors.

The same machine, Chrome profile, signed-in page, Codex thread, and workflow worked earlier that day. No Chrome, extension, or Codex settings were changed by the user.

Environment

• Windows Codex Desktop package: 26.818.8289.0
• Current bundled Chrome / Browser / Computer Use plugin version: 26.818.61809
• Previously working Chrome plugin version: 26.818.41509

Timeline

1. Around 11:50 local time, Chrome control worked successfully with plugin version 26.818.41509. It enumerated multiple Chrome extension instances, skipped an empty instance, and claimed the instance containing the signed-in target tab.
2. Around 22:10, the bundled Chrome, Browser, and Computer Use plugin directories were automatically replaced with version 26.818.61809.
3. Around 22:11, the bundled control runtime also switched to a new build.
4. Immediately afterward, Chrome control failed before browser-instance or tab discovery.
5. Codex was fully exited and restarted after the update. New Codex processes were confirmed, but a fresh initialization attempt produced the same error.
6. The in-app feedback upload was retried multiple times and also failed, although the app retained a local feedback ID.

Chrome error

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

Computer Use error

Trusted RPC package must resolve within a configured trusted module directory:
@oai/sky/service

Expected behavior

After an automatic bundled-plugin update and app restart, Chrome and Computer Use service dependencies should be registered as trusted. Chrome control should enumerate connected extension instances and allow the existing signed-in tab to be claimed.

Actual behavior

Both browser control and Computer Use fail during initialization, before any browser instance, tab, webpage, or authentication state is inspected.

Additional observations

• The Chrome tab remained open and signed in throughout.
• The error occurs before extension-instance enumeration, so it is not caused by selecting an empty Chrome profile or by page login state.
• The previously working plugin version 26.818.41509 was removed by the automatic update, so a safe local rollback was not available.
• Restarting Codex after the update did not repair the trusted-path registration.
• This blocks scheduled workflows that require confirmation from an existing signed-in Chrome tab and cannot safely substitute cached data or another browser.

Please check whether the trusted RPC dependency/module registration in Windows Desktop 26.818.8289.0 is compatible with bundled plugin version 26.818.61809.

Start with the Windows Desktop package version 26.818.8289.0 and bundled plugin version 26.818.61809, comparing them with the previously working 26.818.41509 version. Investigate trusted RPC dependency and module registration during initialization, including the browser-service.mjs path and @oai/sky/service module. Done means Chrome control enumerates extension instances and Computer Use initializes successfully after an automatic update and restart.