Chrome plugin connection times out despite extension showing Connected

What version of Codex CLI is running?

codex-cli 0.130.0

What subscription do you have?

Unknown

Which model were you using?

GPT-5 in Codex app (Chrome plugin task)

What platform is your computer?

Darwin 25.3.0 arm64 arm; macOS 26.3.1 (25D771280a)

What terminal emulator and version are you using (if applicable)?

Codex app / Chrome plugin workflow; terminal not involved. Shell: zsh; Ghostty installed.

What issue are you seeing?

The Codex Chrome plugin cannot connect from Codex even though the Chrome extension popup shows "Connected".

When using @chrome from Codex, the browser-client connection times out repeatedly while trying to list/control Chrome tabs. Reinstalling the Chrome plugin and reopening Chrome did not fix it.

Thread ID: 019e0b4c-4552-76e3-b094-1985eb424eb4

What steps can reproduce the bug?

Uploaded thread: 019e0b4c-4552-76e3-b094-1985eb424eb4

1. In Codex app, use @chrome for a task that needs the signed-in Chrome browser.
2. Codex tries to connect to Chrome and list/open tabs.
3. The browser-client call times out.
4. Retry after waiting.
5. Confirm Chrome is running.
6. Confirm Codex Chrome Extension is installed/enabled and its popup shows "Connected".
7. Confirm native host manifest check passes.
8. Open a fresh Chrome window for the Default profile and retry.
9. Reinstall the Chrome plugin and retry.

Observed: the connection still times out.

What is the expected behavior?

Codex should connect to the Chrome extension and list/control Chrome tabs.

Additional information

Environment observed during troubleshooting:

• Google Chrome 147.0.7727.138
• Codex Chrome Extension v1.1.4
• Extension installed/enabled check passed.
• Native host manifest check passed.
• Chrome running check passed.
• Computer Use could see Chrome and the extension popup showing Connected, but @chrome browser automation remained unusable.