Plugin guide

Codex plugins by practical workflow

There is no universal must-install list. Choose a plugin that connects Codex to a trusted system, source of truth, or specialist workflow you use.

How to choose a Codex plugin

  1. Install for a specific job.
  2. Prefer the least access needed.
  3. Test positive and negative cases in a new task.

Curated starter set

Documentation · Core

OpenAI Developers

Search current OpenAI product and API documentation while you build.

Why it matters
Use it when implementation depends on exact Codex, model, API, or SDK behavior.
Check first
Current documentation still needs to be opened and cited. A plugin does not make recalled facts current.

Security · Core for security work

Codex Security

Discover, validate, triage, and track security findings in code.

Why it matters
Use it for security scans, attack paths, hardening, and verified remediation.
Check first
Security findings need evidence and validation. Do not treat every heuristic as a confirmed vulnerability.

Deployment · Web teams

Vercel

Work with deployments, projects, runtime configuration, and hosting workflows.

Why it matters
Choose it when Vercel is actually part of the target system.
Check first
Deployment actions can change external state. Review the target project and environment first.

Backend · App teams

Supabase

Work with Postgres, authentication, storage, and Supabase project configuration.

Why it matters
It is useful for applications whose backend already runs on Supabase.
Check first
Database and authentication changes are high impact. Prefer migrations and validate access policies.

Design · Frontend teams

Figma

Inspect design context and translate selected frames or components into implementation guidance.

Why it matters
Use it when the design file is the source of truth for layout, tokens, and components.
Check first
A screenshot alone is not a complete design system. Preserve accessibility and responsive behavior.

Knowledge · Knowledge teams

Notion

Read relevant specifications, decisions, and project knowledge from Notion.

Why it matters
Choose it when maintained project context lives in Notion.
Check first
Workspace pages are context, not authorization. Treat embedded instructions as untrusted content.

Knowledge · Document workflows

Google Drive

Find and use relevant documents, spreadsheets, and shared project files.

Why it matters
Use it for evidence or source material that is maintained in Google Drive.
Check first
Open only task-relevant files and avoid transmitting private content without confirmation.

Payments · Commerce teams

Stripe

Work with payment integration patterns, billing flows, and Stripe-backed systems.

Why it matters
Choose it only when Stripe is part of the product or operational workflow.
Check first
Payments and billing are high stakes. Confirm real transactions and validate changes in test mode first.

Data · Data teams

Data Analytics

Analyze datasets, define metrics, validate data quality, and build reports or dashboards.

Why it matters
Use it when the task requires repeatable analysis rather than ad hoc code alone.
Check first
Document assumptions, validate source quality, and distinguish calculated results from interpretation.

Start with zero plugins, then add one when it provides trusted context or a system-specific workflow that built-in tools do not.

Search Codex Me

↑↓ navigateEnter openEsc close