Skip to content
NewsProduct launch

OpenAI Folds Codex into ChatGPT Desktop and Sets August 9 End Date for Atlas Browser

· by Pondero Newsdesk

The short version

OpenAI merged the Codex app into a unified ChatGPT desktop on July 9 and confirmed August 9 as the shutdown date for the Atlas standalone browser, launched just nine months ago.

OpenAI Folds Codex into ChatGPT Desktop and Sets August 9 End Date for Atlas Browser

Two OpenAI products are disappearing as standalone apps. The Codex coding environment merged into a new unified ChatGPT desktop application on July 9, and the Atlas browser received a firm end date: August 9, 2026. Neither shutdown is a surprise in isolation, but the combined move consolidates the entire OpenAI desktop surface into one application within a month.

What happened

OpenAI shipped a new ChatGPT desktop application on July 9, 2026 that combines Chat, the new ChatGPT Work agent, and Codex in a single window. The app is available on macOS immediately, with Windows rolling out over the following days. Every plan tier, including Free, gets access to the combined app.

For existing Codex desktop users, the transition is a forced update rather than a migration. Per Implicator.ai's coverage, existing users can update the Codex app and their projects, settings, and workflows carry over automatically. After the update, the app becomes the new ChatGPT desktop with Codex remaining available as a dedicated coding mode. Developers who prefer the Codex view can still set it as the default and keep the Codex logo as the macOS app icon.

The Atlas browser, OpenAI's standalone Chromium-based browser that launched on Mac in October 2025, has less than a month left. OpenAI's James Sun confirmed per 9to5Mac that August 9 is the current deprecation target. Atlas's agentic-browsing capabilities move into the ChatGPT desktop app's built-in browser and an updated Chrome sidebar extension. The category read from the Digital Applied analysis of the launch is direct: "the standalone AI browser as a category now has a serious existence question" once the best-resourced lab in AI concluded a separate browser product was redundant with an assistant that ships with browsing built in.

One technical note for Mac users: the old native ChatGPT Mac app was 159 MB; the new combined app is a 1.5 GB Electron bundle per Implicator.ai.

Why it matters

Codex is no longer an independent product with its own distribution and roadmap. It is now a mode inside ChatGPT, sharing the same desktop surface with a general-purpose chat interface and the Work agent. OpenAI's Codex lead Andrew Ambrosino described the merger as "only the first" step toward unifying the experience across web, mobile, and desktop.

For teams using Cline or Aider in AI coding pipelines: both tools connect to OpenAI models via the API, not the desktop app, so API-based automation is unaffected. If your team used the standalone Codex desktop app for any local integrations or specific interface features, the update to the new ChatGPT desktop app is required. Codex gains inline diff editing, side-panel PR review, and multi-repo project support in the new app.

For Atlas users, August 9 is a hard cutoff. The intended replacements are the browser built into the ChatGPT desktop app and an updated Chrome sidebar extension. Workflows built around Atlas's standalone browser have roughly four weeks to migrate.

Context

The consolidation was signaled in March 2026 when OpenAI outlined plans to fold ChatGPT, Codex, and Atlas into a single desktop application. The July 9 launch also coincides with the general availability of GPT-5.6, which powers ChatGPT Work and Codex in the new app. Atlas launched in October 2025, giving it less than a year of life as a standalone product.

What to watch next

August 9 is the only hard date in play. Whether OpenAI extends that deadline under user pressure is the first signal to watch. Ambrosino's comment that the July 9 merger is "only the first" step means interface changes are still in motion; teams building Codex desktop automation should treat the current app as transitional rather than stable.

Sources