codex - 💡(How to fix) Fix Codex Desktop Chrome plugin unavailable even though extension and native host are installed

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

Codex Desktop 0.131.0-alpha.9 / Windows package OpenAI.Codex 26.513.4821.0

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Codex Desktop shows the Chrome plugin as unavailable even though the Chrome extension and native host appear to be installed correctly.

UI symptoms:

• Plugins page shows: Chrome Unavailable in this context openai-chrome
• Typing @Chrome in the composer shows: No results
• Chrome extension popup previously showed Disconnected

Local checks:

• chrome@openai-chrome is enabled in config.toml
• Chrome extension is installed and enabled
• Chrome extension ID: hehggadaopoacecdllhhajmbjkdcmajg
• Chrome extension version: 1.1.4_0
• Native host manifest check returns correct=true
• Native host manifest path: C:\Users\user\AppData\Local\OpenAI\extension\com.openai.codexextension.json
• extension-host.exe is running from: C:\Users\user.codex\plugins\cache\openai-chrome\chrome\latest\extension-host\windows\x64\extension-host.exe

Observed logs:

• Codex logs start only backend=iab
• I do not see Chrome/external backend startup logs
• This looks like Codex Desktop is exposing only the in-app browser backend, not the external Chrome backend

What steps can reproduce the bug?

Feedback: 019e36fd-fd05-72d1-8605-a5f797562f52

Steps to reproduce:

1. Install/enable the openai-chrome plugin in Codex Desktop.
2. Install the Chrome extension.
3. Restart Codex Desktop.
4. Open Codex Desktop Plugins page.
5. Observe that Chrome is listed as unavailable in this context.
6. Start a chat and type @Chrome.
7. Observe that @Chrome does not appear and the composer says No results.

Additional local verification already performed:

• check-extension-installed.js reports installed=true, registered=true, enabled=true
• check-native-host-manifest.js reports correct=true
• extension-host.exe process is running

What is the expected behavior?

Chrome plugin should be available in this context. @Chrome should appear in the composer, and Codex Desktop should be able to connect to the Chrome extension / external Chrome backend.

Additional information

Please check whether this Windows build/account has browser_use_external disabled, or whether the Desktop app/plugin/runtime versions are mismatched.