CLI /plugins browser does not show installed local plugins
Summary
In Codex CLI 0.142.0, the TUI /plugins browser shows Installed 0 of 7 available plugins, even though codex plugin list reports multiple OpenAI-curated plugins as installed and enabled from ~/.codex/config.toml.
Uploaded feedback thread: 019ef514-aaff-7cd2-8106-4c2f2ddb4790
Environment
- Codex CLI:
0.142.0 - Platform: macOS arm64
- Install method: npm
- Working directory when reproduced:
~/Projects/MLX-Community
Reproduction
- Start Codex CLI.
- Run
/pluginsin the TUI. - Observe the plugin browser output.
- In a shell, run
codex plugin list.
Observed behavior
The TUI /plugins browser shows only 7 available category/workspace-style plugins, such as:
- Creative Production
- Data Analytics
- Investment Banking
- Metabase
- Product Design
- Public Equity Investing
- Sales
It reports:
Installed 0 of 7 available plugins.
However, codex plugin list reports multiple plugins as installed and enabled, including:
canva@openai-curatedbox@openai-curatedcoderabbit@openai-curatedbuild-web-apps@openai-curatedcircleci@openai-curatedhugging-face@openai-curatedremotion@openai-curatedcodex-security@openai-curatedhyperframes@openai-curatedbuild-ios-apps@openai-curatedbuild-macos-apps@openai-curatedbuild-web-data-visualization@openai-curated
The same entries are enabled in ~/.codex/config.toml.
Expected behavior
The TUI /plugins browser should show the same installed/enabled plugin state as codex plugin list, or clearly distinguish the cloud/workspace plugin directory from the local CLI plugin registry.
Notes
This appears to be a source mismatch in the TUI plugin browser rather than a missing local installation. The installed plugin skills and MCP-backed tools are still available in the session.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