How do I install a Codex plugin?

Open the Codex CLI and run /plugins to browse the Plugin Directory. Pick a plugin from the curated list, shared list, or your own creations, and it installs into ~/.codex/. To invoke a plugin in a prompt, use the @ symbol followed by the plugin or skill name. To disable a plugin without uninstalling, set enabled = false under its section in ~/.codex/config.toml.

What is the difference between a Codex plugin and a Codex skill?

A skill is a single instruction file (SKILL.md) that teaches Codex how to handle one type of task. A plugin is a package that can bundle multiple skills together with app connectors and MCP servers. Skills are atomic, plugins are composable. A plugin like Firecrawl can ship an MCP server plus several skills under one install, while a standalone skill like grill-me handles exactly one workflow.

Are Codex plugins free?

Most community plugins and the curated plugins from OpenAI are free and open source. Plugins that connect to paid services (Firecrawl, Composio, Linear, Context7 Pro) require an account or API key for the underlying service, but the plugin itself is free to install. Free tiers on most of these services cover meaningful usage before any paid plan is needed.

What is the Firecrawl Codex plugin used for?

The Firecrawl Codex plugin gives Codex live web context. It bundles search, scraping, crawling, URL mapping, and live browser interaction into one install, with JavaScript rendering handled automatically. Codex's built-in web search queries a cached index by default. Firecrawl replaces that with real-time results and clean markdown output, so Codex stops hallucinating answers about current documentation, pricing, or APIs.

What is Composio for Codex?

Composio is a managed integration layer that lets Codex call out to over 1,000 SaaS apps (Gmail, HubSpot, Salesforce, Notion, Slack, Stripe, and more) without writing OAuth flows or maintaining tokens. It handles authentication, rate limits, and per-user credentials behind a single tool surface. Use Composio when Codex needs to act on third-party services rather than just answer questions about them.

How is Context7 different from Codex's built-in knowledge?

Codex's model knowledge has a training cutoff, so it can recommend deprecated APIs for fast-moving libraries like Next.js, React, or Tailwind. Context7 fetches live, version-accurate documentation from the source on demand, so Codex generates code that matches the exact version you are using. The index covers more than 100,000 libraries with trust scores and snippet counts.

Is Superpowers a Codex plugin or a Claude Code plugin?

Both. Superpowers started as a Claude Code skill collection and now ships first-class support for Codex CLI and the Codex desktop app. It includes Codex-aware tool mappings, sandbox-friendly worktree workflows, and graceful degradation when running in a single-agent harness. With 224k+ GitHub stars, it is the most comprehensive agent workflow framework available as a plugin.

What does Caveman do?

Caveman is a skill from Matt Pocock's collection that strips Codex's responses down to the essentials, cutting token usage by roughly 75% on routine interactions. It is a behavioral skill rather than a tool integration: it changes how Codex talks back, not what it can do. Useful when you want fewer pleasantries and more signal across long sessions.

How does RTK reduce Codex token usage?

RTK is a Rust CLI proxy that sits between Codex and your shell. It intercepts the output of common dev commands (git, npm, docker, kubectl, and 100+ others) and compresses or filters that output before it reaches Codex's context window. Reported token reductions are 60 to 90 percent on routine command output, with less than 10 milliseconds of overhead per call.

What is the Figma plugin for Codex?

The Figma plugin connects Codex to your Figma design files via the official Figma MCP server. Codex can read frames, components, and layout data directly from a Figma URL instead of working from screenshots, then generate React, Vue, or HTML/CSS that matches the design. This makes the design-to-code handoff far more accurate for components grounded in real Figma data.

Why use a Linear plugin in Codex?

The Linear plugin lets Codex pull tickets, update issue state, add comments, and break tasks into subtasks without leaving the CLI. You can ask Codex to summarize the next ticket in your queue, start implementation, then mark the ticket in review when the PR opens. It turns Linear into a shared memory layer between you and the agent across a development cycle.

What problem does GitNexus solve for Codex?

GitNexus builds an interactive knowledge graph of any codebase entirely in the browser, with no server or API key required. Drop in a repo or ZIP, and you get a visual graph plus a built-in Graph RAG agent that Codex can query for code exploration. It is most useful for onboarding to large unfamiliar codebases or auditing dependencies across files.

Where do I find more Codex plugins?

The Plugin Directory inside the Codex CLI is the official source — run /plugins to browse curated, shared, and self-created plugins. For community plugins, check the openai/skills repository, github.com/topics/codex-plugin, and the skills.sh directory maintained by Vercel. Matt Pocock's skills repo and obra/superpowers are two of the most actively maintained third-party collections.

