Built-in browser frequently fails across projects; connection still fails after desktop app update

Summary

The built-in browser has been unreliable for a long time while working on different projects. It frequently encounters problems. The specific failure below is reproducible now, including after updating the desktop app.

Current reproducible failure

1. On Windows, use the ChatGPT/Codex desktop app and ask Codex to connect to the built-in Browser for a page test.
2. Browser initialization fails before any page can be opened or navigated.
3. Reset the browser automation session and retry. The same error occurs.

Actual result: e.nodeRepl?.setResponseMeta is not a function

Expected result: The built-in browser connects and can open a page for testing.

Environment and observations

• Windows desktop app package version after update: 26.915.3509.0
• Previously running package version: 26.911.7940.0
• Browser plugin cache version observed locally: 26.602.40724
• The same initialization error occurred before and after the app update, and again after resetting the browser automation session.
• This is one confirmed manifestation of the broader, long-running reliability problem. Other past browser failures have not been characterized here.

Please investigate the browser integration and any compatibility issue between the desktop app, browser plugin, and browser automation runtime. No session transcripts or logs are attached.

Start by reproducing the Windows failure with desktop app versions 26.915.3509.0 and 26.911.7940.0, the observed browser plugin cache version, and a reset browser automation session; inspect the browser integration and compatibility boundaries around setResponseMeta. Done means initialization succeeds and the built-in browser can open and navigate to a page.