Install agent plugins
On this page
Plugins give Codex or Claude additional skills and tools. You can install a plugin from a marketplace in the desktop app or approve one proposed by Codex in a conversation. Where the plugin is installed determines which devboxes will receive it.
If a service gave you an MCP server URL or setup command, follow Add MCP servers. For a Team Template member project, follow the member-project instructions below; the project-wide plugin page is unavailable there.
Find and install a plugin
- In the desktop app, select your project and open Integrations → Codex/Claude Plugins.
- Choose Load Template box state to load installed plugins and marketplace actions. This may wake your Template box.
- Choose Add plugin, then select the Codex or Claude tab.
- Search for a plugin in the configured marketplaces. To add another marketplace, paste its GitHub address and choose Add marketplace, then select a plugin from its results.
- Review the installation destination using the table below, then choose Install.
- Start a new session with the selected agent on the Template box and check that the plugin works, as described below. Complete any sign-in required by its tools.
- If it's a Template box install that you want in future devboxes, choose Snapshot Template box.
The destination shown before installation explains how the plugin will reach your machines:
| Destination | What to expect |
|---|---|
| Managed for this project | boxes.dev will keep the plugin installed on your Template box and devboxes. Sleeping devboxes will catch up after waking. No snapshot is needed. |
| Template box only | The plugin will be installed on your Template box. Choose Snapshot Template box afterward if future devboxes should inherit it. Existing devboxes will keep their own plugins. |
boxes.dev can manage supported plugins from verified public GitHub marketplaces across a project. Private or local sources, and plugins with components that need setup on each machine, remain local to the Template box. The installation preview will explain the reason.
To check that a plugin works, follow its usage instructions and ask the agent to perform one task the plugin supports. After installing an issue-tracker plugin, for example, ask the agent to find a known issue by its title.
A Template box snapshot can include a plugin's configuration, saved data, and sign-in material. It does not guarantee that a tool inside the plugin is authorized on a new devbox. After creating a devbox, start an agent session there and check the plugin's tools.
Paste a native plugin command
The Add plugin input also accepts a GitHub marketplace address such as
https://github.com/owner/repo (with or without https://), or one of these
commands:
codex plugin marketplace add <url>
claude plugin marketplace add <url>
codex plugin add NAME@MARKETPLACE
claude plugin install NAME@MARKETPLACE
A command naming Claude will be handled for Claude even on the Codex tab. A bare marketplace address will use the selected tab. A command naming a plugin will open that plugin directly for review.
If adding a marketplace fails, the dialog will keep your pasted text and show the agent's error so you can correct it and retry.
If the Template box needs an update before it can use this dialog, the page will show the native command you can run in a Template box terminal or agent session.
Update or remove a plugin
Use a plugin row's actions to enable, disable, update, or remove it where supported. A managed plugin stays at the commit boxes.dev verified when it was installed or last updated. Choose Check for update, where offered, to check for and install a newly verified version.
A Managed for this project change will reach the project's machines without a snapshot. For a Template box change, take a new snapshot if future devboxes should inherit it. Start a new agent session after a change.
A supported public GitHub plugin already installed on the Template box can offer Manage for this project after boxes.dev verifies its source. Choose that action if you want boxes.dev to keep that version installed across the project. Removing a Claude plugin will keep its saved data.
The page also has two read-only sections when relevant:
- Synced by Codex lists plugins whose availability Codex manages for your account and workspace. They do not need a Template box snapshot; start a new Codex session to pick up changes.
- Seen only on devboxes lists plugins last reported by individual devboxes. Opening or refreshing the page will not inspect or wake those devboxes.
Install from a conversation
When Codex proposes a plugin, review the card's destination before approving:
- Install in Codex is for plugins Codex syncs to your account.
- Install on Template box or Install plugin installs a native plugin on the machine named in the card.
After a native install, an eligible public GitHub plugin will automatically become managed for the project. An unsupported source will stay on that machine. If you want a native-only plugin in future devboxes, install it on the Template box and save a snapshot.
Project setup can import supported agent configuration from your computer, but it does not copy plugin bundles or marketplace registrations. Install the plugins you need on boxes.dev.
Use plugins in a member project
Member projects do not have the project-wide plugin page because they have no personal Template box. Ask your agent to install a plugin on the current devbox with its native tools, or ask your team admin to add it to the shared Team Template. A native install on a member devbox stays on that devbox.