Stop guessing how to distribute your Codex or ChatGPT plugin. The ecosystem has fractured into three distinct pipelines, and most power users are leveraging all of them to bypass bottlenecks. Whether you are shipping an MCP-backed app or a simple skill set, understanding the official review process versus the decentralized GitHub marketplace is critical for rapid adoption in late 2026.
The Official Gate: OpenAI's Shared Directory
Since July 9, 2026, OpenAI consolidated the ChatGPT app directory into a single public plugin directory shared by ChatGPT and Codex. This means submitting a ChatGPT app is now synonymous with submitting a plugin, regardless of whether it is skills-only, MCP-backed, or both. The submission process through the OpenAI Platform is rigorous: you must upload a built ZIP package and resolve any automated validation errors. For MCP servers, the requirements escalate significantly, demanding five positive and three negative test cases, a video walkthrough, and release notes. If your plugin requires authentication, you must provide a test account that functions without MFA or email codes, a hurdle many developers overlook until rejection. OpenAI notes that review timelines vary, and after approval, you choose when to publish.
The Hacker Route: GitHub Repos as Marketplaces
If you want speed over prestige, skip the review queue entirely. You can distribute plugins directly via your GitHub repository by adding a .agents/plugins/marketplace.json file. This allows users to install your plugin with two simple commands: codex plugin marketplace add owner/repo followed by codex plugin add plugin-name@marketplace-name. This method requires no approval from OpenAI and places the burden of trust on the developer's reputation and code visibility. It is the purest form of open-source distribution, allowing you to push updates instantly without waiting for a centralized gatekeeper to review your changes. Put those install commands at the top of your README and test from a clean machine before announcing.
Community Directories and Trust Signals
Beyond the official and GitHub routes, independent catalogs like PickAPlugin, awesome-codex-plugins, and HOL Plugins serve as crucial discovery layers. PickAPlugin offers a free listing where you simply send the repo on the submit page. The awesome-codex-plugins list is both an awesome list and an installable marketplace but requires a scanner score. HOL Plugins provides a free directory with trust scores. Other independent catalogs include CodexStacks, Codex Harness, and Codex Marketplace. To succeed here, your README must be optimized for conversion: include a one-sentence value prop, a copy-paste install line, a clear license, and recent commit history. Directories display last update dates, so stale repos get buried. Explicitly stating what files your plugin can read and write is also vital, especially if it executes shell commands or hooks.
Key Takeaways
- OpenAI merged ChatGPT and Codex directories on July 9, 2026, enforcing strict MCP testing requirements.
- GitHub repositories can function as direct marketplaces via
.agents/plugins/marketplace.json, bypassing review. - Community directories like PickAPlugin and HOL Plugins offer free listings but rely on trust scores and active maintenance.
- README optimization (clear install lines, recent commits, permission transparency) is the primary driver of adoption outside the official store.
The Bottom Line
Waiting for OpenAI's review queue is a strategic error for most indie developers. By combining the immediate visibility of GitHub-based marketplaces with the trust signals of community directories, you can achieve faster adoption and maintain total control over your release cycle without sacrificing credibility.