The Ultimate Guide to Codex Plugins: From Beginner to Power User

Opening the Codex plugin page, the most frustrating thing is the wall of English text—there’s just too much. Every plugin looks useful, yet none seems immediately necessary. So instead of walking through a “plugin list,” I’ll frame it differently.

Can these plugins actually enter your real workflow?

If you’re browsing the web in your browser, it needs to see web pages. If you’re modifying a PR on GitHub, it needs to read the repo and comments. If you’re handling tasks in Gmail, Slack, or Linear, it needs to access those tools. If you’re working on spreadsheets, PPTs, PDFs, or Word docs, it needs to understand the structure of those files—not just copy out the text.

That’s where plugins shine: Codex doesn’t just give suggestions in a chat box—it goes to where the work happens.

After reading this, you won’t need to remember every plugin’s description. You’ll just know: which ones to install now, and which ones look powerful but can wait.

Table of Contents (other series at the end of the article)

Don’t Choose by Plugin Name

I’ll group Codex plugins into categories.

Interface-oriented: Browser, Chrome, Computer Use.

File handling: Documents, Spreadsheets, Presentations, PDF, Template Creator.

Communication & project flow: Gmail, Slack, Teams, Outlook, GitHub, Linear, Vercel.

Business system integration: Google Drive, Notion, Airtable, Supabase, Stripe, Shopify, PostHog.

Design & content: Canva, Figma, Data Analytics.

This makes it clear. You don’t ask “is this plugin advanced?” Instead, ask “do I have this use case?”

Without a use case, even the strongest plugin just takes up space. With a use case, one plugin can eliminate a lot of copying, pasting, screenshots, and switching windows.

Browser, Chrome, Computer Use: All Three Can Browse the Web, But They’re Different

Many people get confused by these three first.

Browser is Codex’s built-in in-app browser. It’s good for local development pages, public web pages, and previews. For example, if you ask Codex to modify a front-end page, it can open localhost, click buttons, check console errors, and take screenshots to inspect layouts. It’s handy for building web pages, tweaking UI, and verifying front-end changes.

Chrome allows Codex to use your Chrome state. Its key feature is “logged in.” If you need Codex to access backend systems, CRMs, LinkedIn, internal company pages, or any site that requires login, think of Chrome. It’s closer to your real browser than Browser, and it demands more caution with permissions because it might access history, login states, and page content.

Computer Use is more like remote control. It can see the screen, click desktop software, open system settings, and operate things that have no API, no web interface, and no plugin. It’s powerful, but don’t make it your default. If you can use the GitHub plugin, don’t have it click through GitHub in a browser; if you can use the Gmail plugin, don’t have it slowly search for emails in the browser. Computer Use is for tasks that “only have a graphical interface to work with.”

In one sentence:

• Local pages and public web pages: use Browser.
• Needs your login state: use Chrome.
• Needs desktop software and system UI: use Computer Use.

Documents, Spreadsheets, Presentations, PDF: A Set That Non-Programmers Can Use Immediately

This group of plugins is often underestimated.

• Documents handles Word files, reports, memos, and the like. It doesn’t just help you write a paragraph; it can modify according to the document structure, add comments, manage versions, and make the content closer to a deliverable draft.

• Spreadsheets handles Excel, CSV, and table analysis. Ordinary chat models can interpret tables too, but the trouble is often hidden in formulas, formatting, worksheet structure, column name cleaning, charts, and summaries. Sales tables, budgets, data cleaning, monthly reports—all can be handed to it first.

• Presentations handles PPT or slide decks. It’s good for compressing a bunch of material into a structure, breaking pages into titles, bullet points, presentation order, and then making a file that can be further edited. For people who frequently give reports, this is more useful than “give me an outline.”

• PDF plugin reads, creates, and inspects PDFs. The issue with PDFs is their fixed layout; often you can’t just read the text. You need to check contract pages, report layouts, scanned materials, exported manuals—the PDF plugin is more reliable than plain text reading.

