Codex Plugins

What is Codex Plugins?

Codex Plugins are bundles that extend what Codex can do by combining reusable “skills,” app integrations, and MCP servers into workflows available in Codex. The goal is to let Codex access tools and structured workflows for tasks such as reading and managing email, working with documents and files, or drafting and summarizing messages in team tools.

For example, you can install a Gmail plugin so Codex can read and manage Gmail, a Google Drive plugin to work across Drive, Docs, Sheets, and Slides, or a Slack plugin to summarize channels or draft replies. Plugins can also include MCP servers to provide Codex access to additional tools or shared information—often from systems outside the local project.

Key Features

• Plugin bundles reusable workflows: A plugin can package multiple capabilities (skills, apps, and/or MCP servers) so Codex can use them as part of a task.
• Skills for task-specific instruction: Skills are reusable instructions for specific kinds of work; Codex can load the right steps and references (including helper scripts) when needed.
• Apps for reading and taking actions in external tools: App connections (e.g., GitHub, Slack, Google Drive) let Codex read information from tools and take actions in them.
• MCP servers for additional tool access: MCP servers provide access to additional tools or shared information, including from systems outside the local project.
• Curated installation flow in the app and CLI: You can browse and install curated plugins in the Codex app, or open the plugins list from the Codex CLI (via codex /plugins).
• Permission and data-sharing controls remain in effect: Installing a plugin makes the workflows available, but existing approval settings still apply; connected external services follow their own authentication, privacy, and data-sharing policies.

How to Use Codex Plugins

1. Open the plugin browser: In the Codex app, open Plugins and browse the curated directory. In the Codex CLI, run codex /plugins to open the plugins list.
2. Install a plugin: Select the install button (app) or “Install plugin” (CLI). If the plugin needs an external app, connect it when prompted. Some plugins require authentication during install; others defer it until first use.
3. Start a new thread and ask Codex: After installation, start a new thread and request the task (for example, summarizing unread Gmail threads from today or pulling launch notes from Google Drive).
4. Choose between automatic selection and explicit invocation:
   • Ask for the outcome directly and let Codex use the right installed tools.
   • Specify a particular plugin or bundled skill by using @ to invoke the plugin/skill explicitly.

Use Cases

• Email triage and summarization: Install the Gmail plugin and ask Codex to summarize unread Gmail threads from a specific time window.
• Content retrieval across productivity suites: Install the Google Drive plugin and request the latest launch notes, with Codex working across Drive, Docs, Sheets, and Slides.
• Team communication support: Install the Slack plugin to summarize a channel or draft replies based on channel context.
• Workflow automation with integrated tools: Use plugins that bundle apps and skills so Codex can follow the appropriate steps and references for a task while interacting with external systems.
• Access to external systems via MCP: For workflows requiring tools or shared information outside the local project, use plugins that include MCP servers.

FAQ

• What happens when I install a plugin? Installing a plugin makes its workflows available in Codex, but your existing approval settings still apply.

• Do plugin integrations change my existing approvals or privacy controls? No—approval settings you already have continue to apply. For data accessed or actions taken through connected services, those external services’ authentication, privacy, and data-sharing policies apply.

• When do I authenticate with external apps? Some plugins ask for authentication during install, while others wait until the first time you use them. Codex may prompt you during setup or first use when the plugin includes apps.

• How do I disable or remove a plugin? To remove it, uninstall via the plugin browser in the Codex app. Uninstalling removes the plugin bundle from Codex, but bundled apps can remain installed until you manage them in ChatGPT. To turn off a plugin without uninstalling, set enabled = false for the plugin entry in ~/.codex/config.toml and restart Codex.

• Can I create my own plugin? Yes. The documentation points to a “Build plugins” page that covers local scaffolding, manual marketplace setup, plugin manifests, and packaging guidance.

Alternatives

• Codex without plugins: Use Codex’s built-in capabilities for tasks that don’t require direct access to external systems like Gmail, Drive, or Slack.
• General-purpose automation via external apps/APIs: If you need multi-step actions across tools, an alternative is building or using automation flows that call the relevant APIs directly rather than using Codex plugins.
• Other assistant integrations using tool connectors: Instead of Codex plugins, you can use assistant platforms that support tool integrations (e.g., connectors and “actions”) to bring external data and actions into chat workflows.
• MCP-based tool access without a Codex plugin wrapper: For users who specifically want MCP server access, an alternative approach is to integrate MCP servers and tools in a way that fits your existing workflow, rather than installing a packaged Codex plugin bundle.