Codex Is a Workbench Now: 12 Plugins That Wire AI Into Real Workflows

Recently, I've been using Codex as my primary AI tool for nearly a month.

Initially, I only used it to complete code and fix bugs. After using it for a while, I increasingly feel that Codex's power isn't just about the model itself; more critically, it's about the plugin ecosystem behind it.

Many people install Codex and only use it to chat, generate code, and explain errors. But once you connect the plugins, Codex is no longer just a "question-answering window" — it can directly handle design, video, office tasks, data, and automation workflows. While others are still switching between tools, copying and pasting, and organizing materials, you can use a single sentence to get Codex to run an entire workflow.

I also have some AI Coding (SDD Agent AI tools, etc.) and Node technology exchange groups. If you're interested, you can add my personal WeChat ikoala520 to join the group, learn together, and make progress.

As of June 9, 2026, I've re-reviewed the official updates, plugin repositories, and community discussions. The most obvious recent trend is: Codex is shifting from a "programmer's tool" to a "knowledge work tool." In OpenAI's June 2nd update, they discussed role-specific plugins, Sites, and Annotations together, which already indicates the direction: plugins are not decorations, but a way to adapt Codex to different roles, toolchains, and deliverables.

The role plugins officially highlighted this time include data analysis, creative production, product design, sales, financial markets, and investment banking. Behind them are connections to real tools like Figma, Canva, Snowflake, Tableau, Salesforce, HubSpot, Gmail, Google Drive, and FactSet. In other words, what Codex aims to do is not "answer a few more questions," but help you produce work results.

So this article isn't a generic list of all plugins. I'll group the 12 most noteworthy plugins based on my own usage scenarios: some are suitable for design and content teams, some for writing reports, making PPTs, and processing spreadsheets, and some for automating repetitive operations. You don't necessarily need to install all of them, but if you truly want to make Codex your primary tool, there's a high probability you'll find a few here that fit your workflow.

The Conclusion First: Don't Install by Name, Install by Workflow

Many people fall into a trap when installing plugins: they install whatever is popular, ending up with a long list of entries on the left sidebar, but when it comes to actual use, they still just ask "help me write this."

I recommend selecting plugins based on your workflow. For example, if you're a content creator, prioritize installing Canva, Documents, Presentations, and Chrome. If you do product and front-end work, prioritize Figma, Product Design, Chrome, and Presentations. If you frequently handle data, put Spreadsheets first. If you do repetitive desktop operations, then consider Computer Use.

The value of a plugin isn't "one more button," but enabling Codex to access real materials, invoke real tools, and deliver real files.

Work Scenario	Recommended Combination	Suitable For
Quick Image Generation	Canva + Figma + Product Design	Content operators, designers, indie developers
Video Content	HyperFrames by HeyGen + Remotion	Short videos, courses, product demos
Office Deliverables	Presentations + Spreadsheets + Documents	Reporting, consulting, operations, managers
Professional Diagrams	BioRender + Documents	Scientific research, medical, educational content
Repetitive Operations	Chrome + Computer Use + Google Calendar	People needing web, desktop, and schedule automation

1. Canva: The Fastest Way to Turn Ideas into Presentable Images

Canva is suitable for anyone who needs to quickly produce images. You input the topic, purpose, and style, and Codex can invoke design templates to generate posters, social media images, article covers, event visuals, or promotional graphics.

The scenario it's best suited for isn't creating highly complex design systems, but rather "I need a usable image right now." For example, WeChat public account covers, Xiaohongshu images, course posters, event invitation images, and product launch announcements—these types of content often aren't worth designing from scratch, but you can't just slap on a screenshot either.

You can use it like this:

Use Canva to make a WeChat public account cover for me.
The theme is "Must-Install Codex Plugins Checklist," with a professional, tech-savvy style, not flashy.
The visual should emphasize the "plugin ecosystem" and "efficiency tools."

If you do content marketing, personal branding, knowledge monetization, or project promotion, Canva is the design plugin you should install first.

2. Figma: Turning Design Requirements into Editable Drafts

Figma is more suitable for product, UI, and front-end related work. You can give Codex a description, screenshot, existing page, or simple code, and have it generate editable high-fidelity drafts. You can also have it help you break down a design draft into components and implementation ideas.

