Plugins
A Claude Code plugin bundles skills, subagents, hooks and MCP servers. Plugins are published in a
marketplace: a folder or git repository with a .claude-plugin/marketplace.json. Repave installs
them the way Claude Code does, and you choose who gets each one: your project's agents, your
developers in the Repave IDE, or both.
Open Plugins under Management in the project sidebar. An administrator manages the plugins every project gets under Admin → Plugins.
Adding a marketplace
Choose Add marketplace, then one of:
- Git repository —
owner/repofor GitHub, or anyhttps://git URL. Give a Branch or tag to follow one other than the default, and an Access token for a private repository. The token is stored encrypted and never shown again. - Hosted file — the URL of a
marketplace.jsonwhose plugins come from git, npm or an archive. - Upload zip — a zipped marketplace folder, up to 50 MB, for a server that can't reach a git host. To update it, upload the new zip: it replaces the one with the same name.
A marketplace your project adds is for your project only. One an administrator adds is listed in every project, marked For all projects, and only an administrator can refresh or remove it.
An access token is only sent over https://.
Each marketplace lists its plugins. A plugin Repave can't install says why, for example Can't be installed: Repave doesn't run marketplace commands. Repave also checks each plugin with Claude Code before installing it, and refuses one Claude Code would not load, with Claude Code's reason.
Installing a plugin
Choose Install next to a plugin, then:
- Who uses it — Agents and developers: every agent run in the project loads the whole plugin, its skills, subagents, hooks and MCP servers, and developers get it in the Repave IDE too. Developers: only the project's Repave IDE sessions get it.
- Update automatically — off unless you tick it. See Updates.
- Any option the plugin can't run without, such as an API token.
Installing a plugin also installs the plugins it depends on, marked Installed for the plugin that needs them, and so does an update that adds one. Uninstalling it removes those that nothing else needs.
An administrator can't install a plugin for every project while a project has its own copy of it; the project uninstalls its copy first.
A plugin runs code in agent runs and Repave IDE sessions, with their files, shell and network. Only install plugins you trust. A plugin that needs the internet does not work on a server that can't reach it.
Changing an installed plugin
- Who uses it can be changed at any time, or set to Off to keep the plugin and its options without loading it anywhere.
- Configure changes the plugin's options. Emptying an option clears it. A secret option shows only that it is set; leave it empty to keep it, or type a new value to replace it.
- Details lists what the plugin holds and about how many tokens it adds to every turn.
- ⋯ → Uninstall removes it and its saved data.
A change reaches agent runs that start after it. An open Repave IDE session gets it without a restart:
Claude Code says the project's plugins changed, and /reload-plugins loads them. Codex in the Repave IDE
gets a plugin's skills.
A plugin can also say:
- Needs configuration — an option it requires has no value yet.
- Failed to load in the last agent run — with the reason. It clears when a later run loads it.
- Removed from its marketplace — it keeps working, but can't be updated.
- Blocked by your admin — no agent run or session loads it.
Updates
An installed plugin stays on the version you installed. Repave checks every git and hosted marketplace
each hour, and Refresh checks one now. When a plugin has a newer version, it shows the version
available and an Update button. A plugin set to Update automatically takes each new version at
the check. A plugin that sets a version in its plugin.json updates only when that version changes.
If a check fails, the marketplace says Last refresh failed with the reason, and its plugins keep working at the version they had.
For administrators
Under Admin → Plugins an administrator:
- adds marketplaces every project sees, and installs plugins for every project. A project lists those as Installed for all projects and can't change or uninstall them.
- sets Allowed sources: once any are listed, projects can add marketplaces only from those, such as
github.com/acme/*, oruploadfor zip uploads. With none listed, any source can be added. The list also covers where a project's marketplace fetches its plugins from (registry.npmjs.org/<package>for an npm package). Marketplaces already added keep working. - uses Block on a plugin, so no project can install it and no agent run or session loads it. Unblock undoes it.
Who can change plugins
Everyone on the project can open the Plugins page. Only the project's owner and editors see the controls that add marketplaces and install or change plugins.