OpenAI just turned ChatGPT into a platform — and the ChatGPT Apps SDK is how developers ship to it. The company stopped treating ChatGPT as a chatbot and started treating it as an operating system.
The 2026 reform — a "super app" redesign reportedly codenamed Aria — folds AI agents, the Codex coding tool, image generation, and a growing catalog of third-party apps directly into the main ChatGPT interface. For its ~900 million weekly users, the chat box is becoming a launcher: you ask for a playlist and Spotify renders inside the conversation, you ask for a place to stay and Booking.com shows up as an interactive card, you sketch an idea and Canva opens inline.
The thing that makes this real for developers is the Apps SDK — and the most important detail is that it is built on the Model Context Protocol (MCP). OpenAI did not invent a proprietary plugin format this time. It standardized on the same open protocol the rest of the industry is converging on, and added a UI layer on top.
The short answer: ChatGPT is now a distribution platform, and the Apps SDK is how you ship to it. If you build software, "being inside ChatGPT" is about to be a channel you have to think about — the way "being in the App Store" became one in 2008.
TL;DR
- OpenAI reworked ChatGPT into a super app: agents, Codex, image generation, and third-party apps live inside the main interface, reaching ~900M weekly users.
- The Apps SDK is how developers build those apps, and it is built on MCP (Model Context Protocol) — an open standard, not a closed plugin format.
- An app is an MCP server that lists tools, executes tool calls, and returns widgets — web UI components ChatGPT renders inline in the conversation via a sandboxed iframe.
- The UI talks to ChatGPT over a JSON-RPC bridge (postMessage) and can request inline, picture-in-picture, or fullscreen display via
window.openai.requestDisplayMode. - Launch partners included Booking.com, Canva, Coursera, Figma, Expedia, Spotify, and Zillow.
- Apps are available to logged-in users outside the EEA, Switzerland, and the UK on Free, Go, Plus, and Pro.
- Developers submit apps through a submission portal; approved ones land in the App Directory to be discovered and shared.
- Because it is MCP-based, the same app can run in other MCP Apps–compatible hosts — you build the UI once.
What the "Super App" Reform Actually Is
For years, ChatGPT was a text box with a model behind it. The reform changes the shape of the product: the conversation becomes a surface where different capabilities and apps render directly.
Concretely, the redesigned ChatGPT pulls several things into one place:
- Agents that can take multi-step actions on your behalf
- Codex, the coding tool, available in-line for engineering work
- Image generation as a first-class capability, not a mode you switch to
- Third-party apps — Spotify, Canva, Figma, Booking.com and more — that render interactive UI inside the chat
The strategic move is obvious once you name it: OpenAI wants ChatGPT to be the place you start a task, not the place you go to get text you then paste elsewhere. That is the definition of a super app — one interface that handles many jobs — and it is the same playbook WeChat ran in China a decade ago.
Why this is not 'plugins, again'
The 2023 plugin era failed partly because it was a closed, bespoke format with weak UI and weak discovery. The 2026 reform fixes all three: it is built on the open MCP standard, apps render rich inline UI, and there is a real App Directory for discovery. Same ambition, much better foundation.
Why Building on MCP Is the Real Story
The single most important technical decision in this release is that the Apps SDK builds on the Model Context Protocol.
MCP is the open standard for connecting models to external tools and data. If you have already built an MCP server — for Claude, for an internal agent, for anything — you are most of the way to a ChatGPT app. And because ChatGPT implements the same iframe-and-bridge model that the broader MCP Apps effort defines, a UI you build for ChatGPT can run in other MCP Apps–compatible hosts too.
That is a genuinely different bet than a proprietary plugin store. It means:
- You build once. The tool contract and UI bridge are standardized.
- You are not fully locked in. MCP is an open protocol with multiple hosts.
- The ecosystem compounds. Every MCP investment across the industry now points at ChatGPT distribution too.
If you are new to MCP, start with my guide to building an MCP server and the walkthrough on deploying an MCP server on Cloudflare Workers — the same server you build there is the foundation for a ChatGPT app.
How the ChatGPT Apps SDK Works
An app in ChatGPT has two halves: an MCP server (the logic) and an optional UI component (the interface). This is the core of the ChatGPT Apps SDK — here is the anatomy.
At minimum, your MCP server implements three capabilities:
The UI half runs inside a sandboxed iframe and communicates with ChatGPT over a standard bridge — ui/* JSON-RPC messages over postMessage. Your component can read state, call your tools, and negotiate how it is displayed:
// Inside your app's UI bundle, running in the ChatGPT iframe.
// Ask ChatGPT to present the widget larger for an interactive task.
await window.openai.requestDisplayMode({ mode: 'fullscreen' }); // or 'inline' | 'pip'
// Call one of your MCP server's tools from the UI and render the result.
const result = await window.openai.callTool('search_listings', {
location: 'Lisbon',
checkIn: '2026-08-01'
});
renderListings(result.structuredContent);
The bridge is the whole trick
Your UI never talks to the network directly for app logic — it talks to ChatGPT over the bridge, and ChatGPT relays to your MCP server. That is what keeps apps sandboxed, consistent, and portable across MCP Apps hosts. Build the UI once; the host handles presentation.
The display modes
window.openai.requestDisplayMode lets a widget negotiate how it appears:
Building an App: The Shape of the Work
You do not need to learn a new framework. If you can write an MCP server and a small web UI, you can build a ChatGPT app.
Availability caveat
At launch, apps in ChatGPT were available to logged-in users outside the EEA, Switzerland, and the UK, on Free, Go, Plus, and Pro. If your audience is primarily European, factor that rollout gap into any launch plan — the distribution surface is not yet global.
The Opportunity — and the Risk
This is a real distribution channel, but building on someone else's platform always cuts both ways.
For brands, the mental shift is the same one search and app stores forced: users increasingly start inside an aggregator. If people begin their travel, design, or media tasks in ChatGPT, being absent from the App Directory is a discovery problem — the same way being absent from Google once was.
Readiness Checklist
The Bigger Picture: This Pairs With GPT-5.6
The super app reform did not ship in a vacuum. It arrived in the same window as the GPT-5.6 model family, and the two reinforce each other. A more capable, more efficient model makes agentic, multi-app workflows economically viable; a super app surface gives that model somewhere to do things. Cheaper tokens plus a distribution platform is how "AI agent that gets real work done" stops being a demo.
If you are building agents that call many tools, the same discipline I wrote about in the agentic AI enterprise security model applies: capability without governance is a liability, and apps inside ChatGPT are no exception.
FAQ
Final Take
The ChatGPT super app reform is OpenAI's clearest bet yet that the interface, not just the model, is the product.
By building the Apps SDK on MCP, OpenAI turned "being inside ChatGPT" into a channel you can reach with mostly standard, reusable work — and turned ChatGPT into a distribution platform sitting in front of ~900 million weekly users. That is a genuine opportunity and a genuine dependency at the same time.
The right posture is pragmatic: reuse your MCP investment, ship an app as a channel, design for portability, and keep your product's center of gravity your own. Do that, and the super app is upside without the classic platform trap.
Next, read the GPT-5.6 complete guide that shipped alongside it, and — if you are building the backend — my MCP server guide.
Sources
- OpenAI: Introducing apps in ChatGPT and the new Apps SDK
- OpenAI Developers: Apps SDK
- OpenAI Developers: Build your ChatGPT UI
- OpenAI: Developers can now submit apps to ChatGPT
- Model Context Protocol Blog: MCP Apps — bringing UI capabilities to MCP clients
Explore more: AI Coding Agents & Developer Experience
Originally published at umesh-malik.com
Keep reading on umesh-malik.com:
Top comments (0)