A Codex plugin bundles skills, MCP servers and hooks into one install: run /plugins in the CLI, or codex plugin add <plugin>@<marketplace>. The Codex plugin for Claude Code is something else: OpenAI's plugin that runs Codex inside Claude Code (October 2026).
Free for 3 seats · No credit card · One command signs in every agent on your machine
Sample data
Stack in the Zest app: how well your setup is wired, and what raises the score
USED BY ENGINEERING TEAMS AT
What is a Codex plugin?
A plugin packages a reusable workflow for ChatGPT and Codex. Plugins run in ChatGPT on the web, desktop and mobile, in Codex in the ChatGPT desktop app, and in the Codex CLI; the IDE extension doesn't support them. A plugin can carry:
Skills: SKILL.md instructions Codex picks when a request matches, or you run as $skill-name.
MCP servers, declared in the plugin's mcp.json, which connect Codex to outside tools.
Hooks: commands that run at fixed points in a session, such as SessionStart or PreToolUse, like Claude Code hooks.
Browser extensions a workflow needs, and links to already registered ChatGPT apps in an .app.json file.
Skill, plugin or AGENTS.md?
OpenAI's rule of thumb: use a skill for reusable instructions for a focused task, and a plugin when you want an installable package that combines instructions with connected services or other tools. AGENTS.md is not part of a plugin. It stays in the repository, where Codex reads it on every run, so keep it to the rules every task needs.
How to install and manage Codex plugins
In the CLI, /plugins opens the plugin browser. Install from a configured marketplace, press Space to turn an installed plugin on or off, and start a new session before you use its skills or tools. The same steps from a shell:
To turn a plugin off for one repository without uninstalling it, set enabled = false in that project's .codex/config.toml. Codex loads a project config only for trusted projects; the plugin browser saves your own choices in ~/.codex/config.toml.
codex plugin marketplace add owner/repo --ref main # add a Git marketplace
codex plugin marketplace upgrade # pull its newest versions
codex plugin add my-plugin@my-marketplace # install a plugin
codex plugin list # list plugins
codex plugin remove my-plugin@my-marketplace # remove it from config and cache
A plugin is a folder with a manifest. New packages put a plugin.json at the root, written to the Agent Plugins schema: a kebab-case name, a version and a description, plus author, homepage, repository, license and keywords. Settings only OpenAI reads go under extensions.com.openai: registered app links, the hooks file, and the interface ChatGPT shows, from displayName and category to the logo and defaultPrompt.
Older plugins keep .codex-plugin/plugin.json, which still works as a fallback, and OpenAI also accepts Claude-compatible manifests. Installed plugins sit in ~/.codex/plugins/cache/<marketplace>/<plugin>/<version>/, where a plugin from a local folder gets local as its version. Test a local plugin by installing it from the ChatGPT desktop app.
plugin.json
{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "my-plugin",
"version": "0.1.0",
"description": "Reusable skills and MCP servers",
"extensions": {
"com.openai": {
"hooks": "./hooks/hooks.json",
"interface": {
"displayName": "My Plugin",
"category": "Productivity",
"defaultPrompt": ["Use My Plugin to summarize new CRM notes."]
}
}
}
}
Hooks in a Codex plugin
Codex runs hooks by default. The plugin_hooks feature flag was removed in Codex CLI 0.134 (May 2026), so codex features enable plugin_hooks does nothing. A plugin's hooks live in hooks/hooks.json at its root, and each command gets PLUGIN_ROOT and PLUGIN_DATA (plus CLAUDE_PLUGIN_ROOT for Claude Code plugins).
Installing a plugin doesn't trust its hooks. Codex skips them until you review and trust the current definition in /hooks, and it records that trust against a hash of the hook. Events include SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, Stop and SessionEnd. To turn every hook off, set hooks = false under [features] in config.toml.
ChatGPT and Codex share one public plugin catalog, with tabs for plugins built by OpenAI, your workspace's plugins and your own. A plugin gets into the public catalog through OpenAI's plugin submission portal, and workspace admins can import a GitHub marketplace for everyone, synced daily.
Any Git repository can be a marketplace: list its plugins in .agents/plugins/marketplace.json. Each entry names a source (a local path, a Git repository or subfolder at a ref, or an npm package), an install policy (AVAILABLE, INSTALLED_BY_DEFAULT or NOT_AVAILABLE), an authentication policy and a category. Codex also reads a Claude Code-style .claude-plugin/marketplace.json, so one repository can serve both tools' plugin users.
OpenAI publishes a plugin for Claude Code, not for Codex: openai/codex-plugin-cc on GitHub, Apache-2.0, first released March 30, 2026 and at v1.0.6 since July 8. Its own description is “Use Codex from Claude Code to review code or delegate tasks.” It drives your local Codex CLI, so the work counts against your Codex usage limits, not your Claude plan. It needs a ChatGPT subscription (the free one works) or an OpenAI API key, and Node.js 18.18 or later.
/codex:review runs a read-only Codex review, and /codex:adversarial-review a steerable one that challenges the change.
/codex:rescue hands a task to Codex, and /codex:status, /codex:result and /codex:cancel manage the background jobs.
/codex:transfer turns the current Claude Code session into a persistent Codex thread.
Zest's Codex plugin shows the parts working together. Its manifest points at three things: a skills folder, a hooks file and a local MCP server that Codex starts over stdio. It ships 16 skills, such as login, sync and standup, and each tells Codex to call one tool on that server. Two hooks, on SessionStart and UserPromptSubmit, refresh the login.
It installs from its own Git marketplace (setup). Once you log in, it reads an allowlisted set of session files under ~/.codex, filters them for privacy on your machine and syncs each session's model, tokens, skills and MCP tools, which Zest joins to the pull requests they led to. More in Codex usage.
TRY IT ON YOUR TEAM
See what your team ships with AI.
Starter is free (3 seats, no credit card). Pro is $49 a month with 5 seats and Max is $149 a month with 10 seats — priced per workspace, not per engineer, with extra seats at $19 a month. See pricing
Run codex plugin remove <plugin>@<marketplace>, which removes it from your local config and cache, or press Space on it in /plugins to turn it off and keep it installed.
Do I need to enable plugin hooks in Codex?+
No. Hooks are on by default and the plugin_hooks flag was removed in Codex CLI 0.134. Review and trust a plugin's hooks in /hooks, or Codex skips them.
Can a Claude Code plugin run in Codex?+
Partly. Codex accepts Claude-compatible manifests, reads .claude-plugin/marketplace.json and sets CLAUDE_PLUGIN_ROOT for hooks, and skills share the SKILL.md format. Test a plugin's hooks and MCP servers in Codex before you rely on them.