Recently, discussions about product design within Codex have been very hot, essentially because an AI front-end can't just write code. Whether a page is usable depends on information hierarchy, visual density, interaction states, responsive layout, and brand feel. Plugins like Figma can bring forward the "design judgment before writing code."

A suitable prompt is:

Based on this product requirement, first give me 3 Figma drafts with different visual directions.
The target users are B-end operations personnel; the interface should be restrained, clear, and suitable for long-term use.
Don't make it a marketing landing page; prioritize information scanning efficiency.

If you often have AI write front-end code, I suggest putting Figma at the very front. It can reduce the rework of "realizing the aesthetics are wrong only after the code is written."

3. Product Design: Make Product Judgments First, Then Let Codex Write Code

Product Design is a role plugin that's been very noteworthy recently. Its difference from Figma is that Figma is more like a design file and canvas entry point, while Product Design is more like a product design workflow: first understand the brief, then do visual direction, product spec, prototyping, UI critique, and design review.

This type of plugin is best suited to solve an old problem: when AI writes front-end code directly, the functionality often works, but the page lacks a product feel. For example, the information hierarchy is unclear, it's uncomfortable on mobile, button states are missing, and the page looks like a template site. The value of Product Design is to bring forward the "judgment before writing code," letting Codex think like a product designer first.

You can use it like this:

Use Product Design to help me make a workspace for an AI writing tool.
Please don't write code yet; first give 3 product directions and visual directions.
The target users are tech bloggers and indie developers; the interface should be professional, restrained, and suitable for long-term writing.

If your workspace can see this plugin, I suggest product managers, front-end developers, and indie developers all give it a try. It's not simply about making pages look better, but about letting Codex complete a "product direction alignment" before development starts.

4. HyperFrames by HeyGen: Generate Videos from Scripts

HyperFrames by HeyGen is suitable for making short videos, product introductions, and demo animations. Its approach isn't traditional editing, but using HTML or scripts to describe visuals, then automatically rendering the video.

This type of plugin is very attractive to content teams because many videos are actually structured: an opening title, three selling points, product screenshots, subtitles, and a closing CTA. In the past, you had to drag the timeline bit by bit in editing software; now, you can first have Codex generate a video structure based on the copy, then hand it over to the plugin for rendering.

You can use it like this:

Turn this article into a 60-second short video script and use HyperFrames to generate a video draft.
Visual pacing: the first 5 seconds present the pain point, the middle showcases the 12 plugins, and the end gives installation advice.

It's suitable for people who need to produce video assets in batches, especially for product promotion, course clips, and feed ads.

5. Remotion: More Professional Video Motion Effects

If HyperFrames leans more towards "quick generation," Remotion is more suitable for creating controllable video motion effects. It's essentially a framework for writing videos with React, suitable for combining scripts, data, and animation parameters to generate structurally stable, reusable videos.

For example, product demos, course intros, data report animations, and version update videos can all be made into templates with Remotion. In the future, you only need to swap data, screenshots, and copy to generate a new video.

A typical use case is:

Use Remotion to make a 45-second product update video.
Structure: title intro, 3 feature points, each feature point paired with a screenshot animation, and finally display a QR code.
Please control the animation pacing to be clean, without excessive showiness.

If you're doing long-term content rather than one-off videos, Remotion's value is greater because it can turn video production into an engineered template.

6. Presentations: Quickly Generate PPT First Drafts

Presentations is the plugin I think is most easily underestimated. Many people think it's just "help me generate a PPT," but where it truly saves time is: it first helps you build an outline, break down logic, and arrange the structure, then generates a presentation file you can continue to modify.

Daily reports, project reviews, fundraising pitch decks, courseware, product launches, and internal training are all suitable for drafting with it. You don't need to start from a blank page, nor do you need to write an outline in a document first before moving it to PPT.

You can use it like this:

Help me make a 12-page PPT on the topic "Why Codex Plugins Will Change Knowledge Workflows."
The audience is product managers and content teams.
Please provide a complete outline first, then generate the presentation draft, with a professional style and moderate information density.

My advice is: don't have it make the final version directly; treat it as a "first-draft structure generator." Once the structure is out, supplement it with business details and real data, and efficiency will be much higher.

7. Spreadsheets: No More Manual Fiddling with Complex Tables

Spreadsheets is suitable for handling formulas, charts, data cleaning, and analysis. It can help you organize CSVs, create pivot tables, fill in formulas, generate charts, and explain why metrics changed.

