Skip to content
AI Primer
release

OpenAI introduces Codex Sites for shareable interactive apps

OpenAI rolled out Codex Sites so plans, docs, dashboards, and creative concepts can become interactive apps with shareable URLs. The launch also added role-specific plugins, so teams can use the same workspace for thumbnail pulls, transcription, and other nontechnical tasks.

5 min read
OpenAI introduces Codex Sites for shareable interactive apps
OpenAI introduces Codex Sites for shareable interactive apps

TL;DR

You can browse the Sites guide, skim the plugin docs, and see OpenAI pitch Sites in the announcement as a way to turn launch materials into living hubs, dashboards, and planners. The buried detail lives in the developer docs: every deployment URL is production by default. The other tell is in the Help Center FAQ, which treats Sites as a workspace plugin with admin controls, not a public no-code toy.

Sites

OpenAI is framing Sites as a canvas inside Codex, not a separate website builder. In the launch post, the company says Codex can turn ideas, analyses, and plans into dashboards, planners, review workspaces, project boards, galleries, and lightweight tools that anyone in the same workspace can open by URL.

The examples split cleanly into two buckets:

The Sites documentation pushes the scope a little further than the launch copy. It says Sites can create, save, deploy, and inspect websites, web apps, and games hosted by OpenAI, and the internal-apps guide says the range runs from static pages to full-stack JavaScript or TypeScript apps.

Role-specific plugins

The plugin side of this launch is broad enough to matter on its own. OpenAI says the six new role packs ship with bundled apps, skills, instructions, and workflows, so Codex starts with the tools and prompts for a job instead of a blank chat.

According to the official launch post, the six plugins are:

  1. Data analytics: Snowflake, Databricks Genie, Hex, Tableau
  2. Creative production: Figma, Canva, Shutterstock, Picsart, fal
  3. Sales: Salesforce, HubSpot, Slack, Outreach, Clay, Rox, Actively
  4. Product design: prototype from a live URL, audit user flows, carry work into Figma and Canva
  5. Public equity investing: Moody's, Daloopa, Datasite, FactSet, LSEG, S&P, PitchBook, Hebbia
  6. Investment banking: research, comps, diligence, and client-ready materials

The plugin docs make the packaging more explicit: plugins can combine skills, app connections, and MCP servers into reusable workflows. That turns Sites itself into a plugin too, which is a neat tell about how OpenAI wants this product to scale.

Nontechnical workflows

The creative angle here is that Codex is starting to absorb jobs that used to bounce between chat, docs, file storage, and specialized SaaS tools. OpenAI says more than 5 million people use Codex weekly, and about 20% are non-developers growing more than 3x faster than developers, in the launch post.

The user reports in the evidence pool are much more specific than the launch copy:

That is the real texture of this update. The headline feature is Sites, but the stickier shift is Codex behaving more like a role-aware work surface that can grab the right tool on its own.

Access and deployment

The admin and hosting details are more opinionated than the marketing copy suggests. The Help Center FAQ says ChatGPT Sites is available in preview only for eligible Business and Enterprise workspaces, Business has it enabled by default, and Enterprise exposes it as an Early Access toggle.

The same FAQ says Sites created in Codex are workspace-internal apps with Sign in with ChatGPT access, admins and owners can disable the Sites toggle or take down an existing site, and admins have default access to all sites created by members. The Sites developer guide adds one more important constraint: every deployment URL is a production deployment, so if a team wants a reviewable draft, Codex has to save a version without deploying it.

That makes Sites feel less like lightweight publishing and more like managed internal hosting with guardrails, permissions, and a very fast path from prompt to live URL.

Further reading

Discussion across the web

Where this story is being discussed, in original context.

On X· 2 threads
Sites2 posts
Nontechnical workflows3 posts
Share on X