ChatGPT Agent
breaks out of Chrome.
Until last month, only Chrome users could hand browser tasks off to ChatGPT. OpenAI has now extended support to Edge, Brave, Opera, and Vivaldi — not just a compatibility patch, but a step in retiring its standalone "Atlas" app and folding its lessons back into ChatGPT itself.
Why OpenAI shelved
its standalone browser
In July 2025, OpenAI introduced ChatGPT Agent (formerly known as Operator), a browser-automation agent that can navigate websites, click, fill in forms, and complete multi-step tasks on its own. Its original showcase was a standalone AI browser app called Atlas — a dedicated "vessel" built to demonstrate agentic browsing.
This time, OpenAI is stepping back from that separate-app approach. Its official help-center article, "Evolving Atlas into ChatGPT for browser-based agentic work," confirms that OpenAI is folding what it learned from Atlas back into ChatGPT itself rather than asking users to switch apps. Instead of pulling people into a new app, OpenAI is meeting them inside the browser they already use — this isn't a one-off compatibility add-on, it's a shift from a "dedicated app" strategy to a "meet users where they already are" strategy.
The extension now reaches
four more browsers
The ChatGPT browser extension used to be Chrome-only. It now also supports major Chromium-based browsers.
As OpenAI's 2025 announcement "Introducing ChatGPT agent" explains, ChatGPT Agent operates directly inside a real browser — managing multiple tabs, downloading files, and even logging into accounts to complete tasks autonomously. This expansion carries the same capabilities OpenAI built for Atlas — multi-tab handling, downloads, improved navigation, and account login support — over to the newly supported browsers. So while the visible change is "more browsers supported," what actually happened underneath is that the capabilities of a separate app, Atlas, have been folded into ChatGPT's shared foundation.
Who benefits, and how
People who skipped browser automation for one reason only — "I don't use Chrome" — now have an option.
Edge-standardized enterprises
Companies whose IT policy sets Edge as the default browser can now use ChatGPT Agent's browser automation without installing anything extra. If "we need Chrome" was the reason your IT team shelved this, it's worth checking whether that's still true.
Engineers and automation owners
When building internal tools around ChatGPT Agent, you no longer need to force end users onto Chrome. Removing one browser constraint directly lowers the friction of rolling automation out across an organization.
Brave and Vivaldi regulars
Privacy-conscious users who stick with Brave or Vivaldi can now get the same automation benefits without switching browsers. Previously, reinstalling Chrome was a hidden cost of using the agent at all.
Re-check whether the browser was really the blocker
If your team passed on ChatGPT Agent because "it needed Chrome," confirm whether that's still the case. If the browser requirement was the only obstacle, it may be worth revisiting now.
Reinstall the extension on your target browser
If you use Edge, Brave, Opera, or Vivaldi, update the ChatGPT browser extension to the latest version and verify it works for a small task in your own environment.
Audit browser assumptions in your automation flows
Check internal runbooks and automation scripts for lingering "run this in Chrome" assumptions, and update the documentation now that support has widened.
Instead of shipping a dedicated app,
meet people inside the browser they already use.
Don't overtrust it: the limits worth flagging
Vendor claims of "expanded browser support" often lag the reality of actual behavior. Edge, Brave, Opera, and Vivaldi are all Chromium-based, so their extension APIs are close enough to Chrome's that a ChatGPT Agent extension built for Chrome has a realistic chance of working there. Still, browser-specific security defaults — Brave's aggressive tracker and content blocking, for instance — could interrupt some agent actions at the edges even within the Chromium family.
More notably, OpenAI's announcement does not mention Firefox or Safari. Both use rendering engines and extension APIs that differ from Chromium's, so this expansion covering "Chromium-family browsers" does not imply support across all browsers. If you rely on Firefox or Safari day to day, you're still outside the benefit of this update for now.