Codex desktop app hides Plugins UI while plugin runtime and CLI marketplace are available #16783

Activity

1. Pavel-Sennikov

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on Apr 4, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   skillsIssues related to skillsIssues related to skills

   on Apr 4, 2026
3. github-actions commented on Apr 4, 2026

   

   github-actionsbot

   on Apr 4, 2026 – with GitHub Actions

   Contributor

   More actions

   Potential duplicates detected. Please review them and close your issue if it is a duplicate.

   • Plugins not show, only show skills #16298
   • Plugins briefly appear on launch, then disappear after Codex finishes loading #16133
   • Codex App briefly shows 'New Plugin' then falls back to 'Skills' after startup #16006
   • Codex App dont find plugins #15962

   Powered by Codex Action
4. DmitriiSid commented on Jun 1, 2026

   

   DmitriiSid

   on Jun 1, 2026

   More actions

   Additional integration context from a third-party desktop companion app.

   We are evaluating a Codex integration comparable to existing Claude Code and OpenCode integrations. Codex CLI appears to have the necessary plugin/hook primitives for installing a local companion plugin, but Codex Desktop plugin discoverability is important for this class of integration.

   Current companion pattern:

   • installer copies agent-specific integration files into the user-level agent plugin/config location
   • agent plugin/hook opens a local desktop companion window through a custom URL scheme
   • plugin/hook exchanges request/response files or SDK calls with the companion app
   • settings UI shows one install command per supported agent

   For Codex, the preferred path would be a first-class Desktop-visible plugin install/management surface that can show and manage the same local plugin used by CLI. Without Desktop plugin UI parity, users can install/use the CLI integration but cannot verify or manage it from the Codex Desktop app, which makes the Desktop story feel incomplete for third-party companions.

   Useful Desktop behavior for this use case:

   • show installed local/third-party plugins, not only curated marketplace plugins
   • expose plugin status/trust/errors for hooks and MCP servers bundled by a plugin
   • document whether Desktop and CLI share the same plugin directory/runtime contract

   This is separate from marketplace discovery: even a local plugin installed by a companion app needs a discoverable Desktop management surface.
5. neo-picasso-2112 commented on Jul 10, 2026

   

   neo-picasso-2112

   on Jul 10, 2026

   More actions

   yeah having the same issue here
6. etraut-openai commented on Aug 5, 2026

   

   etraut-openai

   on Aug 5, 2026

   Contributor

   More actions

   Desktop now exposes plugin browsing, details, install links, and state.
7. etraut-openai

   closed this as completedon Aug 5, 2026