OpenAI retired the Atlas browser on August 9, 2026. Where the browsing agent lives now

Where Atlas stands (read 2026-09-25)

Each row is one OpenAI page opened in a browser on September 25, 2026, with what it returned. No third-party report is used in this section.

So the only page that answers "did Atlas stop working on August 9?" in the past tense is the deprecation notice on the launch post. The help article, which is the page people search for by title, was last touched at the end of August and still describes the shutdown as scheduled. We did not run Atlas ourselves and cannot say from OpenAI's pages whether an installed copy opens today.

What replaced it, by release-note date

The July 9 article promised "a more capable browser experience in ChatGPT, including multiple tabs, downloads, improved navigation, account login support". The ChatGPT release notes show that arriving in dated pieces. Quotes are OpenAI's.

That is the account-login support, the multi-surface reach and the tool access the July article described, now in the default app and a five-browser extension rather than a separate download. The population of ChatGPT users who can point an agent at a website did not shrink when Atlas went away.

What OpenAI said on July 9 (the original announcement)

The primary source is OpenAI's own support article, “Evolving Atlas into ChatGPT for browser-based agentic work”. Its opening line: “We're deprecating Atlas and moving browser-based agentic capabilities into ChatGPT and Codex.” The specifics as published in July:

• Atlas stops working on August 9, 2026. OpenAI's words: after that date “Atlas may no longer open, browse, or support browser-based agentic workflows.” The browser launched in October 2025, so it was retired inside ten months. The FAQ states the plan as "an approx. 30 day wind down period" from a July 9 announcement.
• The capability moves, it doesn't die. OpenAI says it is “building on what we learned from Atlas to support a more capable browser experience in ChatGPT, including multiple tabs, downloads, improved navigation, account login support, and other browser improvements where available.”
• Two surfaces replace one. For “deeper agentic browser work,” OpenAI points users to the ChatGPT desktop app. For browsing help inside Chrome, it points to the ChatGPT Chrome extension or sidebar.
• Atlas data does not follow. Bookmarks, open tabs, and browser history do not transfer automatically; OpenAI told users to export bookmarks to an HTML file and import them into another browser such as Chrome before August 9. Cookies and active sessions cannot be imported into another browser.

Why a browser shutdown is an AI-visibility story

It is tempting to file this as product news: a company killed an app that didn't catch on. The part that matters for anyone who cares about being recommended by AI is where the capability landed. A standalone browser is a thing a user has to choose, download, and switch to. A feature inside the ChatGPT desktop app and a browser extension is a thing that shows up in the tool people already have open. The population of users who can point an agent at your website goes up, not down.

And note what the August 25 release note says the agent can do: sign in where a site allows it, keep the session, and complete a task up to the point of a reservation or payment. That is not a summarizer skimming a homepage. That is an agent that can move through a site the way a customer does: click into a booking page, open a pricing table, get past a login. The question “can an AI find and understand my business?” stops being about whether a crawler indexed your text and starts being about whether a machine can complete the journey a buyer would.

Three concrete implications

• Agent traffic is not a rounding error, and it doesn't convert like human traffic. Cloudflare's own data, which we covered on July 9, showed AI crawlers extracting content at lopsided ratios relative to the referrals they send back. Folding the agent into the default app pushes that ratio further. Anything you measure in Google Analytics will keep telling you nothing about it.
• Machine-readability is now a conversion issue, not just an SEO one. If your prices, service list, service area, or booking flow are locked behind JavaScript, a chat widget, a PDF, or an image, an agent working on a customer's behalf has to guess or give up. Competitors whose information is in plain HTML are the ones it can act on. The August 31 site-tools note adds a second path: a site can expose tools to the agent through WebMCP, in the desktop browser only.
• The engines still disagree about you, and the browser change doesn't fix that. In our 1,120-answer comparison across four engines, ChatGPT named the audited business in 16% of answers while Claude named it in 38%: same business, same questions. A better browser in ChatGPT changes how the agent reads the web; it does not change whether the model decides to name you.

The takeaway

August 9 was a hard date for a small number of Atlas users and a signal for everyone else: agentic browsing was pushed into the default surface, and the release notes since then show it gaining logins, more browsers and site tools. The businesses that will do well when a customer's assistant goes looking on their behalf are the ones whose sites can be read and acted on by a machine, and that are named by the model in the first place. Start with the second half, because it is the one you cannot see: a free 60-second check samples ChatGPT and Perplexity (the $79 audit adds Gemini and Claude, 25 questions sampled three times each) and reports how often each one actually recommends your business. If you run this problem for clients, the agency 5-pack runs the same audit five times over, white-labeled.