Finance, operations, growth, sales, and content data analysis will all use it. Previously, you might have had to try formulas back and forth in Excel or Google Sheets; now, you can directly state your goal and have Codex generate the table structure and analysis conclusions.

For example:

Analyze this channel advertising data and find the main reasons for the drop in conversion rate.
Please generate a table with charts and give 3 actionable suggestions.

Recently, the official team has also listed data analysis plugins as a key direction, indicating that Codex's plugin ecosystem is expanding from "writing documents and code" to "explaining business changes." For people who frequently deal with data, this direction will become increasingly important.

8. Documents: Long-Form Text Processing and Report Writing

Documents is suitable for handling long texts: summarizing materials, extracting key points, rewriting reports, generating scripts, organizing meeting minutes, and drafting proposals. Its value isn't just writing words, but organizing a pile of scattered content into a structured document.

For example, if you have several articles, interview transcripts, and meeting minutes, you can have Codex first extract common themes, then generate a report framework, and finally export it as a document.

You can use it like this:

Read these materials and organize them into a 3000-word analysis report.
Structure includes: background, core findings, risks, recommendations, next steps.
Please retain key factual sources and do not fabricate data.

If you frequently write proposals, reports, articles, or scripts, Documents is basically a must-install.

9. BioRender: More Professional Scientific and Medical Diagrams

BioRender is more vertical, suitable for scientific research, medicine, biology, pharmacy, and educational content. You input professional requirements, and it can generate diagrams that better conform to academic expression conventions, such as mechanism schematics, experimental flowcharts, cellular pathway diagrams, and medical science illustrations.

The biggest fear with these types of diagrams is that they "look like decorative images." In scientific and medical scenarios, diagrams aren't for looking good, but for accurately expressing structures, processes, and relationships. BioRender's value lies in its better understanding of professional visual language compared to general design tools.

You can use it like this:

Help me make a medical science diagram on the topic "How GLP-1 Drugs Affect Appetite and Blood Sugar."
Requirements: clear structure, suitable for general readers to understand, avoid overly specialized terminology.

If you're not in scientific research or medicine, you can skip installing it for now; but as long as you have professional diagram needs, it will be much more reliable than general image generation tools.

10. Chrome: Let Codex Directly Operate Web Pages

Chrome is the most practical among the automation plugins. It allows Codex to control the browser, read web pages, scrape information, fill out forms, compare pages, and check visual effects.

For developers, it can be used to verify local pages: open localhost, click buttons, take screenshots, and check if interactions are normal. For non-developers, it can handle some repetitive online tasks, like organizing web materials, comparing prices, entering forms, and checking backend data.

You can say this:

Open this web page and organize the product names, prices, and key features on the page into a table.
If there is pagination, please continue to the next pages and finally give me a summary.

A reminder: when it comes to actions like logging in, making payments, publishing, deleting, or sending emails, don't let the AI decide automatically. It's best to have it prepare, preview, and confirm first, then you authorize the execution.

11. Computer Use: Let Codex Operate Local Desktop Applications

Computer Use goes a step further than Chrome. Chrome mainly controls the browser, while Computer Use can operate local Mac applications and system interfaces, such as clicking, typing, scrolling, dragging, and reading screen content. This means some tasks that have no API, no web interface, and can only be done through a desktop UI can also be handed over to Codex for semi-automated processing.

It's suitable for handling those "simple but annoying" tasks: exporting files from a desktop application, batch-changing settings, checking interface status based on screenshots, moving information between multiple windows, or operating an old system backend. For developers, it can also be used for manual acceptance testing of local applications, especially for interactions that are hard to verify solely through the command line.

You can use it like this:

Use Computer Use to open this desktop application and check if the export process is normal.
Please only operate up to the preview and confirmation page, do not click final submit or delete buttons.
If you encounter a step that requires my authorization, stop and explain first.

This plugin is very powerful, but also requires more caution. Any action involving payment, deletion, publishing, sending, authorization, or changing system settings should have Codex stop before confirmation. It's best suited for "supervised automation"; don't let high-risk operations run completely unchecked.

12. Google Calendar: Let Codex Manage Your Schedule Too

Google Calendar is suitable for managing schedules, creating meetings, adjusting arrangements, and coordinating time. It might not look as flashy as design or video plugins, but it's very useful for team collaboration.

