Stop Downloading ZIPs: The Correct Way to Install Codex Plugins

Plugins bundle skill descriptions, external service connections, and interaction features together. Installing a plugin does not mean it is already connected to an external service ; some only provide skills while others require separate authorization. The installation path depends on whether you use the desktop app or the command line.

Desktop: Use the Plugins Entry

In the ChatGPT desktop sidebar, open Plugins , find the desired plugin, and review its description, included applications, required permissions, and setup steps. Click Install plugin when ready; if a Connect prompt appears, select the service to link and complete authorization. Some plugins need no external connection and work immediately after installation.

Do not hand over sensitive repositories just because a plugin shows "installed." First verify what data the plugin can access and whether it performs write operations. Test with a small task — for example, ask it to analyze a sample project's directory structure — observe which capabilities it invokes, and confirm the results meet expectations before adding it to your production workflow.

In a Codex task interface that supports plugins, open Sources → Use plugins and select the target plugin from the installed list. Button locations and capabilities may differ across environments; if the sidebar option is missing, check whether the current interface, plan, and workspace have plugin support enabled instead of relying on screenshots.

Command Line: Start with the Built-in Browser

If you use the Codex CLI, launch codex and enter /plugins to open the plugin browser. Read the plugin description fully before installing; for plugins that require an external application, complete the connection steps. Using the OpenAI Developers plugin as an example, the official path is: open /plugins, locate the plugin, choose install, connect to OpenAI Platform as needed, then start a new session to use it.

The "new session" step is specific to this plugin's installation example — do not assume all plugins require a computer restart. Also avoid copying installation commands from other tools directly into Codex CLI; similar names do not guarantee identical command syntax or plugin formats.

Installed but Not Working? Troubleshoot in Three Layers

Layer 1 — Visibility: The plugin directory's contents are influenced by plan, region, workspace role, and admin settings; just because someone else can install a plugin does not mean it will appear in your interface. Layer 2 — Connection: Installed and authorized are two separate states; if the external application requires login or approval, that step must be completed. Layer 3 — Invocation: In a supported task interface, select the plugin or explicitly instruct the model to use it for a specific task — simply asking "is it installed?" is not enough.

Remember the boundary: plugins cannot bypass the service provider's or workspace's permissions. If authorization fails, check the connection status and admin configuration; never paste tokens into unfamiliar pages to save time. The simplest reliable installation method is: pick the right plugin from the directory, review its permissions, complete any required connections, then verify it works with a small test task .