• Template Creator is more for long-term use. If you have fixed formats like weekly report templates, client proposal templates, or research card templates, you can turn them into reusable templates. Next time, just ask Codex to produce in your format, reducing the need to explain the rules again.

This group suits people who may not write code but are constantly buried in documents, spreadsheets, PPTs, and PDFs.

Gmail, Slack, Teams, Outlook: Bring Communication Flow In

Communication plugins solve the problem of “information scattered everywhere.”

• Gmail can help you check emails, summarize threads, find pending replies, draft responses. Good for people whose inbox has clients, collaborations, invoices, and notifications.

• Slack, Teams are for team communication. They can organize progress, disputes, tasks, and owners from channels, and also help draft replies. The main saving is in judgment cost: you don’t have to guess “where is the bottleneck now” from dozens of messages.

• Outlook is for those using Microsoft’s email and calendar ecosystem. For corporate email users on Outlook, it’s closer to the work environment than Gmail.

These plugins share a common boundary: the closer to real communication, the more careful you need to be with permissions and accidental sends. Having Codex summarize, search, and draft is fine; before sending, best to review yourself.

GitHub, Linear, Vercel: The Essential Trio for Developers

If you use Codex for coding, the GitHub plugin is almost top priority.

It can view repos, PRs, Issues, review comments, CI results, help you locate failed checks, organize code review feedback, and prepare changes. Without it, Codex can only guess context locally; with it, Codex sees the collaboration scene.

• Linear handles requirements and tasks. It brings in product requirements, bugs, and project progress. You can have Codex read tickets, break down tasks, update status, and align implementation plans with project management. It fills in the background of “why the code needs to change this way.”

• Vercel handles deployments, build logs, project configuration, and online troubleshooting. After a frontend project goes live, issues often aren’t in the code editor but in deployment logs, environment variables, build failures, domains, and protection settings. The Vercel plugin lets Codex see this information, reducing the back-and-forth of “copy the error for me.”

Put together, this set allows Codex to cover a common development chain: from task to code to PR to deployment.

OpenAI Developers, Supabase, Stripe: Install When Building Products

• OpenAI Developers plugin is for those integrating the OpenAI API. It can check official docs, help you understand API, Agents SDK, model calls, error troubleshooting. When writing AI apps, it’s more direct than generic search.

• Supabase plugin is for projects using Supabase. Database, table structures, SQL, permissions, Auth, logs, Edge Functions—once these are separated from the code, it’s easy to lose continuity. The plugin lets Codex understand both application code and backend state simultaneously.

• Stripe plugin handles payments, subscriptions, invoices, refunds, customer management. Payment systems are most afraid of “looks like it works, but actually misses key steps.” It connects products, prices, payment links, subscriptions, webhooks, and documentation suggestions.

These plugins don’t need to be installed in advance. They become essential when you’re actually building AI apps, backend databases, or payment systems.

Canva, Drive, Notion, Airtable: Content and Operations Will Feel the Difference

• Canva is for design, social media images, presentations, brand assets. It connects “ideas” to editable designs, not just a prompt.

• Google Drive suits teams with materials scattered in Docs, Sheets, Slides, and folders. It acts as an entry point for Codex to find context from cloud files.

• Notion is for knowledge bases, meeting notes, project documentation. Its best uses: finding answers from old materials, and organizing new information back into the knowledge base.

• Airtable suits operation tables, content libraries, customer databases, project ledgers. It sits between a spreadsheet and a lightweight database, suitable for letting Codex query, update, and analyze structured records.

The judgment for this group is simple: wherever your work materials live, Codex should connect there. Materials in Notion? Don’t copy them out every day. Materials in Drive? Let it read directly.

Data Analytics, PostHog, Figma: Only Touch When You Have a Clear Need

• Data Analytics sounds like everyone needs it, but it’s more suited for those with data analysis habits: product usage, KPIs, notebooks, semantic layers, dashboards. If you only occasionally look at a small table, Spreadsheets is enough.

