Add a marketplace file at `$REPO_ROOT/.agents/plugins/marketplace.json`
and store your plugins under `$REPO_ROOT/plugins/`.
**Repo marketplace example**
Step 1: Copy the plugin folder into `$REPO_ROOT/plugins/my-plugin`.
```bash
mkdir -p ./plugins
cp -R /absolute/path/to/my-plugin ./plugins/my-plugin
```
Step 2: Add or update `$REPO_ROOT/.agents/plugins/marketplace.json` so
that `source.path` points to that plugin directory with a `./`-prefixed
relative path:
```json
{
"name": "local-repo",
"plugins": [
{
"name": "my-plugin",
"source": {
"source": "local",
"path": "./plugins/my-plugin"
},
"policy": {
"installation": "AVAILABLE",
"authentication": "ON_INSTALL"
},
"category": "Productivity"
}
]
}
```
Step 3: Restart Codex and verify that the plugin appears.
Add a marketplace file at `~/.agents/plugins/marketplace.json` and store
your plugins under `~/.codex/plugins/`.
**Personal marketplace example**
Step 1: Copy the plugin folder into `~/.codex/plugins/my-plugin`.
```bash
mkdir -p ~/.codex/plugins
cp -R /absolute/path/to/my-plugin ~/.codex/plugins/my-plugin
```
Step 2: Add or update `~/.agents/plugins/marketplace.json` so that the
plugin entry's `source.path` points to that directory.
Step 3: Restart Codex and verify that the plugin appears.
The marketplace file points to the plugin location, so those directories are
examples rather than fixed requirements. Codex resolves `source.path` relative
to the marketplace root, not relative to the `.agents/plugins/` folder. See
[Marketplace metadata](#marketplace-metadata) for the file format.
After you change the plugin, update the plugin directory that your marketplace
entry points to and restart Codex so the local install picks up the new files.
### Share a local plugin with your workspace
After you create a plugin and add it to Codex, you can share it with other
members of your ChatGPT workspace from the Codex app.
1. Open **Plugins** in the Codex app.
2. Go to **Created by you** and open the plugin details page.
3. Select **Share**.
4. Add workspace members or copy a share link.
5. Choose who has access, then send the invitation or link.
People you share with can find the plugin under **Shared with you** in the
plugin directory. Sharing a local plugin with your workspace doesn't publish
it to the public Plugin Directory. Shared plugins stay within your workspace
and organization boundary; accounts that aren't signed in to that workspace
can't access them. Use a marketplace when you want repo or CLI distribution,
and use workspace sharing when you want selected teammates to install a plugin
from the Codex app.
Workspace admins can disable plugin sharing from cloud-managed requirements by
adding `plugin_sharing = false` to `requirements.toml`:
```toml
plugin_sharing = false
```
### Marketplace metadata
If you maintain a repo marketplace, define it in
`$REPO_ROOT/.agents/plugins/marketplace.json`. For a personal marketplace, use
`~/.agents/plugins/marketplace.json`. A marketplace file controls plugin
ordering and install policies in Codex-facing catalogs. It can represent one
plugin while you are testing or a curated list of plugins that you want Codex
to show together under one marketplace name. Before you add a plugin to a
marketplace, make sure its `version`, publisher metadata, and install-surface
copy are ready for other developers to see.
```json
{
"name": "local-example-plugins",
"interface": {
"displayName": "Local Example Plugins"
},
"plugins": [
{
"name": "my-plugin",
"source": {
"source": "local",
"path": "./plugins/my-plugin"
},
"policy": {
"installation": "AVAILABLE",
"authentication": "ON_INSTALL"
},
"category": "Productivity"
},
{
"name": "research-helper",
"source": {
"source": "local",
"path": "./plugins/research-helper"
},
"policy": {
"installation": "AVAILABLE",
"authentication": "ON_INSTALL"
},
"category": "Productivity"
}
]
}
```
- Use top-level `name` to identify the marketplace.
- Use `interface.displayName` for the marketplace title shown in Codex.
- Add one object per plugin under `plugins` to build a curated list that Codex
shows under that marketplace title.
- Point each plugin entry's `source.path` at the plugin directory you want
Codex to load. For repo installs, that often lives under `./plugins/`. For
personal installs, a common pattern is `./.codex/plugins/