ChatGPT Enterprise Workspaces Can Now Share Codex Plugins by Default

OpenAI has quietly flipped an important default for ChatGPT Enterprise customers using Codex. Plugin sharing, previously something you had to request activation for through your OpenAI account contact, is now switched on by default for eligible Enterprise workspaces. If your team uses Codex, this changes how you can distribute internal tools and workflows starting today.

What Changed, Exactly

Until now, Enterprise users who wanted to share locally built plugins with colleagues had to ask OpenAI to enable the feature. ChatGPT Edu workspaces already had it on by default, but Enterprise did not. That gap is now closed.

With sharing enabled by default, any Codex user in an eligible Enterprise workspace can publish a local plugin to a shared workspace directory. Teammates can then find it under “Shared with you” in the Codex plugin directory and install it themselves. No IT ticket, no waiting on OpenAI.

The sharing stays inside your organisation. Shared plugins are not published to a public directory, and anyone outside your workspace cannot access them.

What Codex Plugins Actually Are

If you have not spent time with Codex plugins yet, a quick primer helps here.

A plugin is a self-contained bundle that packages together skills (reusable task definitions), app integrations, MCP server configurations, and lifecycle hooks into a single installable unit. The idea is that instead of every team member manually setting up the same Codex environment, one person builds it once, packages it as a plugin, and shares it. Everyone else installs it in a few clicks.

Each plugin has a manifest at .codex-plugin/plugin.json and can include a skills/ directory, an .app.json file pointing at connected apps or connectors, an .mcp.json file for MCP server config, and assets for how the plugin appears in the directory.

The plugin directory itself groups content into three sections:

• Curated by OpenAI — highlighted plugins available to all Codex users
• Shared with you — plugins shared by workspace members
• Created by you — plugins you have built or added yourself

How Sharing Works in Practice

To share a plugin you have built, you open the Codex app, go to Plugins, find the plugin under “Created by you,” open its details page, and select “Share.” From there you can add specific workspace members, add workspace groups, or copy a share link. You choose who gets access.

Groups are the right tool when an entire team or role should share the same plugin. If you want broader repo or CLI distribution, a marketplace setup makes more sense. Workspace sharing is specifically for getting teammates to install a plugin through the Codex app.

Recipients find shared plugins under “Shared with you” in the directory and install from there.

What This Means for Enterprise Admins

The default-on change shifts the administrative posture from opt-in to opt-out. If your organisation needs to restrict plugin sharing, you now need to actively disable it rather than simply never enabling it.

The control lives in requirements.toml. Admins can set plugin_sharing = false in cloud-managed requirements to turn off workspace sharing for locally built plugins. This can be deployed via MDM (using com.openai.codex:requirements_toml_base64 on macOS) or through the Codex Policies page, which lets admins push enforced configuration to specific groups without distributing device-level files first.

Codex applies requirements layers in a defined order: cloud-managed requirements take priority, then MDM-managed preferences, then system-level requirements.toml files. So a cloud-managed plugin_sharing = false will override anything set at the device level.

Beyond the sharing toggle, admins and owners have further controls available. You can disable specific plugins by disabling the corresponding app in Workspace settings under Apps. Enterprise and Edu admins can also use RBAC to control which users get access to a given app or plugin. One current limitation: app controls apply across all surfaces at once, including ChatGPT web, mobile, and Codex. You cannot enable a plugin in Codex while disabling it in the ChatGPT mobile app.

The Broader Picture

This change fits into a deliberate effort to make Codex a practical team tool rather than something only developers configure individually. OpenAI has noted that roughly 20% of Codex’s weekly users now come from non-engineering roles, including analysts, marketers, and operations teams, and that group is growing faster than the traditional developer base.

Plugins are a direct response to that shift. When someone on the finance team builds a Codex workflow that queries internal data and formats a report, packaging it as a plugin means everyone with the same need can use the same setup. Before this change, sharing that plugin across an Enterprise workspace required a manual handshake with OpenAI. Now it just works.

For teams that have been building internal Codex tools and emailing colleagues instructions on how to replicate their setup, this is a meaningful quality-of-life improvement. The infrastructure was already there. The default finally matches how people actually want to work.