Codex CLI: Plugin Marketplace Discovery & Lifecycle Management

CodexView original changelog

Codex CLI 0.113.0 expanded the plugin system β€” first introduced in 0.110.0 β€” with curated marketplace discovery, richer plugin/list metadata, install-time authentication checks, and a dedicated plugin/uninstall endpoint. These additions formalize the plugin lifecycle in Codex CLI, moving from a manual configuration-file approach to a structured install-discover-uninstall workflow. Developers can now find, authenticate, install, and remove plugins through the app-server API rather than hand-editing config.toml.


Plugin Marketplace Discovery & Lifecycle Management in Codex CLI

When OpenAI introduced the Codex CLI plugin system in version 0.110.0, it established the foundation: load skills, MCP entries, and app connectors from config or a local marketplace file. Codex CLI 0.113.0 takes that foundation and turns it into a full plugin lifecycle, with curated marketplace discovery, richer metadata, install-time authentication, and an uninstall endpoint.

Curated Marketplace Discovery

The 0.113.0 release adds curated marketplace discovery to the plugin system. The plugin marketplace surfaces a browsable, curated list of available plugins β€” including skills, MCP connectors, and app integrations β€” directly within the CLI workflow. This removes the need for developers to manually locate and configure plugins by searching GitHub or sifting through documentation pages.

The plugin/list endpoint now returns richer metadata alongside each plugin entry: descriptions, capability tags, authentication requirements, and compatibility information. This metadata powers the in-app discovery surface and gives developers the context they need to evaluate plugins before committing to an install.

Install-Time Authentication Checks

A common friction point with plugin systems is discovering authentication failures after installation. Codex CLI 0.113.0 addresses this with install-time auth checks: when a plugin is installed via the plugin/install endpoint, the CLI validates authentication credentials before activating the plugin. Developers get immediate feedback if credentials are missing or invalid, rather than encountering auth errors later during an active agent session.

The plugin/install endpoint adds the plugin to the cache folder and enables it in config.toml, making the installation persistent across sessions without requiring manual file edits.

Plugin Uninstall Endpoint

The release also adds a plugin/uninstall endpoint, completing the plugin lifecycle. Developers can now remove plugins through the same API surface used to install them, with the CLI handling cache cleanup and config.toml updates automatically. This is particularly useful in multi-agent or CI environments where plugin sets are managed programmatically.

Curated Plugin Loading Fixed in TUI Sessions

The 0.113.0 release also fixed a bug where curated plugins were not being loaded in TUI sessions as expected. Curated plugins now load correctly at session startup, ensuring that marketplace-installed plugins are available immediately in interactive sessions without requiring a workaround.

Impact for Developers

The expanded plugin marketplace and lifecycle management in 0.113.0 marks a maturation of Codex CLI's extensibility model. What started as a config-file-based mechanism for loading custom skills and MCPs is now a structured ecosystem with discovery, authentication, and lifecycle management built in. For teams building Codex into development workflows, this lowers the operational overhead of managing plugin dependencies β€” particularly in environments where plugin sets change frequently.


Mentioned onGitHubReleasebot