• A 19 March 2026 Wall Street Journal report described an internal plan to combine ChatGPT, Codex and browsing. OpenAI confirmed the superapp direction on 31 March and launched a new ChatGPT desktop app globally for macOS and Windows on 9 July.
  • The released product brings Chat, Work, Codex and a built-in browser into one application, but it is not complete convergence. ChatGPT Classic remains available, Codex cannot be selected on the web or mobile, cloud and desktop Work conversations are separated at launch, and the built-in browser has its own state.

From an internal memo to a shipped desktop app

OpenAI introduced the standalone Codex app for macOS on 2 February and brought it to Windows on 4 March. The Journal then reported on 19 March that an internal memo from applications chief Fidji Simo described a desktop superapp intended to combine ChatGPT, Codex and a browser. That report established the plan, not a public release.

On 31 March, OpenAI publicly said it was building a unified AI superapp bringing together ChatGPT, Codex, browsing and broader agent capabilities. The status changed again on 9 July, when OpenAI released a new ChatGPT desktop app for macOS and Windows and described it as available globally across all plans, including Free.

The original article's future-tense framing is therefore obsolete. DALL-E was not named as a core pillar in either the March confirmation or the July desktop launch and should not be inserted into the product scope merely because image generation exists elsewhere in ChatGPT.

What the July release actually combines

The new application presents three principal modes. Chat remains the conversational surface. Work can operate on local files and permitted applications, use plugins and browse the web. Codex can work across repositories, produce diffs and pull requests, and run multiple coding tasks. A built-in browser supports Work and Codex with per-site permission choices.

For existing Codex app users, updating the app converts it into the new ChatGPT desktop app while retaining projects, settings and workflows. OpenAI also says it is beginning to sunset the standalone Atlas browser. These distribution choices concentrate product entry points, update paths and agent capabilities under the ChatGPT desktop brand.

One application does not mean one continuous system

The previous ChatGPT desktop app can remain installed as ChatGPT Classic. OpenAI says Classic will continue to receive model access, bug and security fixes, and existing enterprise support, but it has not published a final retirement date. Keeping both applications reduces immediate migration risk while demonstrating that desktop unification is still transitional.

Chat conversations sync between web and desktop, but cloud Work conversations do not appear in desktop Work at launch; desktop Work conversations and local-file context remain local. Codex is not a selectable mode on the web or mobile, although supported remote tasks can be monitored from mobile. The built-in browser also keeps state separate from Chrome unless a user chooses the Chrome extension path.

The control surface expands with the product

The relevant control surface is broader than a simpler menu. The app may access local files, other applications, repositories, websites, plugins and network resources. Users grant browser permissions by site, while Enterprise and Edu administrators receive workspace controls. Plan, account and workspace policy determine which capabilities are available.

That concentration can reduce switching, but it also makes permission design, local-versus-cloud handling, plugin governance, browser state, telemetry, network access and update integrity more important. A shared desktop shell does not erase those boundaries; it makes clear disclosure and auditable controls the condition for using the combined workflow safely.

Strategic meaning and evidence limits

OpenAI's product pages and help articles are primary evidence for release timing, stated features, migration behaviour and documented limitations. They do not independently prove higher productivity, lower switching costs, reliability at scale, successful migrations or adoption. Customer examples and company performance claims should be read as attributed claims, not measured outcomes.

Strategically, the launch makes ChatGPT the distribution layer for conversational, coding, browsing and computer-use workflows. The competitive question is no longer whether OpenAI intends to build a desktop superapp, but whether it can make these modes coherent without obscuring permissions, fragmenting state or forcing users through disruptive product retirements.

What to watch next

  • A dated retirement schedule and migration commitments for ChatGPT Classic and Atlas.
  • Whether cloud and desktop Work histories converge without weakening local-data guarantees.
  • Codex availability and continuity across desktop, web and mobile.
  • Enterprise and Edu controls for plugins, browser access, local files, network use and auditability.
  • Independent evidence on reliability, migration failures, user retention and productivity rather than company testimonials alone.

Sources