All posts
AI / Web

OpenAI Shuts Down Its Atlas Browser Less Than a Year After Launch

ZKO blog tile: AI

OpenAI's Atlas browser stopped working on 9 August 2026, less than a year after it launched. The company is not replacing it with a new version. Instead, the features Atlas offered, an AI sidebar that could read the page you were on and an agent mode that could carry out multi-step browsing tasks, are moving into ChatGPT and Codex directly.

Atlas launched as a Chromium-based desktop browser with ChatGPT built in. Beyond the chat sidebar, its agent mode could handle tasks like booking travel or running a piece of data analysis from inside the browser itself. What it never managed was a full platform rollout: promised builds for Windows, iOS and Android never shipped, not even as public betas, leaving Atlas a macOS-only product for its entire life.

According to OpenAI's help centre article on the shutdown, the company is building on what it learned from Atlas to support browser-based agentic work inside ChatGPT instead: multiple tabs, downloads, better navigation, and account login support are all listed as features moving into the main app. A Chrome extension and an in-app browser for the ChatGPT desktop client cover the rest, alongside a separate cloud browser for ChatGPT Work agents.

Users were told to export bookmarks and save any pages they wanted to keep before the shutdown date, since Atlas bookmarks do not transfer automatically. Chat history is stored separately and remains available regardless.

It is a fast reversal for a product line OpenAI launched with real ambition. Standalone AI browsers, also tried by Perplexity with Comet and by several smaller teams, have struggled to answer a simple question: why open a whole new browser, with all the extensions and bookmarks and muscle memory that implies, when the same AI features can just live in a sidebar or an extension on the browser you already use. OpenAI's answer, after nine months of Atlas, appears to be that they cannot, and that agentic browsing works better as a feature bolted onto an existing habit than as a habit of its own. For anyone building AI tools that touch the browser, that is the more durable lesson here than anything about Atlas specifically.