Claude Design for ChatGPT: Is There an Alternative for ChatGPT and Codex?
Written by
Published on
On this page
If you’ve actually used Claude Design, you know it isn’t a toy that spits out a nice-looking picture. It designs real websites and product UI, full app screens and user flows, straight from a prompt, while following your own design guidelines and design system. You can edit the result in place, restyle components, and iterate on whole interfaces. A lot of people drive it directly from Claude Code, Anthropic’s agentic coding tool. In practice it behaves less like a slide generator and more like an AI-native alternative to Figma for designing and shipping product UI.
Which is exactly why we keep hearing the same question from everyone who doesn’t live in Claude: “Is there a Claude Design for ChatGPT, or for Codex?” Most teams that want this aren’t in Claude Code at all. They’re in ChatGPT, and their engineers run Codex, OpenAI’s agentic coding tool and the closest counterpart to Claude Code. They want the same on-brand, design-system-aware output, in their stack.
Short answer: there’s no native Claude Design inside ChatGPT or Codex, and there won’t be. Two open-source projects, Doop and OpenDesign, now give Codex a Claude Design-style canvas, and we cover both below. But a design canvas doesn’t give you the file most business teams actually need: an editable PowerPoint deck. That’s what SlideSpeak adds, through its app in ChatGPT and its MCP server in Codex, Cursor, and Claude Code. Here’s how it fits together.
What Claude Design actually is
Claude Design is a design environment from Anthropic Labs built into Claude. Instead of generating a flat image, it designs in real code and gives you an open, editable layer, so the output looks and behaves like a designer built it rather than a diffusion model guessing at pixels. What it’s genuinely good at:
- Designing whole interfaces, not single screens. Websites, web apps, and mobile app UI, including multi-screen user flows.
- Following your design system. Give it your design guidelines, tokens, and components and it produces UI that respects them.
- Direct editing. You can modify layouts, components, and styling inside Claude Design rather than re-prompting from scratch every time.
- Code-native output. Because it designs in code, the work carries straight into a build, which is why so many people run it from Claude Code.
In other words, it’s closer to an AI-native Figma for product design than to a “make me a slide” tool. It’s free for Claude Pro and Max users, and it’s a real step forward.
But there’s a catch for everyone who isn’t all-in on Claude:
- It’s Claude-only. There is no Claude Design in ChatGPT and none in Codex. If your team and your agents live in the OpenAI ecosystem, it simply isn’t available to you.
- It’s built for UI and product design, not business documents. It’s superb at app and web interfaces. It is not built to hand you an editable
.pptxdeck, a one-pager, or an infographic your sales and marketing teams can open and present. - The design system lives in the session. The guidelines you feed it apply to that project. They don’t carry over to the rest of your tools automatically.
For a deeper walkthrough of using it for slides specifically, see How to Create Presentations with Claude Design.
Why there’s no Claude Design in ChatGPT or Codex
Claude Design is a proprietary Anthropic feature, so it will never ship inside ChatGPT or Codex. ChatGPT can write excellent content and Codex can write excellent code, but out of the box neither knows what your brand or design system looks like. Ask either for a deck or a landing page and you get a model’s best guess at fonts, colors, and spacing, which is exactly the off-brand output you then spend an hour fixing.
The fix depends on what you’re making. For product UI, you want a design canvas. For business decks, you want a tool that produces a real presentation from your template. ChatGPT and Codex both support Model Context Protocol (MCP) connectors or apps, which let them use external tools on demand.
The Claude Design alternative for presentations in ChatGPT and Codex: SlideSpeak
SlideSpeak covers the job Claude Design isn’t built for: business presentations your team can open and edit. There are two ways in, depending on where you work.
- In ChatGPT: the SlideSpeak app creates a deck from your prompt right in the chat. You then open it in SlideSpeak to edit it and export a PowerPoint file.
- In Codex, Cursor, Claude, and Claude Code: the SlideSpeak MCP server lets your agent generate a native PowerPoint file and hand you a download link.
To keep decks on brand, upload your branded template to SlideSpeak once and pass its ID through the MCP. Your layouts, colors, and fonts come from the template rather than from the model’s best guess.
Even if you use Claude Design, SlideSpeak still earns its place
This isn’t only for OpenAI teams. If you run Claude Design from Claude Code, SlideSpeak complements it rather than replacing it. Claude Design is where you design and build product UI. SlideSpeak is where you generate the decks Claude Design isn’t built for.
1. It uses far fewer tokens
When a model designs from scratch in code, it generates thousands of tokens of markup, styling, and layout for every asset. With SlideSpeak, the agent mostly orchestrates: it sends the content and the template, and SlideSpeak renders the file on its servers.
2. You get real, editable business files
Design tools output design and code. Most business workflows need an editable presentation. SlideSpeak produces native decks your team can open, tweak, and present, not a webpage you have to screenshot.
Claude Design vs. SlideSpeak: which do you need?
They overlap less than the search term implies. One is a place to design UI; the other is a way to produce on-brand presentations. Many teams will use both.
| Capability | Claude Design | SlideSpeak |
|---|---|---|
| Where it runs | Claude / Claude Code only | ChatGPT app, plus Codex, Cursor, Claude, and Claude Code through MCP |
| Primary job | Design & build app / web UI and flows | On-brand, editable presentations |
| Follows your brand | Yes, per session | Yes, through your branded template |
| Editable PowerPoint / .pptx export | No | Yes |
| Token efficiency at volume | Low (designs in code each time) | High (renders server-side) |
Open-source Claude Design alternatives that run on Codex: Doop and OpenDesign
If what you miss in Codex is the canvas itself, the place where an agent designs a screen and you watch it render and iterate, two open-source projects fill that gap. Neither is built around your PowerPoint template, which is why they pair well with SlideSpeak rather than replacing it.
Doop
Doop is a hosted, multiplayer canvas where humans and several agents design together in real time. Frames stream in live as the agent writes them, the agent reviews its own screenshots, and anything on the canvas can be exported to a live URL. It connects to Claude Code, Codex, and any MCP agent over streamable HTTP with OAuth, so agents act as you rather than through a shared API key. It’s open on GitHub as a single Docker container plus Postgres and free during beta. Doop is a strong fit if you want a team watching and commenting while agents work. It’s a canvas, though, not a deck generator, so pair it with SlideSpeak for presentations.
OpenDesign
OpenDesign takes the local route and is the closest thing to a drop-in Claude Design for Codex. It’s an Apache-2.0, local-first desktop app for macOS and Windows that uses the coding agent you already run as the design engine. Point it at Codex, Claude Code, Cursor, Gemini CLI, or a couple dozen other CLIs, bring your own key, and you get prototypes for web, desktop, and mobile, plus slides, images, and video, with HTML, PDF, PPTX, and MP4 export. It also runs as a stdio MCP server, so an agent in another repo can read your OpenDesign projects without opening the GUI. It ships with a large library of design systems and skills, which is great for getting a good-looking result fast. Its slide output is a rendered export rather than a deck built on your own template. For most Codex teams, OpenDesign is the right pick for UI and prototype work, with SlideSpeak handling business presentations.
| Claude Design | Doop | OpenDesign | SlideSpeak | |
|---|---|---|---|---|
| Works with Codex | No | Yes | Yes | Yes |
| Open source | No | Yes | Yes (Apache-2.0) | No |
| Where it runs | Hosted, Claude only | Hosted or self-hosted | Local desktop app, BYOK | ChatGPT app, MCP for any client |
| Primary job | App / web UI | Multiplayer design canvas | UI, prototypes, slides, media | On-brand presentations |
| Uses your own PowerPoint template | No | No | No | Yes |
| Editable .pptx | No | No | Yes (export) | Yes (native) |
Where do Figma MCP, Google Stitch, and DESIGN.md fit in?
If you’ve been researching AI design for ChatGPT or Codex, you’ve probably bumped into a few adjacent tools. They’re good, but most solve a different problem than on-brand presentations.
- Figma’s MCP server bridges design files and code for product UI/UX. It’s powerful, but it assumes you’re already designing in Figma. It isn’t built to spin up an on-brand deck or infographic from a prompt. Worth noting: Claude Design itself competes directly with Figma here, which is part of why it’s such a big deal.
- Google Stitch (from Google Labs, powered by Gemini) generates app and web interfaces from a prompt and exports to Figma. Again, that’s UI generation, not on-brand business documents.
- DESIGN.md is the same instinct in a file: a markdown spec that encodes a design system (colors, type scale, spacing, components) so coding agents like Cursor and Claude Code produce consistent UI. Browse the open collection at awesome-design-md. For slides, see DESIGN.md for Presentations.
The throughline: agents produce better work when you hand them your design system instead of making them guess. Claude Design does that for product UI inside Claude, and Doop or OpenDesign give you a comparable canvas on Codex. SlideSpeak does it for presentations, through your branded template.
How to set up Claude Design-style output in ChatGPT and Codex
- Upload your branded template to SlideSpeak. This gives every deck your layouts, colors, and fonts.
- Connect SlideSpeak where you work. Add the SlideSpeak app in ChatGPT, or the SlideSpeak MCP server in Codex, Cursor, Claude, or Claude Code.
- Prompt naturally, for example “Build a 6-slide investor update on Q3 revenue.”
- Get the editable file: a native presentation your team can refine and present, not an HTML page.
Frequently asked questions
Is there a Claude Design for ChatGPT?
Not natively. Claude Design is an Anthropic feature inside Claude and isn’t available in ChatGPT. To create presentations inside ChatGPT, use the SlideSpeak app. It builds the deck in the chat, and you can open it in SlideSpeak to edit it and export a PowerPoint file.
Is there a Claude Design for Codex?
Not from OpenAI. Codex is OpenAI’s agentic coding tool and has no built-in Claude Design. Two open-source options fill the gap: Doop, a hosted multiplayer canvas any MCP agent can join, and OpenDesign, a local desktop app that uses Codex as its design engine and is the closest one-to-one stand-in. For presentations, connect the SlideSpeak MCP server so Codex can generate an editable PowerPoint file from your branded template.
What is the best Claude Design alternative?
It depends on the job. For designing product UI and full app flows, Claude Design (or Figma) is the right tool, and if you’re on Codex, Doop and OpenDesign are the open-source equivalents, with OpenDesign the closer one-to-one match. For on-brand presentations across ChatGPT, Codex, Cursor, and Claude Code, SlideSpeak is the strongest option because it uses your own template and produces editable PowerPoint files.
Does SlideSpeak really use fewer tokens?
Yes. Designing from scratch in code consumes a large number of tokens on every request. SlideSpeak renders the deck on its own servers, so the model mostly orchestrates rather than writing markup.
Does it work with Claude and Claude Code too?
Yes. The SlideSpeak MCP is a standard MCP server, so it works with any MCP client, including Claude and Claude Code. If you already use Claude Design, SlideSpeak complements it by handling the editable presentations Claude Design isn’t built for.
The takeaway
Claude Design proved the appetite: people want AI that designs to a real system, not AI that guesses. But it lives in Claude, and most teams work in ChatGPT and Codex. Open-source canvases like Doop and OpenDesign bring the design surface to Codex, but they won’t hand you a deck built on your template. For that, use SlideSpeak: on-brand output, editable files, and far fewer tokens, in ChatGPT, Codex, Cursor, Claude, and Claude Code.
