macOS: Chrome browser control times out with “No ChatGPT browser route is available” #48322

Summary

Chrome browser control is unavailable in Codex Desktop on macOS. Chrome and the ChatGPT extension are discovered successfully, but every tab-control request times out.

Environment

• Codex Desktop: 26.917.71314 (build 10954)
• macOS: Apple Silicon
• Google Chrome: 154.0.8037.58
• ChatGPT Chrome extension: installed and enabled in the Default profile

Observed behavior

The browser runtime can select Chrome and retrieve its documentation, but:

• chrome.user.openTabs() times out after about 30 seconds
• chrome.tabs.list() is unavailable for the same reason
• Reinitializing the browser runtime produces the same result
• The Codex desktop log reports: No ChatGPT browser route is available for browser session ...
• The browser-control runtime reports: nodeRepl.fetch request failed

Diagnostics completed

• Chrome is running normally.
• The official Chrome extension is installed and enabled.
• The Native Messaging host manifest exists and has the expected host name and extension origins.
• The native host process is running.
• Reinstalled Chrome and the extension.
• Restarted Chrome and Codex.
• Recreated the browser-control session and tested again.
• The failure remains after these steps.

The issue appears to be in Codex Desktop browser session-route registration or browser-control RPC, rather than Chrome installation, extension enablement, or a target website.

Expected behavior

After Chrome discovery succeeds, Codex should be able to enumerate and control the user's open Chrome tabs, or return an actionable component-level error instead of timing out.

Related reports: #43787 and #47270.