OpenAI Adds Team Sharing for Custom Codex Plugins

OpenAI is adding plugin sharing to Codex so a plugin built for one person’s workflow can be distributed from inside the app. The important change is not the plugin directory itself; it is the access model around plugins that already exist.

The directory view shown in Codex is organized around three useful surfaces: “Curated by OpenAI,” “Shared with you,” and “Created by me.” That framing explains the product model. Some plugins come from OpenAI’s curated directory, some are built locally by a user or team, and some are received from teammates inside a workspace.

A custom plugin can be opened from the “Created by me” area of the Codex plugin directory, then shared from its details page. The example is First Week Quest, an onboarding plugin that creates a first-week path for a new teammate joining a repo, project, or team area. Its visible description says it turns a repo, project, or feature area into “what to read, what to run, what to ask, and the first small task that proves the teammate is oriented.” The page also shows default prompts for building an onboarding quest, making a first-week plan, and creating a starter task. Its information panel identifies the category as Local, Engineering, and the developer as Corey Ching.

From the plugin page, the creator can click “Share” and choose how the plugin is distributed. The share modal includes an “Add people” field, an access section, owner information, “Stop sharing,” and “Copy link.” The access choices shown are “Only those invited” and “Anyone at workspace with the link.” Saving the workspace-link option makes the plugin available to anyone in the workspace who has the link; the creator can then copy that link and send it to the team.

That is the core workflow: a teammate builds a useful Codex plugin, sets the appropriate access level, and shares a link from within Codex. The access choices are doing the governance work here. A plugin can be kept to named invitees, or it can be made available more broadly to workspace members who receive the link.

Shared plugins do not require a separate discovery path. Codex adds a “Shared with you” tab in the plugin directory, where users can see plugins their teammates have made available to them.

The example shown there is Finalize Code, a Productivity plugin marked as shared by Nick Baumann. Its details page describes it as a plugin for the “last mile of software work”: preflight checks, review passes, verification summaries, and release handoff notes. The information panel identifies it as a workspace-directory plugin in the Productivity category, developed by Codex Demo. The visible included skills are code-review-pass, preflight-checklist, and release-ready-handoff. An install dialog lists the plugin’s capabilities as Review, Write, and Summarize.

The stated use case is pull-request preparation: the plugin can be used for validation, code refactoring, and making sure a PR is in a strong state before it is sent for review. That example gives the sharing feature its practical meaning. A team can turn a recurring internal practice — how to check, package, and hand off code — into a Codex plugin that another teammate can find and install from the same plugin area they already use.

OpenAI is also adding share URLs for curated plugin pages. This is separate from sharing a teammate-built plugin into a workspace. The purpose is direct navigation: a user can send the exact plugin page instead of asking someone else to search the directory.

The example is Slack. The Slack plugin page in Codex is shown with the description “Read and manage Slack” and a prompt for summarizing unread activity, drafting replies, or preparing updates. The page lists a Slack App for sending messages and fetching data, a Slack Skill for summarizing threads and drafting posts, and skills for channel summarization, daily digest, notification triage, outgoing message drafting, and reply drafting. Its category is shown as Apps, Search, Productivity.

The shared URL uses a chatgpt.com/plugins/share/... link. When the link is pasted into Chrome, the browser prompts the user to open Codex.app. The screen says ChatGPT is trying to open Codex automatically and shows “Opening plugin: Slack.” The URL is therefore meant to deep link from the browser into the corresponding plugin page in Codex.

The workflows a team builds in Codex do not have to stay on one machine. The controls shown are simple but material: a creator can share with invited users or anyone in the workspace with the link; recipients can find shared plugins in “Shared with you”; curated plugins can be opened through direct share URLs.

“The workflows you build for your team don't have to stay on your machine,” the speaker says. “If the plugin helps one teammate, share it. If someone shares one with you, it shows up right where you need it.”

Onboarding paths, code-finalization checks, Slack triage, and other recurring workflows are presented as shareable Codex assets: visible in the directory, installable by teammates, and linked directly when discovery through search would add unnecessary friction.