OpenAI recently launched the new Codex Chrome extension, but many developers immediately ran into the same issue: the extension either cannot be installed, does not appear in the Chrome Web Store, or throws a generic installation error.
Some users see a “This item cannot be downloaded” message. Others cannot access the extension page at all. In some cases, the install button is simply missing.
The confusion became even bigger because the extension was officially announced only days ago.
So what is actually happening?
The Codex Chrome Extension Is Real
The first thing to understand is that the extension itself does exist.
OpenAI recently introduced browser integration for Codex as part of a broader push toward AI powered development workflows. The goal is much bigger than a simple browser sidebar or autocomplete assistant.
The Codex integration appears designed to connect AI directly with live browser sessions, authenticated dashboards, and active developer workflows. That means Codex could eventually inspect interfaces, interact with webpages, assist with debugging, and automate repetitive browser based tasks inside real environments.
This makes the extension one of OpenAI’s most ambitious developer focused releases so far.
Why the Extension Is Failing for So Many Users
Right now, the rollout appears unstable and incomplete.
Several users are reporting installation failures, missing Chrome Store pages, unavailable download buttons, and extension activation problems. The timing strongly suggests this is related to an early staged rollout rather than a permanent removal.
This kind of rollout is common with new AI tooling, especially when browser integrations depend on authenticated accounts, desktop applications, feature flags, regional permissions, and browser security approvals.
In practice, two users can visit the exact same extension page and still get completely different results.
Some Regions Appear Restricted
A large number of reports seem to come from European users.
That does not necessarily mean OpenAI intentionally blocked Europe, but it does suggest the rollout may currently be region dependent. Browser extensions that interact with authenticated sessions often face additional review requirements related to privacy, permissions, session security, and local regulations.
For users in the EU or UK, the extension may simply not be fully enabled yet.
The Desktop App May Be Required
Another important detail is that the Codex Chrome extension does not appear to function as a fully standalone extension.
OpenAI’s documentation references desktop integrations, browser linking, plugin activation, and reconnecting local services. This suggests the extension depends on communication between Chrome, the Codex desktop application, and authenticated OpenAI sessions.
That architecture is very different from a normal lightweight Chrome plugin.
It also explains why installation problems appear more severe than standard extension issues.
The issue is most likely not a permanent removal.
Instead, this looks more like a phased rollout that has not stabilized yet.
What You Can Try Right Now
If the extension is unavailable for you, there are still a few things worth trying.
First, update Chrome completely. Older Chromium builds sometimes create silent installation failures.
Second, sign out and back into your OpenAI account. Some feature gated rollouts rely on refreshed authentication sessions.
Third, install or reopen the Codex desktop application before attempting the browser integration again.
It may also help to temporarily disable VPNs, restart Chrome fully, or test another Chrome profile.
If none of that works, the problem is probably not on your side.
This Launch Is Bigger Than Most People Realize
Despite the rough rollout, this release matters.
OpenAI is clearly moving toward persistent AI assisted workflows instead of isolated chatbot interactions. That changes the role AI can play in software development entirely.
Instead of manually copying code into ChatGPT, browser integrated AI systems could eventually inspect live applications, navigate dashboards, debug interfaces, automate repetitive browser tasks, and execute workflows directly inside active sessions.
That is a major shift for development tooling.
It also explains why OpenAI is likely being extremely careful with browser permissions and rollout stability.
Final Thoughts
The Codex Chrome extension has not disappeared completely, but the rollout is clearly unstable right now.
For many users, the extension is unavailable, broken, or impossible to install. Most signs point toward an incomplete staged rollout rather than a permanent removal.
At the same time, the technology behind the extension could become one of OpenAI’s most important developer integrations yet.
The launch may be messy, but the direction is very clear: browser based AI agents are arriving much faster than most developers expected.
Top comments (12)
This looks a lot more like a Chrome Web Store rollout delay than anything specific to Codex. I’ve seen new extensions take a while to appear depending on region, account state, and how far the listing has propagated, so the “not available” message can be misleading early on.
Appreciate you calling it out, because this is exactly the kind of thing that trips people up right after a launch. A lot of devs will assume they’re missing a requirement or that access is restricted, when it can just be staged availability catching up.
That’s honestly a very fair point, and I think you’re probably right that Chrome Web Store propagation is a big part of it.
What made it confusing is that the errors users are seeing look almost identical to a removed or restricted extension, especially with the generic “not available” messaging Chrome gives. Combined with the timing of the launch, it immediately created the impression that access was limited or something had been pulled back.
The staged rollout explanation makes a lot of sense here, especially this early after release.
I thought the extension was removed completely. I spent 30 minutes trying different Chrome profiles and reinstalling Chrome itself. Nothing worked.
You’re definitely not the only one running into this right now. The rollout appears highly inconsistent depending on account, region, and whether the Codex desktop integration is active. A lot of people are assuming it was removed because Chrome throws a very generic error page instead of explaining what’s actually happening.
Same issue here in Germany. The extension page exists, but install is blocked. Looks like another half finished AI launch honestly.
There definitely seems to be a regional component involved. Most of the reports I’ve seen so far are coming from Europe and the UK. My guess is that browser permission reviews and staged rollout restrictions are slowing things down. The launch itself feels very early access at the moment.
OpenAI really needs to stop launching unfinished products. This is becoming a pattern.
I understand the frustration, especially because developers immediately try integrating these tools into real workflows. That said, browser based AI integrations are a completely different level compared to normal SaaS releases. Once an AI tool starts interacting with authenticated browser sessions, security reviews and rollout complexity increase massively.
Cursor still feels way more stable than this.
At the moment, I would agree. Cursor, Windsurf, and existing VS Code integrations are significantly more mature right now. The Codex Chrome extension feels more like the beginning of a larger long term strategy rather than a polished developer tool today.
Honestly this feels bigger than people realize. If Codex can actually interact with authenticated browser sessions, this changes everything.
Exactly. That’s the part many people are overlooking right now because everyone is focused on the installation problems. The real story is that OpenAI is moving toward persistent browser level AI workflows instead of isolated chatbot interactions. That could completely reshape browser automation and developer tooling over the next few years.