OpenAI's Codex development tool now supports plugins that connect directly to Slack, Figma, Notion, Gmail, and Google Drive, expanding the AI assistant beyond coding into full workflow automation. The move positions Codex to compete more directly with Anthropic's Claude Code, which has established early dominance among developers.
Plugins bundle authentication and pre-built skills for each service, allowing Codex to operate within tools like Google Drive across Docs, Sheets, and Slides without manual configuration. The integrations work across the Codex app, CLI, and IDE extensions including JetBrains environments.
OpenAI rolled out more than 20 plugins on March 26, 2026. The company differentiates between skills for personal or project-specific use and plugins for team sharing.
"Start local, then package the workflow as a plugin when you are ready to share it,"
OpenAI recommends in its documentation. The expansion comes as Claude Code has gained traction among developers while Codex adoption has lagged behind. One developer noted that every programmer they talk to uses Claude Code, while none have mentioned using Codex. The $200 monthly starting price for Codex versus Claude's $100 Max plan may contribute to the disparity.
Plugins transform Codex from a coding assistant into what OpenAI calls "the agentic force behind planning, research, coordination, and post-development workflows." The Figma integration connects directly to design files, removing friction in design-to-code handoffs. Slack and Notion plugins handle coordination and documentation tasks that typically surround coding work.
Codex runs on the GPT-5.3-Codex model across all surfaces, which operates 25% faster than its predecessor while using 48% fewer tokens for equivalent results. Over 1 million developers used Codex in the past month alone according to OpenAI data released earlier this week.
OpenAI plans to open plugin development to third parties soon with self-serve publishing tools. The company mentions "marketplace" 41 times in its announcement blog post, signaling ambitions for a broader ecosystem where developers can share custom integrations.
