Chrome plugin backend times out even though extension native host reports connected

What happened?

The Codex Chrome plugin backend consistently times out while initializing, even though the Chrome extension appears installed, enabled, and connected to the native host.

From Codex, initializing the Chrome browser-use backend hangs and eventually times out after 30 seconds before it can list or claim Chrome tabs.

Thread ID: 019e0bc5-5fe2-7d62-a905-9c5ee667449f

Environment

• Codex app: 26.506.31421
• macOS: 26.4.1 (25E253)
• Google Chrome: 148.0.7778.97 arm64
• Chrome profile: Default
• Codex Chrome Extension: 1.1.4
• Extension ID: hehggadaopoacecdllhhajmbjkdcmajg
• Native host: com.openai.codexextension

What I tried / verified

• Verified Chrome is running normally.
• Verified the Codex Chrome Extension is installed, enabled, and registered in the Default profile.
• Verified the native messaging manifest exists and points to the bundled extension-host.
• Verified the native host binary exists, is executable, is Mach-O arm64, and does not have the com.apple.quarantine attribute.
• Verified the extension-host process is running.
• Verified the Chrome extension details page includes the native messaging permission.
• Toggled the Codex Chrome Extension off and on; the service worker and native host restarted.
• In the extension service worker DevTools, chrome.storage.local.get("NATIVE_HOST_STATUS") reported state: "connected".
• Restarted the Codex desktop app and retried the Chrome plugin connection twice; both attempts still timed out after 30 seconds.
• Checked /tmp/codex-browser-use sockets and confirmed the extension-host process is holding a socket under that directory.
• Temporarily isolated stale/non-Chrome browser-use sockets during diagnosis; the Chrome backend still timed out. The temporary changes were restored.

Expected behavior

Codex should connect to the running Chrome extension/native host and be able to list or claim open Chrome tabs.

Actual behavior

Codex hangs during Chrome backend initialization and times out after 30 seconds. It never reaches tab listing/claiming.

Additional notes

This appears to match the troubleshooting case where the extension shows as connected but Codex still cannot use Chrome. I did not find an existing open issue that exactly matches com.openai.codexextension / hehggadaopoacecdllhhajmbjkdcmajg / this native host timeout behavior.