Chrome Extension not working with Chrome Beta 150

I can reproduce a related second-stage failure on macOS with Chrome Beta 150.

Initial state matched this issue: Codex had installed the native host manifest under stable Chrome, but not under Chrome Beta:

~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.openai.codexextension.json
# present

~/Library/Application Support/Google/Chrome Beta/NativeMessagingHosts/com.openai.codexextension.json
# missing

After copying the same native host manifest into the Chrome Beta NativeMessagingHosts directory and fully restarting Chrome Beta, the extension popup changed to connected. The native host process also starts successfully:

~/.codex/plugins/cache/openai-bundled/chrome/latest/extension-host/macos/arm64/extension-host chrome-extension://hehggadaopoacecdllhhajmbjkdcmajg/

The Chrome backend is then usable from Codex. agent.browsers.list() includes the extension backend and browser.user.openTabs() succeeds, so the live bridge is working.

However, Codex settings still reports the Chrome integration as not connected. The bundled checker appears to keep inspecting stable Chrome only:

{
  "userDataDirectory": "~/Library/Application Support/Google/Chrome",
  "selectedProfileDirectory": "Default",
  "installed": false,
  "enabled": false
}

When the same checker is pointed at Chrome Beta, it passes:

{
  "userDataDirectory": "~/Library/Application Support/Google/Chrome Beta",
  "selectedProfileDirectory": "Default",
  "installed": true,
  "enabled": true,
  "versions": ["1.1.5_0"]
}

So there seem to be two Chrome Beta gaps:

1. The native host manifest is not installed for Google/Chrome Beta.
2. After fixing that manually, the Codex app settings health check still reports disconnected because it checks stable Chrome rather than the live connected Chrome Beta backend/profile.

Environment details from this repro:

• macOS arm64
• Chrome Beta 150.0.7871.13
• Codex Chrome extension 1.1.5_0
• Chrome plugin bundle 26.611.61753

About two weeks since I reported the bug and no action from Codex team here - does that mean this bug will not be dealt with?

Confirming this remains reproducible on the July 9, 2026 unified ChatGPT/Codex build, including after reinstalling the bundled Chrome plugin.

Environment:

• ChatGPT/Codex app: 26.707.31123 (build 5042)
• macOS, Apple Silicon
• Google Chrome Beta: 151.0.7922.19
• ChatGPT Chrome Extension: 1.2.27203.26575_0
• Bundled plugin: chrome@openai-bundled version 26.707.31123
• macOS default browser bundle ID: com.google.chrome.beta

Verified state:

• The extension is installed, registered, and enabled in Chrome Beta's Default profile.
• The app's bundled browser detector reports the default browser as unknown app (com.google.chrome.beta) and inspects the stable Chrome profile tree instead.
• The app logs record isExtensionInstalled=false even though the extension is enabled in Chrome Beta.
• The native host manifest exists and validates under stable Chrome:

~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.openai.codexextension.json

• The corresponding Chrome Beta manifest is not created:

~/Library/Application Support/Google/Chrome Beta/NativeMessagingHosts/com.openai.codexextension.json

• No extension-host process starts for Chrome Beta.
• The extension popup remains Disconnected.
• Runtime probe fails immediately with: Browser is not available: extension.

Recovery attempts:

• Fully restarted the app and Chrome Beta.
• Reinstalled chrome@openai-bundled from the app UI.
• Rechecked the Beta profile and native-host registration after reinstall; the Beta manifest is still missing.

This appears to be a Chrome Beta detection/native-host registration gap rather than a stale browser-use socket problem, since the failure occurs before an extension host is launched.