›_ Codex Issues
Codex Issues / #23283

Windows Codex Chrome plugin reinstall does not create native messaging host

Open 💬 11 comments Opened May 18, 2026 by dz1115
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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.

View original on GitHub ↗

11 Comments

github-actions[bot] contributor · 3 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #22558
  • #22598

Powered by Codex Action

arkuszzhu-maker · 2 months ago

I’m seeing the same failure on Windows after Codex update/reinstall, with the current bundled plugin cache now verified clean/current but the native messaging host still not created.

Environment:

  • Windows Codex app package: OpenAI.Codex_26.609.4994.0_x64__2p2nqsd0c76g0
  • Codex app version: 26.609.4994.0
  • Installed bundled plugins:
  • chrome@openai-bundled 26.609.41114, installed/enabled
  • computer-use@openai-bundled 26.609.41114, installed/enabled
  • Chrome extension ID: hehggadaopoacecdllhhajmbjkdcmajg
  • Chrome extension version: 1.1.5_0
  • Extension is installed/enabled in Chrome Profile 1.

Steps already tried:

  • Reinstalled the Codex Chrome plugin multiple times from the Codex plugin UI.
  • Removed/re-added chrome@openai-bundled via CLI.
  • Reinstalled/repaired the Codex Windows app and restarted Codex/Chrome/Windows.
  • Removed stale browser@openai-bundled state.
  • Refreshed %USERPROFILE%\.codex\plugins\cache\openai-bundled from the current WindowsApps Codex package and re-added Chrome/Computer Use plugins.
  • Verified the active plugin cache now matches the installed Codex package. Relevant current hashes match package source:
  • plugins/chrome/scripts/browser-client.mjs: 27DCA86FD6B571C49414A4B78E46B57BCF683A46CD1319799C11FBB6CFAE3110
  • plugins/chrome/extension-host/windows/x64/extension-host.exe: 8FDFBDE04D68A0CFC66E9F0A0737E79CB308011C59F2DE99B80D1F7CBC0385B3
  • plugins/chrome/.codex-plugin/plugin.json: 51533AF990E3B15F41DD29A95D1312F739E9DF19ACC420AFD4850E1A1BEDE260

Current result:

  • Codex reports chrome@openai-bundled installed/enabled at 26.609.41114.
  • The Chrome extension is installed/enabled at 1.1.5_0.
  • The native host is still missing:
  • %LOCALAPPDATA%\OpenAI\extension\com.openai.codexextension.json does not exist.
  • HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension does not exist.
  • Native host diagnostic reports:
  • Windows native host registry key does not exist: HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension; Native host manifest does not exist: %LOCALAPPDATA%\OpenAI\extension\com.openai.codexextension.json
  • The runtime only exposes the in-app browser backend; requesting the Chrome extension backend fails with Browser is not available: extension.

This looks like the Codex app/plugin install path is not running (or is failing before completing) the native host manifest/registry creation step, even when the bundled plugin cache is clean and current and the Chrome extension itself is installed/enabled.

linxiangpk1991 · 2 months ago

Adding another current Windows reproduction. This still reproduces after a full Codex reinstall and repeated Chrome plugin reinstalls from the Codex plugin UI.

Environment:

  • OS: Windows
  • Codex app package: OpenAI.Codex_26.609.4994.0_x64__2p2nqsd0c76g0
  • Codex app version: 26.609.4994.0
  • Chrome plugin cache: openai-bundled/chrome/26.609.41114
  • Chrome extension ID: hehggadaopoacecdllhhajmbjkdcmajg
  • Chrome extension version: 1.1.5_0
  • Selected Chrome profile: Default

What was tried:

  • Repaired/reinstalled the Chrome plugin from the Codex plugin UI many times.
  • Reset Codex.
  • Fully uninstalled/reinstalled Codex from Microsoft Store.
  • Fixed Microsoft Store loading on this machine by clearing Store cache and adding UWP loopback exemptions for Store-related packages.
  • Verified plugin cache health and browser-client trust hash.
  • Verified chrome@openai-bundled is installed/enabled.

