The "Chrome" and "Browser" plugins cannot be found in the Codex desktop application.

Open 💬 2 comments Opened Jun 27, 2026 by citizen132

💡 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 (From “About Codex” dialog)?

26.623.12021

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

The "Chrome" and "Browser" plugins cannot be found in the Codex desktop application. Although I was previously able to find the extension after manually enabling chrome@openai-bundled, the installation failed, and the extension disappeared again after I updated Codex. I would like to know if this is an account or platform deployment issue, or a problem with my local configuration or cache.

What steps can reproduce the bug?

<img width="1490" height="818" alt="Image" src="https://github.com/user-attachments/assets/64c1997f-d5ce-45d8-ab25-0df512e4bdce" />
<img width="1490" height="815" alt="Image" src="https://github.com/user-attachments/assets/181372a4-4336-4607-b855-0190d4c724a5" />

FeedBack ID:019efd44-2e65-7891-8f7b-dd96816c9519

What is the expected behavior?

I need to use these two plugins.

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

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

#30259
#30270

Powered by Codex Action

zemeng5208 · 16 days ago

I maintain WinBridge Recovery for Windows Codex Desktop bundled-plugin recovery: https://github.com/zemeng5208/winbridge-recovery

Because this started after a Codex update and both Chrome/Browser disappeared, one useful first step is to distinguish an account/availability problem from a local bundled-state problem. WinBridge checks the currently installed AppX resources against the generated openai-bundled marketplace, the versioned plugin caches/latest targets, and the Chrome Native Host/runtime paths.

If the current Store package contains the plugins but the generated marketplace/cache is incomplete or still references an older package/runtime, that is within the tool's recovery scope and it can rebuild the user-owned state from the already installed official package with verification/backups. If the local package/marketplace/cache are all healthy and the plugins are being filtered by a rollout/account gate, it reports that boundary rather than pretending to repair it.

It does not modify WindowsApps, bypass feature gates/policies, or bundle OpenAI binaries. Given the update timing here, the package-vs-marketplace/cache comparison should at least make the cause much clearer.