OpenAI pulled the full Codex experience into the ChatGPT app and, alongside it, previewed Sites: a Codex plugin that takes a prompt or a compatible existing project and turns it into a hosted, shareable website or app, no separate deploy pipeline required. It's the clearest sign yet that the "describe it and ship it" loop is collapsing into a single conversation.
What Sites Actually Is
Sites lets Codex "create, save, deploy, and inspect websites, web apps, and games hosted by OpenAI." You describe what you want in a thread, optionally calling the plugin explicitly with @Sites when a task should end in a deployment, and Codex builds the project, runs it for testing, deploys it, and hands back a production URL.
Crucially, this is framed as part of Codex, not a standalone consumer website builder. The scope runs from simple static pages to full-stack JavaScript and TypeScript apps—dashboards, planners, review workspaces, project boards, galleries, and lightweight internal tools that keep updating as the underlying information changes.
The Deploy Model Will Look Familiar
Publishing happens in two deliberate stages:
- Save a version. Codex builds the deployable site and ties that version to the source Git commit used for the build—a reviewable deployment candidate.
- Deploy a version. Codex publishes a saved version and reports the production URL when it succeeds. You only do this when you intend the chosen audience to reach the site.
Under the hood, Sites hosts projects that build Cloudflare Worker-compatible output as ES modules. New projects can start from a recommended site starter; existing projects need Codex to confirm the build produces compatible artifacts before a deploy. Persistent state is handled by D1-style databases and R2-style object storage—so a generated app can hold real user state and uploaded files, not just render static markup.
Built for Teams First
Sites is in preview for ChatGPT Business and Enterprise workspaces. Business workspaces have it on by default; Enterprise admins must enable it through role-based access control before members can use it. Today, sites are shared with anyone in your workspace via URL, giving teams a shared place to explore work, contribute input, and track decisions.
It launched next to two related pieces: role-specific Agent Plugins (with Corporate Finance, Marketing Strategy, Legal, and more coming) and annotations for refining results in place. OpenAI is also building toward an open ecosystem where partners ship their own plugins directly into Codex and ChatGPT.
The Partner Ecosystem Is the Tell
OpenAI named a Sites partner roster that reads like a who's-who of the web-building world: Wix, Base44, Replit, Lovable, Figma, Webflow, and Emergent. That's both a moat and a hedge—OpenAI gets distribution into established builders, and those builders get a Codex on-ramp rather than being routed around entirely.
Why It Matters for Web Developers
The honest read: Sites is preview-grade, workspace-gated, and governed by new ChatGPT Sites Terms—and every deploy URL should be treated as production from day one. It is not going to replace your real deployment pipeline for a customer-facing product.
But the shape is significant. A Cloudflare Worker-compatible build target with D1 and R2 storage means the artifact Codex produces is a real app, portable to infrastructure you already understand—not a walled-garden toy. For the internal-tools layer (onboarding hubs, dashboards, enablement libraries, scenario planners) that every team builds and nobody wants to staff, "ask Codex, get a URL, keep it updated" is a genuinely new default. The interesting question for the next year isn't whether this replaces front-end work; it's how much of the long tail of throwaway internal apps never gets hand-built again.