What works:

  • check-extension-installed.js --json reports the Codex Chrome Extension is installed and enabled:
{
  "extensionId": "hehggadaopoacecdllhhajmbjkdcmajg",
  "selectedProfileDirectory": "Default",
  "installed": true,
  "enabled": true,
  "profiles": [
    {
      "profileDirectory": "Default",
      "installed": true,
      "registered": true,
      "enabled": true,
      "versions": ["1.1.5_0"],
      "selected": true
    }
  ],
  "exitCode": 0
}

What still fails:

  • %LOCALAPPDATA%\OpenAI\extension\com.openai.codexextension.json is not created.
  • HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension is not created.

Current native host diagnostic:

{
  "manifestPath": "%LOCALAPPDATA%\\OpenAI\\extension\\com.openai.codexextension.json",
  "registryKey": "HKCU\\Software\\Google\\Chrome\\NativeMessagingHosts\\com.openai.codexextension",
  "registryManifestPath": null,
  "expectedHostName": "com.openai.codexextension",
  "expectedExtensionId": "hehggadaopoacecdllhhajmbjkdcmajg",
  "expectedOrigin": "chrome-extension://hehggadaopoacecdllhhajmbjkdcmajg/",
  "exists": false,
  "correct": false,
  "problem": "Windows native host registry key does not exist: HKCU\\Software\\Google\\Chrome\\NativeMessagingHosts\\com.openai.codexextension; Native host manifest does not exist: %LOCALAPPDATA%\\OpenAI\\extension\\com.openai.codexextension.json"
}

Health check summary:

  • config.toml: ok
  • plugin cache manifests: ok
  • cache for chrome@openai-bundled: ok
  • trusted browser-client: ok
  • Codex Chrome Extension: ok, installed and enabled
  • Chrome Native Host: fail

This looks like the Chrome plugin install/repair UI is not running, or is silently failing before completing, the native host manifest + HKCU NativeMessagingHosts registration step. The failure persists even after the Store app and Codex app itself have been repaired/reinstalled.

LexingtonSara · 1 month ago

I'm hitting this exact issue on a fresh Windows install and did some digging that might help narrow down the root cause. Environment: Windows 11, Codex Microsoft Store package OpenAI.Codex_26.623.11225.0_x64__2p2nqsd0c76g0 (latest as of writing), Chrome extension hehggadaopoacecdllhhajmbjkdcmajg v1.1.5_0 (installed and enabled, confirmed via the bundled check-extension-installed.js diagnostic).

This happens even after a completely clean reinstall. I fully uninstalled Codex (including the Store package via Get-AppxPackage | Remove-AppxPackage), rebooted, reinstalled from the Store, and used the in-app "reinstall Chrome plugin" option. Neither the manifest nor the registry key gets created:

{
"manifestPath": "C:\\Users\\<user>\\AppData\\Local\\OpenAI\\extension\\com.openai.codexextension.json",
"registryKey": "HKCU\\Software\\Google\\Chrome\\NativeMessagingHosts\\com.openai.codexextension",
"exists": false,
"correct": false,
"problem": "Windows native host registry key does not exist: ...; Native host manifest does not exist: ..."
}
(output from the bundled scripts/check-native-host-manifest.js --json)

What I ruled out, in case it's useful:

  • The bundled extension-host.exe binary is present and intact in the installed package (app/resources/plugins/openai-bundled/plugins/chrome/extension-host/windows/x64/extension-host.exe) — so it's not a corrupted/missing-binary case.
  • Not MSIX file-system virtualization silently redirecting the write to a sandboxed location — the app's virtualized container folders (AppData\Local\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache and ...\AppData) are completely empty, so writes aren't landing there either.
  • Not a stale/separate plugin cache — there's no plugins/cache directory anywhere outside the Store package itself; the plugin code is loaded directly from the installed package.

What would help debug this further: Codex doesn't appear to write any log file for this install step (no AppData\Local\Codex\Logs, no AppData\Roaming\Codex at all get created), so there's no way for users to see what's actually failing inside installManifest.mjs when the "reinstall Chrome plugin" action runs. Would it be possible to add logging around this step (e.g., a log line if execFile('reg', ...) fails, or if the manifest writeFile throws) so we can report back the actual error instead of just "it didn't work"?

Happy to run more diagnostics if someone can point me at what else would help.

SamuelMiller · 1 month ago

