On June 2, 2026, OpenAI shipped the biggest non-model Codex update of the year. Codex plugins are now expanding far beyond developer tools: six new role-specific plugins (sales, design, analytics, banking, equity research, creative production), a preview of Codex Sites that turns Codex into a hosted app builder, and Annotations that let you point at a paragraph or a spreadsheet cell and tell Codex what to change. None of these will replace Claude Code, Cursor, or your favorite IDE. All of them change who Codex is for, and that matters if you ship production apps for a living.
This post takes the June 2 update apart, lines it up against the rest of the AI coding agent market, and shows where it lands if your daily loop already involves Claude Code, Cursor, or Codex calling out to other tools via MCP.
Quick Answer
- Codex plugins are installable bundles that package skills, app integrations, and MCP server configurations together. OpenAI launched the plugin format originally with Codex v0.117.0 in March 2026 and expanded it on June 2, 2026 with six role-specific plugins for sales, creative production, product design, data analytics, public equity investing, and investment banking.
- Codex now connects to 62 popular apps and ships 110 skills out of the box.
- A new Sites preview lets Codex create and host interactive websites and apps that you can share with your team via URL. Sites rolls out to ChatGPT Business and Enterprise first.
- Annotations let you select a specific section of a doc, slide, or spreadsheet and tell Codex exactly what to change inside it.
- The June 2 update is targeted at non-developers, who now make up roughly 20% of Codex's 5M weekly users and are growing more than 3x as fast as the developer cohort.
- If you build production apps, Codex plugins matter mostly because Codex is becoming a general work agent. The right move is to drive an AI app builder like Totalum from inside Codex via MCP and let Codex orchestrate while Totalum produces the real Next.js project.
What changed on June 2, 2026
OpenAI's announcement was titled "Codex for every role, tool, and workflow." Under that umbrella, three things shipped:
- Six new role-specific plugins, designed to make Codex useful for people who do not write code for a living. Each plugin installs with a single click and instantly gives Codex a curated set of tools, prompts, and integrations for that role.
- Codex Sites (preview). With Sites, Codex can turn an idea or a working session into a hosted, interactive site, dashboard, or web app that you can share with a URL. Sites are hosted by OpenAI and managed from the Codex app sidebar.
- Annotations. Instead of asking Codex to "rewrite the doc," you can select the exact paragraph, slide, table cell, or chart you want changed and write a comment in place. Codex applies the change scoped to that selection.
OpenAI also published official documentation for the Plugins and Sites features. The plugin manifest is a .codex-plugin/plugin.json file that bundles one or more skills, app integrations, and MCP server configurations into a single installable.
The Sites preview rolls out to ChatGPT Business and Enterprise plans first. Business workspaces get Sites enabled by default. Enterprise admins can enable Sites by role via the existing RBAC controls. Both plans can manage environment variables and secrets for hosted sites from the Codex sidebar.
The six role-specific plugins
These are the role plugins OpenAI shipped on June 2, with a one-line summary of what each gives Codex:
| Role plugin | What Codex can do once installed |
|---|---|
| Sales | Draft outreach, write call notes, pull CRM context, generate proposals |
| Product design | Generate component variants, write design briefs, run heuristic reviews |
| Data analytics | Wrangle CSVs, draft SQL, build summary dashboards, explain findings |
| Creative production | Write campaign briefs, generate copy variants, storyboard assets |
| Public equity investing | Pull filings, summarize 10-Ks, build comp tables, draft theses |
| Investment banking | Build pitch decks, generate models from term sheets, format memos |
Each role plugin installs to a workspace and surfaces a curated set of slash commands. The plugins call out to the 62 integrated apps (Notion, Slack, Salesforce, Workday, Bloomberg, and so on) and use the 110 packaged skills under the hood.
The architecture is identical to the developer-facing plugins that shipped in March (Composio, Context7, Superpowers, the Claude Code bridge, the React Native plugin from Callstack, and the rest of the long tail). The role plugins are just curated bundles for non-developer workflows, plus the marketing push to introduce them.
How Codex plugins actually work
A Codex plugin is an installable bundle. You can publish one yourself, install one from the community list (the GitHub awesome-codex-plugins repo currently tracks 12 official plus 15 community plugins), or get one from a partner.
Under the hood:
- Skills: focused capabilities (for example, "summarize a 10-K filing" or "generate a Tailwind component"). Skills are the smallest unit of plugin functionality.
- App integrations: connectors to external SaaS apps. The plugin manifest declares which apps the plugin needs.
- MCP server configurations: the plugin can wire up one or more MCP servers so that Codex can call out to them inside a session. This is the part that matters for app builders, because it means a plugin can hand Codex new capabilities like database access, image generation, or driving an AI app builder.
- Permissions: scoped per plugin. Codex prompts you to approve the apps and MCP servers a plugin needs the first time you install it.
The plugin manifest is a single JSON file. You can read OpenAI's reference at developers.openai.com/codex/plugins. The community page at github.com/openai/codex/discussions/16073 lists currently verified plugins.
Codex Sites: OpenAI just joined the AI app builder fight
The most disruptive piece of the June 2 update is Sites. Until now, the conversation about AI app builders centered on Lovable, Bolt, Replit, v0, Base44, and Totalum. Each of those tools generates real web apps from a prompt. With Sites, OpenAI is shipping the same shape of feature inside Codex.
There are caveats. Sites is preview. Sites is hosted by OpenAI, which means you do not own the code that runs there in the same way you would with a builder that gives you a real Next.js project to download. Sites is Business and Enterprise plan only at launch. And Codex Sites does not (as of this writing) include built-in database, authentication, payments, or hosting on your own domain.
That last gap matters. AI app builders like Lovable, Bolt, Replit, and Totalum are converging on the same checklist for "real production app": database, REST API, authentication, payments, hosting, custom domain, code download. The Totalum landing page lays this out in the on-site comparison table under "Why choose Totalum". Codex Sites today covers maybe two of those, and gates the rest behind workspace plans.
So Sites is a credible play, but it is positioned closer to Claude Artifacts and OpenAI Canvas (in-app interactive surfaces) than to a real production builder. The thing to watch is whether OpenAI extends Sites with native database, auth, and payments. Until that happens, Sites is a fast way to share a hosted demo from Codex, not a way to ship a SaaS.
Annotations: precise edits, not full rewrites
Annotations are the smallest of the three June 2 features and the easiest to underestimate. The pattern is borrowed from word processors: highlight a span, write a comment, get an in-place edit. Inside Codex, that span can be a paragraph in a doc, a cell in a spreadsheet, a chart on a slide, or a section of generated code.
The practical effect is that Codex is no longer just a chat-style agent that owns the whole document. You can hand it a 40-page memo and say "the 3rd paragraph of section 4 needs to reflect the new ARR number from cell B12" without rewriting the rest. That is a real productivity unlock for people who used to copy-paste the section back into chat.
For developers, this maps to the way Cursor's inline edit mode and Claude Code's targeted-edit prompts already work. Codex is closing a known gap.
Codex plugins vs Claude Skills vs Cursor plugins
The plugin / skill marketplace race is one of the most important storylines of the 2026 AI coding agent year. Codex is not the only player here, and the architectures differ in ways that matter.
| Capability | Codex Plugins (OpenAI) | Claude Skills (Anthropic) | Cursor plugins (community) |
|---|---|---|---|
| Manifest format | .codex-plugin/plugin.json |
skill.json |
.cursorrules + extensions |
| Installable bundle | Yes, packages skills + apps + MCP | Yes, individual skills | No formal bundle format |
| App integrations included | 62 apps, 110 skills (June 2) | Open via MCP | Open via MCP |
| MCP support | Native, declared in manifest | Native | Native |
| Marketplace | Awesome list + Codex app store | Skills marketplace | None official, community curated |
| Role-specific bundles | Yes, six on June 2 | Partial | No |
| Non-developer focus | Strong | Mixed | Developer-only |
The directions are similar but the centers of gravity differ. Anthropic's Claude Skills marketplace plays to a developer-first audience that wants composable, single-purpose units. Cursor leans on its community for plugins and rules. OpenAI is reaching past developers entirely, packaging Codex as a generalist work agent that knows about sales, design, and equity research as well as it knows TypeScript.
You can tell where the strategy is headed by reading the numbers OpenAI published: 5M weekly Codex users, 20% non-developers, 3x faster growth than developers. The June 2 plugin update is not aimed at the 80%. It is aimed at the 20%, where the curve is.
What this means if you ship production apps
If you build production apps for clients or for your own SaaS, the June 2 Codex update is not a "drop your stack" event. Codex Sites is preview, plan-gated, and lacks database / auth / payments / custom domain. Codex plugins are useful, but most of the role plugins are not aimed at code.
The real signal is that OpenAI just doubled down on Codex as a general-purpose work agent that can call out to anything via MCP. If you already use Codex on Windows or Codex Computer Use, you can now bundle and share your favorite setup as a plugin, and you can route Codex into specialized tools by MCP without writing glue code each time.
For app builders specifically, this means two things. First, Codex Sites raises the floor on what counts as "good enough" for sharing a demo. If you ship demos via Codex Sites and decide later you need real auth, real database, real custom domain, you have to migrate. Second, Codex's MCP support keeps getting deeper, which means an MCP-native app builder is now the cleanest way to let Codex spin up and maintain real production projects on your behalf.
Driving an AI app builder from Codex with Totalum
Here is the pattern that pays off in a 2026 Codex workflow. Totalum is its own AI app builder. It produces real Next.js projects with built-in database, REST API, authentication, payments, file storage, custom domain, and one-click hosting. You own the code, you download it whenever you want, and the data lives in the EU.
The key piece for Codex users is that Totalum is the first AI app builder usable via API and MCP. So instead of asking Codex to write a Next.js app from scratch (and then handling auth, payments, deploys yourself), you can have Codex drive Totalum directly through MCP:
- You give Codex a goal, for example, "build a client portal with auth, a dashboard, and Stripe-style payments."
- Codex calls Totalum via MCP. Totalum creates the project, scaffolds the database, sets up auth and payments, and assigns a default hosting URL.
- Codex iterates by calling Totalum's API: edit a screen, add a table, ship a feature.
- You get a real, downloadable Next.js project at the end. The hosting, database, auth, and payments are already wired up.
This is a different shape from "Codex Sites for sharing demos." It produces a real app you own. It is also a different shape from raw code generation in your IDE, because Totalum handles all the runtime concerns that take weeks to glue together by hand.
If you build apps for clients, this changes the economics of an engagement. If you ship a SaaS, this changes the iteration cycle from days to hours. And if you wrote a Codex plugin to capture your favorite workflow, you can bundle Totalum as the MCP server and ship the whole loop to your team.
For more on the agent + builder pattern, see Claude Code MCP tutorial, the best MCP servers in 2026, and our reactive coverage of Project Polaris from Microsoft Build 2026, which signals the same shift inside GitHub Copilot.
FAQ
When did Codex plugins launch?
The plugin format launched with Codex v0.117.0 in March 2026. On June 2, 2026, OpenAI added six role-specific plugins for sales, creative production, product design, data analytics, public equity investing, and investment banking, plus the Sites preview and the Annotations feature, under the umbrella "Codex for every role, tool, and workflow."
What is the difference between a Codex skill and a Codex plugin?
A skill is a single, focused capability (for example, "summarize a 10-K"). A plugin is an installable bundle that packages one or more skills, app integrations (Notion, Slack, Salesforce, and so on), and MCP server configurations together. Codex currently includes 110 skills out of the box; plugins compose those skills into role-specific or workflow-specific bundles.
What is Codex Sites and is it generally available?
Codex Sites is a preview feature, announced on June 2, 2026, that lets Codex create and host interactive websites and apps you can share with your workspace via URL. Sites is rolling out to ChatGPT Business workspaces by default and to ChatGPT Enterprise workspaces by role through RBAC. It is not generally available outside Business and Enterprise plans at launch.
Are Codex plugins free or paid?
The plugin format is part of the Codex app, which is included in Codex subscriptions. The plugins themselves can be free (the community list, the official six role plugins) or paid (some partner-published plugins, depending on the partner's pricing). MCP servers and app integrations a plugin uses may have their own billing.
Does Totalum work with Codex plugins?
Yes. Totalum exposes a public REST API and an MCP server, so you can wire Totalum into a Codex plugin manifest and have Codex create and maintain real Next.js projects through Totalum. Connect your Codex install at totalum.app/api-and-mcp.
Should I switch from Cursor or Claude Code to Codex because of plugins?
Probably not, and not yet. Cursor's IDE integration and Claude Code's terminal-first agent loop still beat Codex on dedicated developer workflows. The June 2 Codex update is aimed at non-developers and at people who want one agent across sales, design, and analytics in addition to code. If your day is mostly code, stay where you are. If your day is mixed, Codex plugins are now worth a serious look.
Ready to build with Totalum?
If you already use Codex (or Claude Code, or Cursor, or ChatGPT) and want your agent to ship real production apps with built-in auth, database, payments, and hosting, connect it to Totalum via MCP. The agent stays your driver. Totalum produces the project.
Start free at totalum.app or read the API and MCP guide to wire Codex up in five minutes.