Feature request: Support for plugin marketplaces

Resolved 💬 5 comments Opened Jan 8, 2026 by PaulRBerg Closed Aug 5, 2026

💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

The problem

I use both Claude Code and Codex, and there's a gap in extensibility.

Claude Code has a plugin marketplace system that lets me install community-built extensions with one command. Things like custom slash commands, specialized agents, hooks, and MCP servers — all shareable and version-tracked.

For example, I've got playwright-skill installed which lets Claude run browser automation tasks. There are other plugins for code review workflows, deployment helpers, etc.

Codex doesn't have an equivalent system. When I switch between the two tools, I lose access to all these extensions.

What I'd like

A plugin/extension system in Codex that enables:

Installing third-party tools from Git repositories
Sharing custom capabilities across teams
Community-driven ecosystem of extensions

This would bring Codex closer to parity with Claude Code's extensibility model.

---

Codex: 0.79.0 · Platform: macOS arm64

View original on GitHub ↗

5 Comments

Mathf18 · 7 months ago

I would use that as well ! I want to easely share Skill, MCP across my team! ATM, its kind hard and much easier on claude !

PaulRBerg · 7 months ago

A simple implementation would look at ~/.claude/plugins

I know you would like to use ~/.codex/plugins but that would mean a symlink and maintenance cost so it would be great if you could just look at ~/.claude/plugins

styler-ai · 7 months ago

Seems like a duplicate of https://github.com/openai/codex/issues/8512

etraut-openai contributor · 7 months ago

I think this feature request is for a marketplace site, whereas the other one is for an underlying plugin mechanism. This feature depends on the other, but we can keep them both open for now.

etraut-openai contributor · 23 days ago

CLI now supports third-party plugin marketplaces