Where does a codex plugin install on my machine?

The CLI places files in your Codex config directory (typically under ~/.codex or project-local .codex). Exact paths depend on Codex version and install flags.

Do codex plugins work in the Codex IDE extension?

Yes. Install commands work for both CLI and IDE users. Restart or reload after installing a new codex plugin.

What if a codex plugin needs an API key?

Follow the plugin README. Most official codex plugins guide you through OAuth. Community plugins may use environment variables — never commit keys to git.

Documentation

How to Install a Codex Plugin

The complete guide to finding, installing, and managing codex plugins for OpenAI Codex

Getting Started

Codex plugins extend OpenAI Codex with integrations for GitHub, Slack, Figma, and more. Install any plugin with a single npx command. Browse plugins, skills, and hooks on this site, then copy the install command and run it in your terminal.

Installing a Plugin

Plugins add full integrations to Codex. Find a plugin on the Plugins page, copy the install command, and run it in your project directory.

npx codex-marketplace add openai/plugins/plugins/github --plugin

Installing a Skill

Skills are standalone agent instructions that Codex can invoke for specialized tasks. Browse the Skills page and copy the install command.

npx codex-marketplace add Dimillian/Skills/github --skill

Installing a Hook

Hooks automate Codex lifecycle events — notifications, linting, git workflows, security scans, and more. Browse the Hooks page and copy the install command.

npx codex-marketplace add am-will/codex-skills/hooks/aitmpl-codex/automation/discord-notifications --hook

CLI Reference

The install CLI manages plugins, skills, and hooks. Use --plugin, --skill, or --hook flags to specify the item type. The add command downloads and configures the item in your Codex environment.

# Install a plugin
npx codex-marketplace add <owner/repo/path> --plugin

# Install a skill
npx codex-marketplace add <owner/repo/path> --skill

# Install a hook
npx codex-marketplace add <owner/repo/path> --hook

Requirements

You need Node.js 18+ and the OpenAI Codex CLI installed. Sign in with your ChatGPT account. Some plugins require additional API keys or environment variables — check each plugin's description for setup instructions.

Getting started with codex plugins

This guide explains how to find, install, and manage codex plugins from codexplugin.com. Whether you are installing your first OpenAI Codex extension or adding a tenth integration to your workflow, the process is the same: browse the directory, copy the command, run it in terminal.

A codex plugin is distributed as files in a GitHub repository. The install CLI downloads those files and registers them with your local Codex configuration. You do not manually edit config JSON for most plugins — the CLI handles paths and manifests.

Before installing any codex plugin, confirm you have Node.js 18 or newer, the Codex CLI or IDE extension installed, and an active ChatGPT sign-in. Some codex plugins open OAuth flows in your browser on first use.

Install codex plugin commands reference

Plugins use --plugin: npx … add owner/repo/path --plugin. Skills use --skill. Hooks use --hook. The owner/repo/path segment comes from each listing card in our directory — copy it exactly to avoid 404 errors.

Run install commands from the project directory where you use Codex, not necessarily your system root. After install, restart Codex or reload the workspace. Test with a simple prompt tied to the codex plugin you added.

If install fails, check network access to GitHub and npm registry, verify Node version, and read the plugin README for extra dependencies. Community codex plugins may require Python, Docker, or API keys not mentioned in the one-line card description.

Managing your codex plugin setup

Document which codex plugins your team standardizes on — especially OAuth-connected ones like GitHub or Slack. New teammates can install the same set from this directory in minutes.

Update codex plugins when authors ship breaking changes. Re-run the install command or follow the author's migration notes. Remove plugins you no longer use to keep Codex startup fast and reduce unused OAuth tokens.

Combine codex plugins with skills and hooks for a full stack: integrations from plugins, quality playbooks from skills, automation from hooks. Our homepage and category pages explain how each layer fits together.

Troubleshooting codex plugin installs

Command not found: upgrade Node.js to version 18 or newer and ensure npx is available. Network errors: confirm GitHub and npm are reachable from your network; corporate proxies may need HTTPS_PROXY configured. OAuth loops: clear browser cookies for the provider and retry authorization from the plugin README steps.

Plugin installed but agent ignores it: restart Codex CLI or reload the IDE window. Wrong behavior: verify you used --plugin vs --skill vs --hook — mixing flags installs the wrong artifact type. Still stuck? Compare your command character-by-character with the listing on our codex plugin browse pages.

OpenAI Codex plugin resources

Official OpenAI Codex documentation covers CLI setup, IDE extension features, and security model. Our directory complements those docs with a searchable codex plugin catalog and copy-ready commands — use both together when onboarding a team.

Return to the Plugins page to browse integrations, the Skills page for agent playbooks, and the Hooks page for automation. The homepage FAQ answers common codex plugin questions for newcomers.

Frequently asked questions

Where does a codex plugin install on my machine?: The CLI places files in your Codex config directory (typically under ~/.codex or project-local .codex). Exact paths depend on Codex version and install flags.
Do codex plugins work in the Codex IDE extension?: Yes. Install commands work for both CLI and IDE users. Restart or reload after installing a new codex plugin.
What if a codex plugin needs an API key?: Follow the plugin README. Most official codex plugins guide you through OAuth. Community plugins may use environment variables — never commit keys to git.