What Are the Best Codex Plugins to Install in 2026

Q: What are Codex plugins?

Codex plugins are reusable packages that bundle skills, app connectors, and MCP servers into one installable unit. A single plugin can teach Codex a workflow, connect it to an external API like GitHub or Slack, and ship custom skills that activate when the task matches. Plugins are installed from the Plugin Directory inside the Codex CLI using the /plugins command.

TL;DR: Best Codex Plugins

Plugin	What it does
Matt Pocock's Skills	Engineering skill pack: grill-me, handoff, tdd, diagnose, caveman
Firecrawl	Live web context for Codex: search, scrape, crawl, browser interaction
Composio	Connects Codex to 1,000+ SaaS apps with managed OAuth
Context7	Injects live, version-accurate library docs into Codex
Figma	Generates code directly from real Figma design files
Linear	Pull tickets, update state, manage issues without leaving Codex
GitNexus	Client-side knowledge graph and Graph RAG over any codebase
Superpowers	Cross-harness agent workflow framework with Codex-native support
Caveman	Cuts Codex's response verbosity by ~75% to save tokens
RTK	Rust proxy that compresses command output before it hits Codex's context

Codex Plugins officially landed in early 2026, and the directory has been filling out fast. OpenAI ships a growing set of curated plugins (GitHub, Gmail, Drive, Slack, Sites, Security), and the community is publishing skill packs, MCP servers, and integration layers that snap into the same /plugins install flow.

The reason plugins matter more than any single Codex feature this year is reach. A plugin can ship a workflow, an app connector, and an MCP server in one install. You stop pasting setup instructions into AGENTS.md and start sharing a single command from the Plugin Directory. The right combination of plugins turns Codex from a capable agent into one that knows your APIs, your designs, your tickets, and the live web. If you are still picking between Codex and Claude Code, the Claude Code vs Codex comparison covers harness depth and sandboxing side by side.

These are the ten plugins I would install first on a fresh Codex setup.

What are Codex plugins?

Codex plugins are reusable packages that bundle three kinds of capabilities into a single install:

Skills — markdown instructions Codex follows when a task matches. The best Codex skills roundup covers the skill format in detail.
Apps — connectors to external services like GitHub, Gmail, Slack, or Google Drive.
MCP servers — live tool surfaces that let Codex call out to APIs.

One plugin can ship all three. The Firecrawl plugin, for example, registers an MCP server with search, scrape, crawl, and interact tools, plus skills that teach Codex when to reach for each one.

The official Codex plugins documentation covers the full spec, the Plugin Directory, and the ~/.codex/config.toml configuration surface. For the non-engineering angle on the same concepts — when to reach for a plugin versus a skill, with examples drawn from sales, ops, and marketing workflows — OpenAI Academy's Plugins and skills guide is the friendlier read.

Codex Plugin Directory inside the CLI showing curated, shared, and self-created plugins The Codex Plugin Directory groups plugins into Curated by OpenAI, Shared with you, and Created by you.

How to install Codex plugins

Plugins install through the Plugin Directory, which is available in both the Codex App (desktop) and the Codex CLI. The directory itself is the same — same curated set, same shared plugins, same custom plugins you have built — but the install flow looks a little different in each.

Installing plugins in the Codex App

The Codex App ships with a visual Plugin Directory. Open the app, head to the Plugins panel in the sidebar, and you will see the same three groups: Curated by OpenAI, Shared with you, and Created by you.

Codex Plugin Directory in the Codex App The Plugin Directory inside the Codex App groups plugins into Curated by OpenAI, Shared with you, and Created by you.

1. Browse or search. Pick a plugin from the curated list, or use the search bar to find a specific one (Firecrawl, GitHub, Linear, Figma, and so on).

2. Install. Click Install on the plugin card. The app downloads the plugin, registers its skills and MCP tools, and prompts for any required credentials (API keys, OAuth) on first use.

3. Invoke it. Inside any Codex session in the app, type @ to bring up the plugin picker and select the plugin you want to call. Most plugins also activate implicitly when your prompt matches a skill's trigger.

4. Toggle or remove. Each plugin card has an enable/disable switch and a remove option. No config file editing required.

Installing plugins in the Codex CLI

The Codex CLI uses the same Plugin Directory, exposed through the /plugins slash command.

1. Open the Plugin Directory. Start codex and run /plugins. You get the same three groups (curated, shared, created by you) in a TUI.

Codex CLI showing the /plugins menu Run /plugins inside the Codex CLI to browse and install from the directory.

Ready to build?

Table of Contents