• PostHog is for product teams. It cares about user behavior, experiments, feature flags, errors, funnels, retention. If you don’t have a tracking system, it won’t be very useful; if you’re already using PostHog, it lets Codex find product issues from data.

• Figma is for design-to-development collaboration. It lets Codex understand design files and assist in translating UI into code. For non-UI people, skip it.

Don’t be intimidated or attracted by the names of this group. Their professionalism only becomes tangible in professional scenarios.

Skill, Plugin, MCP, Hook: Just Remember Four Sentences

• Skill is a workflow method. For example, if you want Codex to always follow a certain process for writing, reviewing, or researching, write that method as a Skill.

• Plugin is an installation package. It can bundle Skills, app connections, MCPs, and resources together for easy installation, sharing, and management.

• MCP is a channel for connecting to external systems. GitHub, documentation, databases, search, internal tools—many capabilities are provided through this kind of connection.

• Hook is an automatically triggered action. For example, performing checks or processes during certain lifecycle events. It’s useful but more for advanced users; check permissions and behavior carefully when installing.

For regular users, remember: Skill is like a method, Plugin is like a kit, MCP is like an interface, Hook is like an automation switch.

How I’d Recommend You Install

If you just want to try Codex plugins first:

• Browser, Documents, Spreadsheets, PDF

This set covers web page verification, documents, spreadsheets, and PDFs. The daily impact is most noticeable.

If you’re a developer:

• Browser, GitHub, Linear, Vercel

This set covers local pages, code collaboration, task management, and deployment troubleshooting.

If you mainly handle communication and operations:

• Gmail or Outlook, Slack or Teams, Google Drive, Notion, Airtable

This set is more like plugging Codex into your information flow.

If you’re building a commercial product:

• OpenAI Developers, Supabase, Stripe, plus PostHog as needed.

Don’t install all of these at the start. Install them when you actually hit API, database, payment, or user behavior analysis—it’ll be clearer.

My advice is straightforward: install fewer, but install them into your workflow.

The plugin page is not a bookmark collection. When you install a plugin, you should immediately be able to say which step it saves you: one less context copy, one less PR review, one fewer email check, one less backend login, one fewer manual page inspection.

If you can say it, it’s valuable.

If you can’t, leave it for now.

Sources and Boundaries

This article is compiled based on official documentation and local Codex plugin information available as of June 28, 2026. Codex plugins are evolving rapidly; the number, names, connection methods, and permission descriptions may change. When installing plugins that involve external accounts, be sure to check the authorization scope, especially for highly sensitive tools like email, browsers, team communication, payment, and databases.

References:

OpenAI Codex Plugins

Build a Codex Plugin

Codex Skills

Codex Customization

Codex Browser

Codex Chrome Extension

Codex Computer Use

OpenAI Developers Codex Plugin

Codex Security Plugin

I’m Captain Noah Duck, guiding you to find land in the ocean of information~

Stripe The Ultimate Guide: From Beginner to Power User

Product Hunt The Ultimate Guide: From Beginner to Power User

Conso The Ultimate Guide: From Beginner to Power User

Telegram The Ultimate Guide: From Beginner to Power User

Remove AI Flavor The Ultimate Guide: From Detection to Mastery

Web Scraper The Ultimate Guide: From Beginner to Power User

PayPal The Ultimate Guide: From Registration to Mastery

giffgaff The Ultimate Guide: From Beginner to Power User

US Purple Card PayGo The Ultimate Guide: From Pitfall to Mastery

Wise The Ultimate Guide: From Account Opening to Mastery

Gmail The Ultimate Guide: From Registration to Mastery

Apple The Ultimate Guide: From Beginner to Power User: Device Selection

Apple The Ultimate Guide: From Beginner to Power User: Apple ID

Apple The Ultimate Guide: From Beginner to Power User: Black Tech