Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Windows Codex Chrome plugin reinstall does not create native messaging host

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…

Error Message

  • Runtime error from Chrome backend: Browser is not available: extension
RAW_BUFFERClick to expand / collapse

Codex Chrome plugin issue on Windows

Environment:

  • OS: Windows
  • Codex app version visible in path: OpenAI.Codex_26.513.4821.0_x64__2p2nqsd0c76g0
  • Chrome plugin cache: C:\Users\123.codex\plugins\cache\openai-bundled\chrome\0.1.7
  • Time checked: 2026-05-18T18:30:22+08:00

Problem:

  • After reinstalling the Codex Chrome plugin from the Codex plugin UI, Codex still cannot connect to Chrome.
  • Runtime error from Chrome backend: Browser is not available: extension
  • Chrome Web Store page for the Codex Chrome Extension shows "Item not available".

Diagnostics:

  • Missing native host manifest: C:\Users\123\AppData\Local\OpenAI\extension\com.openai.codexextension.json
  • Missing Windows registry key: HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension
  • Expected host name: com.openai.codexextension
  • Expected extension ID: hehggadaopoacecdllhhajmbjkdcmajg
  • Expected allowed origin: chrome-extension://hehggadaopoacecdllhhajmbjkdcmajg/
  • check-extension-installed.js output: Chrome user data directory does not exist: C:\Users\123\AppData\Local\Google\Chrome\User Data

Expected:

  • Reinstalling the Chrome plugin should create the native messaging host manifest and HKCU registry key, then allow Codex to communicate with the Codex Chrome Extension.

Actual:

  • The plugin entry is installed in Codex, but the native host manifest and registry key are not created, so Chrome automation remains unavailable.

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…
#runtime error#network issue#logging issue#authentication issue#prompt issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Windows Codex Chrome plugin reinstall does not create native messaging host