For example, you can have Codex automatically extract to-do items from emails or meeting minutes, find suitable times, and generate schedule drafts; you can also have it help you check this week's arrangements to find conflicts and gaps.

A typical use case is:

Based on this meeting minutes, help me create a draft for the follow-up schedule.
It needs to include: requirements review, design confirmation, development scheduling, and launch review.
First list the suggested times and attendees, don't create them directly, wait for my confirmation.

The key to schedule plugins isn't "automatically arranging everything for you," but reducing low-value coordination costs. Truly important judgments still need your confirmation.

3 Trends Worth Paying More Attention To Recently

Besides the 12 specific plugins above, I think there are 3 trends worth mentioning separately.

First, role plugins will become increasingly important. OpenAI's official repository has already made templates for sales, data analysis, product design, and financial market plugins. They aren't single tools, but packages that bundle a set of skills, connectors, instructions, and workflows. In the future, you might not just install a Figma, but install a complete workflow oriented towards "product design."

Second, Sites will change the delivery method. Previously, AI-generated results were often documents, spreadsheets, PPTs, or code files. The direction of Sites is to let Codex generate shareable interactive pages, such as dashboards, project boards, client review pages, and activity planning pages. Once this matures, many temporary tools and internal pages can be directly built with Codex.

Third, plugins will move from "what the official provides" to "what teams customize themselves." You can already see plugin template structures in the official repository, including .codex-plugin/plugin.json, .app.json, .mcp.json, skills/, and assets/. This means that in the future, the real value won't be in installing the most plugins, but in solidifying your own business processes into plugins.

Installation Method and Usage Suggestions

Plugin installation is very simple. Find Plugins on the left side of the Codex App, search for the plugin name, and install it directly; it usually takes less than a minute. Some plugins require account binding or connector authorization, just follow the prompts to complete it.

But I don't recommend installing them all at once. Too many plugins will scatter your attention and increase permission management costs. A more reasonable approach is to first pick 3 to 5 based on your main workflow:

If you mainly do	Install these first
Writing and content creation	Documents, Canva, Chrome, Presentations
Product and front-end	Figma, Product Design, Chrome, Presentations
Operations and data	Spreadsheets, Documents, Chrome
Courses and videos	HyperFrames by HeyGen, Remotion, Canva
Scientific and medical content	BioRender, Documents, Presentations
Desktop automation	Chrome, Computer Use, Google Calendar

Also, pay attention to three points.

First, the plugins visible may vary slightly depending on your account, region, and workspace. Business and Enterprise workspaces may also be subject to administrator permission controls.

Second, the closer a plugin is to a real business system, the more you need to pay attention to permissions. For plugins like browsers, email, calendars, CRMs, and cloud drives, it's best to have Codex generate drafts and suggestions first, and not allow it to execute irreversible operations by default.

Third, more plugins aren't necessarily better. What truly improves efficiency is whether you can string them into a fixed process. For example, "Chrome searches for materials → Documents organizes → Presentations creates PPT → Canva makes the cover," or "Product Design sets direction → Figma refines the draft → Codex writes the prototype → Chrome verifies the page." This is more valuable than calling a single plugin in isolation.

Finally

After making good use of these plugins, Codex is no longer just a chat tool, nor just a code assistant. It's more like a workstation that can orchestrate tools: you give it a goal, and it helps you find materials, do design, write documents, process data, generate presentations, and even operate browsers and schedules.

Of course, the actual effect depends on your usage habits. Don't try to accomplish everything at once in the beginning; start with one high-frequency scenario, and solidify the prompts, materials, and delivery format. Once one process runs smoothly, then connect a second plugin, and a third.

I also have some AI Coding (SDD Agent AI tools, etc.) and Node technology exchange groups. If you're interested, you can add my personal WeChat ikoala520 to join the group, learn together, and make progress.

I'm now more and more certain of one thing: the gap in the future won't be about "whether you can ask AI," but "whether you can connect AI into real workflows." This is exactly where the Codex plugin ecosystem gets truly interesting.

Further Reading

Material	Why It's Worth Reading
OpenAI: Codex for every role, tool, and workflow	Official release on June 2, 2026, introducing role plugins, Sites, and Annotations.
OpenAI GitHub: role-specific-plugins	Official role plugin template repository, where you can see the plugin structures for sales, data analysis, product design, financial markets, etc.
Example discussion about the Product Design plugin on X	An entry point for intuitive community feedback on Codex's design plugins.