Urgent.News

What's breaking now, across thousands of outlets.

Tech

Why your Codex plugin doesn't show up: a plugin.json checklist

Disclosure: I run PickAPlugin , an independent catalog of ChatGPT and Codex plugins. This is adapted from our guide on the same topic. Codex is pretty quiet when a manifest is wrong. The plugin just doesn't show up, and there's no error to chase. Here's what the manifest needs and the mistakes that trip people up most. What it needs name : kebab-case ( my-plugin , not My Plugin ). It's the id.…

Codex plugins often fail to appear in the platform due to issues with their manifest file, plugin.json. This critical file contains essential information about the plugin, and any errors in its structure or content can prevent the plugin from being recognized and displayed.

The manifest must follow specific guidelines, including the use of kebab-case for the plugin's name (e.g., "my-plugin" instead of "My Plugin"). The version should adhere to semantic versioning (semver), such as "0.1.0". A concise description of what the plugin does for the user is also required.

The manifest should be located at .codex-plugin/plugin.json, and it's the only file that should reside in this designated folder. Additional components like skills, .mcp.json, and hooks should be placed at the root of the plugin itself.

Common errors include using paths that don't start with "./" or absolute paths like "/Users/me/...", which can confuse the system. Paths containing ".." that point outside the plugin's directory are also problematic. Furthermore, marketplace entries should not omit important fields such as "source" or "policy". Storing sensitive information directly in the manifest is discouraged; instead, environment variables should be utilized to manage such data securely.

To ensure the manifest is correctly formatted, the author recommends using a free plugin.json validator, which can be accessed via a web browser without uploading any data. This tool flags errors, warnings, and optional enhancements. Additionally, it validates the marketplace.json file to ensure consistency across the plugin's metadata.

While OpenAI provides documentation on the necessary fields for the plugin.json file, the author also mentions an alternative schema maintained at agent-plugins.org, which can be referenced using the $schema directive within the manifest. For a comprehensive guide on validating and troubleshooting plugin.json files, the author directs readers to pickaplugin.com/guides/validate-plugin-json.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

How to send email without exposing your email provider's API key

To send email without exposing your email provider's API key, keep the key encrypted and only decrypt it inside the code that sends the email.

  • Encrypt API key inside code using Lit wallet
  • Create Lit Action to decrypt key and send email
  • Store ciphertext, remove action from wallet group

More from Monday 16 November →