ChatGPT Atlas stopped working on August 9, 2026, ten months after it launched. Most of the coverage since has asked the same question: which AI browser should replace it? That’s the wrong question for almost everyone reading this. Atlas didn’t fail because AI-assisted browsing is a bad idea β it failed because a standalone browser was the wrong container for it. The capability survived. The product didn’t. Understanding that distinction is what actually decides what you should do next, not a ranked list of Atlas lookalikes.
What Actually Happened to ChatGPT Atlas
OpenAI launched Atlas on October 21, 2025 as a Chromium-based desktop browser with ChatGPT built into a sidebar, an omnibox that doubled as a chat prompt, and an agent mode β limited to paid ChatGPT plans β that could carry out multi-step tasks like shopping or research. Windows, iOS and Android versions were promised at launch and never shipped, even as a public beta; for its entire life, Atlas was a macOS-only product. OpenAI announced the shutdown on July 9, 2026, gave users a roughly 30-day window, and Atlas stopped working on August 9, 2026. Its browser-based agentic features didn’t disappear β OpenAI folded them into the ChatGPT desktop app, which picked up multi-tab support, downloads, improved navigation and account login handling, along with a ChatGPT extension for Chrome and related capabilities in Codex.
Why It Actually Failed
Atlas launched into a market where the incumbent, Chrome, already held people’s passwords, extensions, bookmarks and habits β and Atlas never gave most of them a strong enough reason to leave. Being macOS-only for its entire life cut it off from the majority of desktop users before features even entered the conversation. Security researchers also reported an unpatched prompt-injection vulnerability in Atlas’s omnibox, where a malicious URL could be interpreted as an instruction to the AI rather than a normal address β a class of flaw that OpenAI, Google and independent researchers broadly describe as unsolved across the whole category of AI browser agents, not unique to Atlas. None of that means agentic browsing is dead. It means shipping it as a separate browser, on one operating system, was the part that didn’t work.
If You Still Have Data Trapped in Atlas
If you haven’t migrated yet, treat this as urgent β OpenAI’s own guidance says the app “may no longer” open at all after the shutdown date, so there’s no guarantee it still works when you try.
| Data type | Transfers automatically? | What to do |
|---|---|---|
| Bookmarks | No | Open Atlas’s bookmark manager, export as an HTML file, then import that file into Chrome or another browser |
| Open tabs | No | Manually copy URLs into a note or bookmark each page individually before closing Atlas |
| Browsing history | No | No export path is provided β treat any history you need as already lost if you haven’t saved it |
| Cookies and active sessions | No | Cannot be imported into another browser; expect to sign back into every site and complete multi-factor authentication again |
| ChatGPT conversation history | Yes | Stored in your OpenAI account, not inside the Atlas browser, so it remains accessible through ChatGPT regardless of the browser shutdown |
The Real Choice: A Sidebar in Your Browser, or a New Browser
Set aside Atlas specifically and the current AI browser landscape actually resolves into two genuinely different products, and most guides blur them together. One category adds an AI panel to the browser you already use β ChatGPT’s own new Chrome extension, Claude for Chrome, and Gemini in Chrome (built directly into Chrome itself rather than as an extension) all work this way. The other category is a ground-up AI-native browser built for autonomous, multi-tab agent work β Perplexity’s Comet is the clearest example, alongside Dia and Opera Neon. The sidebar approach keeps your existing bookmarks, passwords, extensions and tab habits intact; the dedicated-browser approach asks you to move your whole browsing life over, the same bet Atlas asked for and lost.
| Tool | Type | Platforms | Cost |
|---|---|---|---|
| ChatGPT extension + desktop app | Sidebar, added to Chrome / standalone app | Cross-platform | Free shell; agent features need a paid ChatGPT plan |
| Claude for Chrome | Sidebar extension | Chrome, cross-platform | Requires a paying Claude plan |
| Gemini in Chrome | Built into Chrome directly | Rolling out; broadest reach by default | Deeper agent features gated to paid Google plans |
| Perplexity Comet | Dedicated AI-native browser | Windows, Mac, Android, iOS | Free; paid Perplexity tiers raise query limits, not required to use Comet |
| Dia | Dedicated AI-native browser | Mac only, reportedly | Free tier available, reported |
| Opera Neon | Dedicated AI-native browser | Desktop | Reported around $19.90/month, no free agent tier |
For most people who wanted Atlas for summarizing pages, drafting from context, or asking questions about what they’re reading, a sidebar dropped into Chrome covers that value without the switching cost. The case for an actual new browser comes down to one thing: whether you specifically need an agent that can act autonomously across several tabs β logging in, filling forms, completing a multi-step task on its own β rather than assisting you while you drive. If that’s genuinely what you need, Comet is currently the only option in this category that’s free and available across Windows, Mac, Android and iOS at once; Dia and several competitors remain limited to macOS.
Before You Turn On Agent Mode in Anything
Whichever route you take, the prompt-injection risk that dogged Atlas isn’t specific to it β it applies to any tool that can read a page and act on it. Run agent features in a separate browser profile, keep banking, primary email and password managers out of its reach, and treat “acts on the page for you” as the risk to manage, not the shell it runs in.
Who Should Actually Switch Browsers
Stay with your current browser plus a sidebar extension if you mainly want summaries, research help, or drafting assistance β that’s most people, and it costs nothing to try. Consider a dedicated AI-native browser only if autonomous multi-tab task completion is the specific feature you’re after, you’ve weighed the security tradeoffs, and β if you’re not on a Mac β you’ve confirmed the tool you want actually ships on your platform, since several of the category’s best-known names still don’t.
Frequently Asked Questions
When exactly did ChatGPT Atlas shut down?
OpenAI announced the shutdown on July 9, 2026, and Atlas stopped working on August 9, 2026, roughly ten months after its October 21, 2025 launch.
Can I still get my bookmarks and history out of Atlas?
Bookmarks can be exported as an HTML file and imported into another browser, but OpenAI’s own guidance warns Atlas may no longer open at all after the shutdown date, so this should be done immediately if you haven’t already. Browsing history has no export path.
Did my ChatGPT conversations disappear along with Atlas?
No. Conversation history is tied to your OpenAI account, not the Atlas browser itself, so it remains accessible through ChatGPT regardless of the browser shutdown.
What replaced Atlas’s agent features?
OpenAI moved browser-based agentic capabilities into the ChatGPT desktop app, which gained multi-tab support, downloads and improved navigation, along with a new ChatGPT extension for Chrome and related capabilities in Codex.
Do I need to switch to a whole new browser to get AI browsing features?
Usually not. Sidebar extensions like ChatGPT’s Chrome extension, Claude for Chrome, and Gemini in Chrome add most of the assistant value to the browser you already use. A dedicated AI-native browser is only worth the switch if you specifically need autonomous, multi-step agent actions across tabs.
Is prompt injection still a risk with the tools that replaced Atlas?
Yes. Any AI feature that can read a page and act on it carries some prompt-injection risk, and OpenAI, Google and independent researchers describe it as an unsolved problem across the category, not something specific to Atlas.