Chrome extension reports app not installed because native-host manifest points to stale plugin link on macOS

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

What version of the Codex App are you using?

26.707.31123 (build 5042)

What platform is your computer?

  • macOS 27.0 (26A5368g)
  • Apple Silicon (arm64)
  • Google Chrome 150.0.7871.115

What issue are you seeing?

The ChatGPT Chrome Extension side panel displays:

Install the app to use ChatGPT in Chrome

However, the desktop app is installed at /Applications/ChatGPT.app, is currently running, and has bundle identifier com.openai.codex.

Codex cannot acquire the Chrome backend and reports:

Browser is not available: extension

Local inspection found a concrete broken native-host path:

~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.openai.codexextension.json

The manifest exists, has the expected host name and allowed origin, and the bundled checker reports correct: true. Its configured executable is:

~/.codex/plugins/cache/openai-bundled/chrome/latest/extension-host/macos/arm64/extension-host

But the latest symlink is stale:

~/.codex/plugins/cache/openai-bundled/chrome/latest
  -> ~/.codex/plugins/cache/openai-bundled/chrome/26.616.71553

That old target no longer exists. The installed Chrome plugin is version 26.707.31123, and its native host exists at:

~/.codex/plugins/cache/openai-bundled/chrome/26.707.31123/extension-host/macos/arm64/ChatGPT for Chrome

So there are two mismatches:

  1. latest still targets a removed plugin version.
  2. The current macOS native-host binary is named ChatGPT for Chrome, while the stale manifest expects extension-host.

The generic “Install the app” message appears to be the extension's fallback when the native messaging host cannot be launched, rather than evidence that the desktop app is absent.

What steps can reproduce the bug?

  1. Install/update the Codex desktop app and bundled Chrome plugin.
  2. Install and enable the ChatGPT Chrome Extension.
  3. Open Chrome and open the extension side panel.
  4. Observe “Install the app to use ChatGPT in Chrome.”
  5. Verify that /Applications/ChatGPT.app is installed and running.
  6. Inspect com.openai.codexextension.json and the bundled plugin latest symlink.
  7. Observe that the manifest resolves through a stale symlink to a nonexistent executable.

Troubleshooting already attempted

  • Fully quit and reopened Chrome and the desktop app.
  • Uninstalled and reinstalled the bundled Chrome plugin.
  • Restarted both applications after reinstalling.
  • Verified the desktop app is installed.
  • Verified the native-host manifest exists and has the expected extension origin.

The stale symlink and manifest path persisted.

What is the expected behavior?

Installing or updating the bundled Chrome plugin should:

  • update the latest link to the active plugin version;
  • rewrite the Chrome native-host manifest with the current executable name/path; and
  • allow the Chrome extension to connect to the running desktop app.

The native-host diagnostic should also verify that manifest.path exists and is executable. At present it can report correct: true even when the configured executable does not exist.

Additional information

There are other open reports of Chrome backend discovery failures, including #31769, but this report identifies a specific stale symlink and nonexistent manifest executable on macOS.

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 1 month ago

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

  • #31769

Powered by Codex Action

ofek · 1 month ago

This is also happening for me on Windows.

<img width="776" height="568" alt="Image" src="https://github.com/user-attachments/assets/7e38b577-029f-4064-a55b-97fb8f7ba218" />

cowboycodr · 1 month ago

Posting issues here seems like a lost cause unfortunately.

TTCashier · 1 month ago

I had this issue on ChatGPT 26.707.41301.

I asked Codex to diagnose it. It found a stale plugin symlink, the renamed ChatGPT for Chrome host, and app-server paths still pointing to /Applications/Codex.app.

Codex repaired the links and changed the stale paths to /Applications/ChatGPT.app. The extension now connects and can control Chrome successfully.

bobobo2026 · 1 month ago

Confirming this is still reproducible on macOS arm64 with the newer bundled Chrome plugin version 26.707.72221.

Observed local state:

  • ~/.codex/plugins/cache/openai-bundled/chrome/latest still points to the removed version 26.616.71553.
  • com.openai.codexextension.json still resolves to .../latest/extension-host/macos/arm64/extension-host.
  • That executable does not exist.
  • The current plugin instead contains extension-host/macos/arm64/ChatGPT for Chrome.
  • The Chrome extension displays “Install the app to use ChatGPT in Chrome”.
  • Codex reports Browser is not available: extension.

Fully quitting and reopening Chrome/Codex, reinstalling the Chrome extension, and removing/reinstalling the integration did not repair the stale symlink or native-host manifest.

This confirms the issue persists in a newer plugin build. The plugin update/install flow should atomically refresh latest, rewrite the native-host manifest with the current executable name, and verify that the resolved executable exists before deleting the previous plugin version.