OpenAI Codex is getting plugins, with OpenAI Developers announcing a rollout designed to let Codex work “out of the box” with tools that show up in day-to-day building: Slack, Figma, Notion, Gmail, and others. The move is aimed less at flashier coding demos and more at the messy perimeter of software work—planning, research, coordination, and the workflows that happen after code is written—while keeping in mind that this plugin system is not exactly the same as Claude plugins.
Plugins as a bridge to “real work” around code
OpenAI frames plugins as a way for Codex to support work that often precedes a pull request: gathering context, organizing decisions, and coordinating across the services where teams keep specs, mockups, and threads.
One concrete example mentioned is a Google Drive plugin that lets Codex operate across Google Drive, Docs, Sheets, and Slides, with “bundled workflows in one loop.” The notable detail here is the emphasis on spanning multiple Google apps under a single plugin experience, rather than treating each surface as a separate integration.
Under the hood: apps, auth, and bundled “skills”
The technical pitch is that plugins bundle apps and “skills” so Codex can authenticate to tools cleanly and be “instantly” competent at using them. In other words, the integration isn’t just a connector—it also packages a set of operational know-how for working with that connector.
That “skills” framing also prompted community commentary. In a reply, developer Eve Park noted the similarity to other agent systems that have converged on skills as a unit of agent knowledge, even if naming and product shapes differ.
Where plugins show up, and what’s next
OpenAI says plugins are available across the Codex product surfaces: the Codex app, Codex CLI, and IDE extensions. The company also signaled continued expansion—more plugins over time and a growing skills library—and pointed to an option to build custom plugins and share them internally with a team.
