codex - 💡(How to fix) Fix Codex Chrome plugin shows Connected on Windows, but Codex cannot control Chrome and initialization times out

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

Unknown, latest Windows desktop app reinstalled on 2026-05-12

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

I’m using the Codex desktop app with the Chrome plugin on Windows. The Chrome extension popup shows Connected, but Codex still cannot read Chrome tabs or control the page.

Confirmed details:

  • The Chrome extension is installed and enabled, version v1.1.4
  • The Windows Native Messaging Host manifest exists: C:\Users\chen\AppData\Local\OpenAI\extension\com.openai.codexextension.json
  • The registry key exists: HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension
  • The manifest points to: C:\Users\chen\.codex\plugins\cache\openai-bundled\chrome\latest\extension-host\windows\x64\extension-host.exe
  • On the Codex side, calling browser.user.openTabs() keeps timing out
  • Reinstalling Codex, restarting Chrome, restarting Codex, and clearing extension-host.exe processes did not fix the issue
  • Chrome can be opened to a URL through a system command, but Codex cannot take control of the page, click elements, upload files, or read tabs

What steps can reproduce the bug?

  1. Install or reinstall the Codex desktop app on Windows.
  2. Enable/install the Chrome plugin.
  3. Open Chrome and confirm the Codex Chrome extension popup shows Connected.
  4. Ask Codex to control Chrome, for example to open tabs or interact with a logged-in website.
  5. Codex attempts to initialize the Chrome browser control backend.
  6. The operation times out, for example when trying to call browser.user.openTabs().

What is the expected behavior?

Codex should be able to read the current Chrome tabs and control the page through the Chrome plugin when the extension shows Connected.

Additional information

The Chrome extension shows Connected, but Codex cannot read tabs or control Chrome. The browser control module times out during initialization.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING