Cmd. /plugins

Purpose

Browse installed and discoverable Codex plugins.

/plugins

Availability

The installed command menu and account or organization settings determine availability.

Examples

/plugins

When to use it

1. Check whether team-standard plugins synced correctly on a new machine.
2. Before installing or removing a work-specific plugin, review current state and auth/setup requirements.
3. Use /hooks after enabling plugin-bundled hooks to verify lifecycle behavior.

Choosing related commands

Effects and persistence

Browses and manages plugins. Installation and activation can change the tools or skills available.

/plugins opens the plugin browser so you can inspect installed and discoverable plugins, review capabilities, install suggested plugins, or toggle installed plugin state. In team operations, it is also the entry point for plugin supply, sharing, source policy, and bundled hook review.

Changes

• Plugins became a first-class workflow with startup sync and clearer auth/setup handling.
• The /plugins browser became the place to start plugin discovery, install, and removal flows.

to v0.125.0 Changes

• codex marketplace add supports GitHub, git URLs, local directories, and direct marketplace.json URLs, expanding how organizations manage plugin sources.
• The plugin workflow grew into tabbed browsing, inline enable/disable toggles, marketplace removal, and remote, cross-repo, and local sources.
• In practice, /plugins is no longer only an install menu. It is also the operational entry point for deciding which marketplaces and sources an organization allows.
• 0.124.0 added remote plugin marketplace list/read support, making source inspection clearer.
• 0.125.0 expanded app-server plugin management with remote plugin installation and marketplace upgrade flows.

to v0.130.0 Changes

• Workspace sharing, share access controls, source filtering, local share path tracking, marketplace removal/upgrades, and remote bundle sync made /plugins a team distribution control surface.
• Plugin details can show bundled hooks, so teams can see lifecycle behavior before trusting a plugin.
• Share-link metadata and discoverability controls make public and internal sharing boundaries clearer.

to v0.139.0 Changes

• 0.131.0 added plugin marketplace CLI commands, version-aware sharing, share checkout, and clearer shared-workspace buckets.
• 0.133.0 improved marketplace-aware list output, installed versions, visible marketplace roots, and remote collection support.
• 0.137.0 added codex plugin list --json and cached remote catalog suggestions, making plugin inventory easier to audit automatically.
• 0.138.0 added --json output for plugin add/remove and marketplace commands, and plugin detail data can expose default prompts, remote MCP servers, and unavailable app templates.
• In the 0.138.0~0.139.0 baseline, codex plugin list --available --json includes uninstalled marketplace plugins, and JSON entries can include marketplaceSource.
• In the 0.139.0 baseline, marketplace operations should be treated together with install/upgrade flows and should log selected marketplaces, upgraded roots, and errors.

to v0.142.0 Changes

• Plugin organization improved in 0.140.0, making installed, discoverable, and source-grouped plugins easier to inspect.
• In 0.142.0-era runbooks, plugin inventory checks should be paired with /usage and rollout token-budget checks because plugins can materially increase agent and multi-agent activity.
• After changing marketplace sources or plugin enablement, re-check /mcp, /apps, and /debug-config so the actual tool surface and config layers are clear.

to v0.144.0 Changes

• Remote plugins are enabled by default; deploy marketplace/source policy before relying on the new default.
• npm marketplace sources and visible local/remote versions make version-drift checks explicit.
• Remote executor skill loading is faster in 0.144.0 because plugin namespaces are resolved once per root.

Cautions

In 0.145.0–0.146.0, audit Agent Plugin manifests and workspace-published artifacts, refresh source allowlists for the additional marketplaces, and re-check MCP/App tools after plugin changes.

• Treat plugin installation as a trust and supply-chain decision.
• Installation alone does not guarantee the actual tool surface is available; cross-check /mcp, /apps, and explicit $mentions.
• Treat plugins with bundled hooks as security/platform review candidates because they can alter the session lifecycle.
• CI and audit scripts should consume codex plugin list --json and codex plugin marketplace list --json rather than scraping the interactive /plugins UI.

Official sources

• Developer Commands
• Rust V0.117.0
• Changelog

Complete command list · Verification scope · History for this command