I’m encountering the same issue on Windows after reinstalling the Chrome plugin numerous times through the ChatGBT (formerly Codex) plugin UI.

My diagnostics differ slightly from the original report:

  • Chrome is running.
  • Selected Chrome profile: Profile 3
  • Chrome plugin bundle version: 26.623.101652
  • ChatGBT reports: Browser is not available: extension
  • Chrome Extension is not registered in the selected profile.
  • The native-host registry entry exists.
  • The registry entry points to:

%LOCALAPPDATA%\OpenAI\extension\com.openai.codexextension.json

  • That manifest file does not exist.
  • Only the in-app browser is discovered; the Chrome extension backend is unavailable.

Repeated plugin reinstalls do not recreate the manifest or restore the Chrome extension connection. This suggests the reinstall/repair flow can leave a stale registry entry pointing to a missing native-host manifest.

zemeng5208 · 16 days ago

I maintain WinBridge Recovery, an independent Windows recovery tool focused on this exact class of Codex Desktop bundled-plugin state drift.

This issue is a strong match because the failure is not simply “Chrome extension missing”: the Chrome plugin can be present/current while both Native Messaging layers are absent:

  • %LOCALAPPDATA%\OpenAI\extension\com.openai.codexextension.json
  • HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension

WinBridge v3.1.1 diagnoses the current Store package, bundled marketplace, versioned plugin cache/latest, Node/CLI/runtime paths, Native Host manifest, Chrome/Edge HKCU registration, and chrome-native-hosts-v2.json as separate layers. That helps distinguish a clean/current plugin cache from a failed Native Host reconciliation step instead of reinstalling everything blindly.

The current recovery path can restore inconsistent user-side Native Host state with backup/rollback coverage. I am also moving the roadmap toward a safer default: restore/verify the official runtime + marketplace + plugin cache first, let Codex Desktop perform its own Native Host reconciliation when possible, then validate the result; direct manifest/registry reconstruction should remain a controlled fallback rather than the first action.

One diagnostic improvement I picked up from related reports: a checker that fails to execute reg query (for example spawnSync reg EPERM) should be reported as query failed / indeterminate, not automatically as registry key missing. WinBridge is tracking that distinction so it does not “repair” a registration that may already exist.

The project only uses the official package already installed on the target machine and does not modify WindowsApps ownership/ACLs or bypass browser/enterprise policy.

gtownbennett · 10 days ago

I can reproduce this on Windows with the current Store build, even though Settings reports that the Chrome browser extension is installed and enabled.

Environment (sanitized):

  • ChatGPT/Codex Desktop Store package: OpenAI.Codex 26.810.7004.0
  • Bundled Browser/Chrome/Computer Use plugins: 26.810.52044
  • Chrome extension ID: hehggadaopoacecdllhhajmbjkdcmajg
  • Chrome extension version: 1.2.27259.19709_0
  • Extension is installed/enabled in the selected Chrome profile

Observed state:

  • %LOCALAPPDATA%\OpenAI\extension\com.openai.codexextension.json is missing
  • HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension is missing
  • The equivalent Edge native-host key is also missing
  • %USERPROFILE%\.codex\chrome-native-hosts-v2.json is missing
  • The Chrome plugin cache exists, but its latest junction is missing
  • Chrome control is unavailable at runtime; only the in-app browser backend is available
  • Clicking Try now opens a new ChatGPT task instead of establishing Chrome control
  • The plugin UI previously failed to uninstall the Chrome plugin, and reinstall/restoring the signed bundled files did not create the native-host manifest or registry keys

I also tested the community WinBridge Recovery v3.1.1 source at release commit 42262f1b0d34f12a07d8b3ea187ffe41498e9f85:

  • Its isolated self-test passed.
  • Its wrapper's DiagnoseOnly mode exits early when the Browser plugin cache is absent, before reaching the Chrome diagnosis.
  • Running the same core in DiagnoseOnly mode reports 27 inconsistencies, including the missing Browser/Computer Use caches, stale runtime/config paths, missing Chrome latest, missing native manifest, both missing registry keys, and missing chrome-native-hosts-v2.json.
  • Its transactional repair correctly refused to make changes while ChatGPT Desktop was running; the write audit reported zero changes.

