ChatGPT Atlas has been discontinued: what replaced it and what it means for your site
OpenAI switched Atlas off on 9 August 2026, 292 days after launch. The browser is gone, the agentic traffic is not, and the replacements reach your site from different places.
OpenAI announced on 9 July 2026 that it was deprecating ChatGPT Atlas, and switched it off on 9 August 2026 — 292 days after launching it. The capabilities moved into ChatGPT and Codex. chatgpt.com/atlas now loads the ordinary ChatGPT page.
It is worth recording what it was, because a lot of writing about agentic browsers was written about Atlas specifically, and a fair amount of that writing is still circulating as though the product exists. Atlas shipped only for macOS 14.2 or later on Apple silicon. Windows, iOS and Android were announced as coming soon at launch and none of them arrived. Any Atlas-for-Windows installation guide you find is a holdover.
The pattern is worth more than the product
Atlas is the third OpenAI agentic-browsing product to be withdrawn in about a year:
| Product | Launched | Withdrawn |
|---|---|---|
| Operator | January 2025 | Access ended 31 August 2025, folded into agent mode |
| ChatGPT agent mode | 17 July 2025 | Removed early August 2026, no advance notice |
| ChatGPT Atlas | 21 October 2025 | 9 August 2026 |
Three product names, three withdrawals, and the underlying capability never went away — it moved. That is the actual lesson for anyone running a website, and it is a technical one: detection built around a product name or a user-agent string has a shelf life measured in months.
If you added a rule for ChatGPT-User in late 2025, or wrote a policy that named Atlas, that rule is now describing something that no longer exists while the traffic it was meant to catch arrives under a different label from a different place.
Where the traffic comes from now
| Replacement | Released | What reaches your site |
|---|---|---|
| ChatGPT desktop app, with built-in browser | 9 July 2026 (macOS, Windows); Linux preview 14 August 2026 | Agentic browsing from the user's machine |
| ChatGPT browser extension | For Chrome, and also Edge, Brave, Opera, Vivaldi | An assistant inside an ordinary browser session |
| ChatGPT Work | Rolling out | Longer multi-step tasks; no logged-in browser work |
| Perplexity Comet | July 2025, free since October 2025, all platforms | The agentic browser with the widest reach now |
The extension row is the one that should change how you think about this. An assistant operating inside ordinary Chrome does not announce itself with a distinctive browser build — it is Chrome, with the user's real profile, on the user's real connection. There is no product name to match on.
What to do instead of naming products
This is the argument we have been making about agentic browsers generally, and Atlas's withdrawal is a reasonably strong piece of evidence for it:
- Do not build policy around user-agent strings or product names. They change under you, and they are claims rather than credentials. In our own logs over thirteen days, 53% of requests presenting an AI-agent user-agent came from addresses belonging to none of the vendors named.
- Decide per flow, not per client. Let automation read. Require evidence of a person on checkout, bulk export and account changes — the places where scale causes the harm. That policy survives a product being renamed.
- Verify the agents you want by published IP range, which is the only method that works reliably today. OpenAI, Perplexity, DuckDuckGo and Google publish ranges; Anthropic does not.
- Watch Web Bot Auth, which replaces the name with a signature. That is the thing that would make an allow-list durable, and see agent identity for why identity alone still will not tell you whether to allow an action.
The browsers will keep being renamed. The question they pose to a site owner — a real customer has delegated a task to software, do you serve it — does not change with the branding.
Working out which agent traffic you are now seeing?
If agentic sessions are reaching your site and the user-agents have changed under you, tell us which user-agents and which endpoints. We will tell you which of them are worth allowing.
Frequently Asked Questions
Is ChatGPT Atlas still available?
No. OpenAI announced on 9 July 2026 that it was deprecating Atlas and switched it off on 9 August 2026, 292 days after launch. OpenAI's help centre said Atlas may no longer open, browse or support browser-based agentic workflows after that date, and chatgpt.com/atlas now loads the standard ChatGPT page.
What replaced ChatGPT Atlas?
Two things. The ChatGPT desktop app, which launched on 9 July 2026 for macOS and Windows with a Linux public preview on 14 August 2026, combines Chat, Work and Codex and has its own built-in browser for deeper agentic work. Separately there is a ChatGPT browser extension for Chrome, which also works in Edge, Brave, Opera and Vivaldi.
Did ChatGPT Atlas ever come to Windows?
No. Atlas only ever shipped for macOS 14.2 or later on Apple silicon. Windows, iOS and Android versions were announced as coming soon at launch and none of them was released before the product was switched off. Installation guides and waitlist pages for Atlas on Windows that are still circulating are holdovers from late 2025 and early 2026.
What happened to OpenAI Operator?
Operator was deprecated with access ending 31 August 2025 and its functionality folded into ChatGPT agent mode, which launched on 17 July 2025. Agent mode was itself removed from ChatGPT in early August 2026 without an advance deprecation notice, and OpenAI now points users to ChatGPT Work for longer multi-step tasks.
Does this mean agentic browser traffic has stopped?
No. The category outlived the product. Perplexity Comet is free on macOS, Windows, Android and iOS, the ChatGPT desktop app carries a built-in browser, and browser extensions put an assistant inside ordinary Chrome. What changed is where the traffic originates and what it calls itself, which is a good reason not to build detection around any particular product name.