This looks like a Desktop/plugin materialization and native-host registration failure, not a disabled Chrome extension. I am proceeding with a controlled, backed-up repair while Desktop is closed and will report the runtime result separately.

gtownbennett · 10 days ago

Recovery follow-up: the user-side native-host repair succeeded, and live Chrome control is working.

WinBridge Recovery v3.1.1 completed its static repair, but its generated registration covered only one extension origin while the current bundled Chrome plugin expects two. After aligning the registration with the current plugin's own extension-ID configuration, the bundled native-host diagnostic passed with no missing origins.

Final runtime verification also passed: Chrome was discovered as an extension-backed browser, a real Chrome tab was created through the extension, navigation to https://example.com/ succeeded, and the page title was read back as Example Domain.

The official Desktop/plugin install path still failed to create this working registration on its own, so the original Windows bug remains reproducible even though this machine is now repaired.

OTUNA-corporate · 9 days ago

Adding another current Windows reproduction, this time on ARM64 and a newer Microsoft Store build. The native-host failure persists after a full app uninstall/reinstall, and browser runtime initialization now also fails trusted-path validation.

Environment (sanitized)

  • Windows 11 Home 25H2, build 26200.9168
  • ChatGPT/Codex Desktop Store package: OpenAI.Codex_26.814.5167.0_arm64__2p2nqsd0c76g0
  • Bundled Browser/Chrome plugin cache: 26.814.41407
  • Google Chrome: 151.0.7922.138
  • Codex Chrome Extension ID: hehggadaopoacecdllhhajmbjkdcmajg
  • Extension version: 1.2.27259.19709_0
  • Selected Chrome profile: Profile 1
  • Extension diagnostic: installed = true, enabled = true

Observed state

The current internal native-host state file exists:

%USERPROFILE%\.codex\chrome-native-hosts-v2.json

It has a current entry for app/plugin version 26.814.41407, both expected extension IDs, and the ARM64 host path:

%USERPROFILE%\.codex\plugins\cache\openai-bundled\chrome\latest\extension-host\windows\arm64\extension-host.exe

However, the externally required Native Messaging registration is still absent:

  • %LOCALAPPDATA%\OpenAI\extension\com.openai.codexextension.json
  • HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension

The bundled diagnostic reports:

Windows native host registry key does not exist:
HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension;
Native host manifest does not exist:
%LOCALAPPDATA%\OpenAI\extension\com.openai.codexextension.json

Chrome browser setup also fails before a Chrome backend can be selected:

Trusted RPC dependency must resolve within a configured trusted code path:
file:///%USERPROFILE%/.codex/plugins/cache/openai-bundled/browser/26.814.41407/scripts/browser-service.mjs

Recovery attempts already completed

  • Reinstalled the Codex Chrome Extension
  • Reinstalled the bundled Chrome and Browser plugins
  • Ran Windows app Repair
  • Fully uninstalled and reinstalled ChatGPT/Codex Desktop
  • Restarted the app and re-ran the bundled diagnostics
  • Did not manually create or modify the registry key or Native Host manifest

The result is unchanged. This appears to show two related/current failures: internal native-host state is materialized, but the Windows manifest/HKCU registration is not reconciled; separately, the Browser runtime rejects its bundled browser-service.mjs trusted path.

chrisma2021 · 9 days ago

Additional reproduction on a newer Windows/Codex build

I can still reproduce this issue after removing and reinstalling the Chrome plugin through the Codex plugin UI.

I followed the current [Chrome extension troubleshooting guidance](https://learn.chatgpt.com/docs/chrome-extension#troubleshooting), including removing and re-adding the plugin. The reinstall did not restore Chrome connectivity.

Environment
  • Windows 25H2, build 26200.9168
  • Codex desktop package: OpenAI.Codex_26.814.5167.0_x64__2p2nqsd0c76g0
  • Chrome plugin: 26.814.41407
  • Chrome extension ID: hehggadaopoacecdllhhajmbjkdcmajg
  • Chrome extension version: 1.2.27259.19709_0
  • Chrome profile: Default
  • Checked on: 2026-08-19 (UTC+8)
Installation result

The Codex desktop log reports a successful plugin installation:

2026-08-19T00:41:44.470Z
plugin_install_succeeded ... pluginName=chrome

The Chrome extension diagnostic also succeeds:

installed: true
registered: true
enabled: true
disabled: false
profileDirectory: Default
version: 1.2.27259.19709_0

The reinstall now creates this manifest:

%LOCALAPPDATA%\OpenAI\extension\com.openai.codexextension.json

The manifest is valid and points to:

%USERPROFILE%\.codex\plugins\cache\openai-bundled\chrome\latest\extension-host\windows\x64\extension-host.exe

The latest junction and extension-host.exe both exist.

However, the required registry key is still absent:

HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension

check-native-host-manifest.js --browser chrome --json reports:

{
  "exists": true,
  "correct": false,
  "registryManifestPath": null,
  "problem": "Windows native host registry key does not exist: HKCU\\Software\\Google\\Chrome\\NativeMessagingHosts\\com.openai.codexextension"
}

A direct registry query also confirms that the HKCU Chrome NativeMessagingHosts key does not exist.

Reconciliation does not repair the incomplete installation

After the incomplete installation, the app considers both the plugin and extension current:

bundled_plugin_chrome_extension_sync_decision
chromeExtensionSyncAction=keep_installed
installedPluginStatus=current
isExtensionInstalled=true
isPluginInstalled=true

It then skips installation:

bundled_plugin_install_skipped_current pluginName=chrome

This suggests the plugin health/reconciliation check validates the plugin and Chrome extension but does not validate the native-host registry registration. As a result, the missing key is not self-healed.

Additional trusted-path runtime failure

There is also a second error before Chrome discovery can complete. Loading the Chrome plugin’s client:

...\openai-bundled\chrome\26.814.41407\scripts\browser-client.mjs

fails with:

Trusted RPC dependency must resolve within a configured trusted code path:
file:///C:/Users/<user>/.codex/plugins/cache/openai-bundled/browser/26.814.41407/scripts/browser-service.mjs

The Chrome client is loaded from the chrome bundle, but its RPC dependency resolves from the sibling browser bundle and is rejected by the trusted-path check. Resetting the browser JavaScript runtime and retrying produces the same error.

This may be a separate packaging/trusted-root issue, but it also prevents Chrome from being used even before the missing native-host registry entry can be reached.

Likely fault boundaries
  1. The Windows plugin-install path writes the manifest but does not create, or fails to persist, the HKCU native-host registry key.
  2. The installer still returns plugin_install_succeeded.
  3. Reconciliation considers the installation current without checking the native-host registry entry.
  4. The trusted-code configuration for the Chrome plugin does not accept the shared Browser bundle’s browser-service.mjs, or the dependency is resolving from the wrong bundle.
Expected behavior
  • Plugin installation should create and validate both the manifest and this registry value:
HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension
(Default) = %LOCALAPPDATA%\OpenAI\extension\com.openai.codexextension.json
  • Installation should not report success/current status when native-host validation fails.
  • Reconciliation should repair a missing registry entry.
  • The Chrome client should resolve its RPC service from an approved trusted path.

I can provide the complete sanitized Codex desktop log if it would help.

chrisma2021 · 8 days ago
### Additional reproduction on a newer Windows/Codex build I can still reproduce this issue after removing and reinstalling the Chrome plugin through the Codex plugin UI. I followed the current [Chrome extension troubleshooting guidance](https://learn.chatgpt.com/docs/chrome-extension#troubleshooting), including removing and re-adding the plugin. The reinstall did not restore Chrome connectivity. #### Environment Windows 25H2, build 26200.9168 Codex desktop package: OpenAI.Codex_26.814.5167.0_x64__2p2nqsd0c76g0 Chrome plugin: 26.814.41407 Chrome extension ID: hehggadaopoacecdllhhajmbjkdcmajg Chrome extension version: 1.2.27259.19709_0 Chrome profile: Default Checked on: 2026-08-19 (UTC+8) #### Installation result The Codex desktop log reports a successful plugin installation: `` 2026-08-19T00:41:44.470Z plugin_install_succeeded ... pluginName=chrome ` The Chrome extension diagnostic also succeeds: ` installed: true registered: true enabled: true disabled: false profileDirectory: Default version: 1.2.27259.19709_0 ` The reinstall now creates this manifest: ` %LOCALAPPDATA%\OpenAI\extension\com.openai.codexextension.json ` The manifest is valid and points to: ` %USERPROFILE%\.codex\plugins\cache\openai-bundled\chrome\latest\extension-host\windows\x64\extension-host.exe ` The latest junction and extension-host.exe both exist. However, the required registry key is still absent: ` HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension ` check-native-host-manifest.js --browser chrome --json reports: { "exists": true, "correct": false, "registryManifestPath": null, "problem": "Windows native host registry key does not exist: HKCU\\Software\\Google\\Chrome\\NativeMessagingHosts\\com.openai.codexextension" } A direct registry query also confirms that the HKCU Chrome NativeMessagingHosts key does not exist. #### Reconciliation does not repair the incomplete installation After the incomplete installation, the app considers both the plugin and extension current: ` bundled_plugin_chrome_extension_sync_decision chromeExtensionSyncAction=keep_installed installedPluginStatus=current isExtensionInstalled=true isPluginInstalled=true ` It then skips installation: ` bundled_plugin_install_skipped_current pluginName=chrome ` This suggests the plugin health/reconciliation check validates the plugin and Chrome extension but does not validate the native-host registry registration. As a result, the missing key is not self-healed. #### Additional trusted-path runtime failure There is also a second error before Chrome discovery can complete. Loading the Chrome plugin’s client: ` ...\openai-bundled\chrome\26.814.41407\scripts\browser-client.mjs ` fails with: ` Trusted RPC dependency must resolve within a configured trusted code path: file:///C:/Users/<user>/.codex/plugins/cache/openai-bundled/browser/26.814.41407/scripts/browser-service.mjs ` The Chrome client is loaded from the chrome bundle, but its RPC dependency resolves from the sibling browser bundle and is rejected by the trusted-path check. Resetting the browser JavaScript runtime and retrying produces the same error. This may be a separate packaging/trusted-root issue, but it also prevents Chrome from being used even before the missing native-host registry entry can be reached. #### Likely fault boundaries 1. The Windows plugin-install path writes the manifest but does not create, or fails to persist, the HKCU native-host registry key. 2. The installer still returns plugin_install_succeeded. 3. Reconciliation considers the installation current without checking the native-host registry entry. 4. The trusted-code configuration for the Chrome plugin does not accept the shared Browser bundle’s browser-service.mjs, or the dependency is resolving from the wrong bundle. #### Expected behavior * Plugin installation should create and validate both the manifest and this registry value: ` HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension (Default) = %LOCALAPPDATA%\OpenAI\extension\com.openai.codexextension.json `` Installation should not report success/current status when native-host validation fails. Reconciliation should repair a missing registry entry. The Chrome client should resolve its RPC service from an approved trusted path. I can provide the complete sanitized Codex desktop log if it would help.

Update 2026-08-20: Chrome control now works, but native-host diagnostic still fails

The functional problem appears resolved with this newer combination:

  • Codex desktop: OpenAI.Codex_26.814.5517.0_x64
  • Chrome plugin: 26.814.41957
  • Windows 25H2

I successfully:

  • Connected Codex to the existing Chrome session.
  • Listed the open Chrome tabs.
  • Claimed an existing BBC News tab.
  • Read and summarized its current contents.

The previous trusted-path error involving the sibling browser-service.mjs is no longer present.

However, the bundled diagnostic still reports:

{
  "exists": true,
  "correct": false,
  "registryManifestPath": null,
  "problem": "Windows native host registry key does not exist: HKCU\\Software\\Google\\Chrome\\NativeMessagingHosts\\com.openai.codexextension"
}

The manifest and host executable exist, but this registry key remains absent:

HKCU\Software\Google\Chrome\NativeMessagingHosts\com.openai.codexextension

Therefore, one of the following appears to be true:

  1. The current Chrome connection no longer requires that registry entry, making check-native-host-manifest.js outdated for the new transport; or
  2. Chrome is connecting through another working path while the native-host installation remains incomplete.

The original user-facing failure is fixed for me, but the diagnostic and expected installation state are still inconsistent. It may be worth updating the diagnostic or clarifying whether the HKCU native-host key is still required.