Skip to content

Documentation Index

Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt Use this file to discover all available pages before exploring further.

Install and manage plugins

Install Claude Code plugins from a marketplace on any surface you use, choose an install scope, and update or remove them later.

Installing a plugin adds its skills, agents, hooks, and MCP servers to Claude Code on your machine.

This page is for anyone using plugins on their own machine or account, whether in the terminal, the desktop app, an IDE, or a cloud session: it covers installing, choosing a scope, adding marketplaces, and keeping plugins updated.

These cases are covered on other pages:

Start with Install a plugin. If someone sent you an install command whose @ name isn't claude-plugins-official, add that marketplace first.

Install a plugin

As an example, this section installs commit-commands from Anthropic's official marketplace, which adds commands for committing, pushing, and opening pull requests.

The same steps install any other plugin: substitute its name and its marketplace's name wherever commit-commands and claude-plugins-official appear. If that plugin comes from a different marketplace, add the marketplace first.

Pick the tab for where you run Claude Code.

Start Claude Code with claude in your project, then:

<Steps>
  <Step title="Open the plugin's details with the install command">
    Run `/plugin install` with the plugin's name and marketplace. In a session, this command doesn't install right away: it opens the `/plugin` panel on that plugin's details so you can review it and choose a scope first.

    ```text theme={null}
    /plugin install commit-commands@claude-plugins-official
    ```

    To browse instead, run `/plugin` with no plugin name: the panel opens on the **Discover** tab, which lists the plugins from your marketplaces, and you can type to search, then press **Enter** on a plugin to open its details.
  </Step>

  <Step title="Review what the plugin adds">
    The details pane shows the plugin's description. It can also show:

    * **Will install**: the commands, agents, skills, hooks, and MCP and LSP servers the plugin adds.
    * **Last updated**: shown for a plugin in Anthropic's official marketplace.
    * **Context cost**: for a plugin in Anthropic's official marketplace, two token estimates. **Every turn** is what the plugin adds to each message you send, and **When invoked** is what its skills and agents add once Claude loads them. The estimates appear when you open the plugin by naming its marketplace, as the step 1 command does, or from the **Marketplaces** tab. The details pane you reach from the **Discover** list doesn't show them.

    Plugins from a local or custom marketplace can show `Components will be discovered at installation` instead.

    A plugin can run hooks and MCP servers, so read the pane before you install. See [Plugin security and trust](/docs/en/plugins/security).
  </Step>

  <Step title="Choose a scope">
    Select one of the three install options:

    * **Install for you (user scope)**: you get the plugin in every project on this machine
    * **Install for all collaborators on this repository (project scope)**: it's enabled for everyone who works in this repository
    * **Install for you, in this repo only (local scope)**: you get it in this repository only

    [Choose an install scope](#choose-an-install-scope) says which settings file each one writes to and which applies when the same plugin is set at more than one.

    After you select a scope, Claude Code installs the plugin along with any dependencies it declares, then prints an install summary.
  </Step>

  <Step title="Read the install summary">
    The last sentence of the summary tells you whether the plugin is usable in this session yet:

    * **Active now**: `Plugin is now active.` No reload is needed.
    * **Active, but a server needs setup**: `Plugin is now active.` is followed by `Its bundled MCP server needs configuration before it can start`. The plugin's [bundled MCP server](/docs/en/plugins/components#include-a-packaged-mcpb-server) can't start until you set its options. Select the plugin on the **Installed** tab in `/plugin` and choose **Configure** to set the server's options.
    * **Reload needed**: `Run /reload-plugins to activate.` The panel closes and Claude Code runs that reload for you. If the reload would [invalidate the prompt cache](/docs/en/prompt-caching#enabling-or-disabling-a-plugin), it warns and leaves the plugin pending instead. Run `/reload-plugins --force` to activate it anyway, which costs one uncached request.
    * **Load failed**: `The plugin couldn't be loaded`. Open the **Errors** tab in `/plugin` for the reason, then see [After install: plugin not working](/docs/en/plugins/troubleshooting#plugin-installed-but-not-working).
  </Step>

  <Step title="Confirm the plugin works">
    Type `/` and look for the plugin's skills under its name, in the form `/<plugin>:<skill>`. For `commit-commands`, `/commit-commands:commit` appears. Two other places list the plugin too:

    * Open the **Installed** tab in `/plugin`, which lists the plugin with its scope.
    * In your shell, run `claude plugin list`, which prints the same list with `Version`, `Scope`, and `Status` lines.

    If `/commit-commands:commit` doesn't appear, see [After install: plugin not working](/docs/en/plugins/troubleshooting#plugin-installed-but-not-working).
  </Step>
</Steps>

Installing from any other marketplace requires one extra step first: [add the marketplace](#add-a-marketplace). Claude Code adds Anthropic's official marketplace for you the first time you start an interactive terminal session, which is why the example skips that step. If you found a plugin on [claude.com/marketplace](https://claude.com/marketplace), its **Claude Code** button copies the install command in its [shell form](#install-from-your-shell), `claude plugin install <name>@claude-plugins-official`.

In a local or SSH session in the desktop app's Code tab:

<Steps>
  <Step title="Open the plugin browser">
    Click the **+** button next to the prompt box and select **Plugins**, then **Add plugin**. The plugin browser opens with the plugins from your marketplaces.
  </Step>

  <Step title="Select the plugin">
    Find `commit-commands` and select it.
  </Step>

  <Step title="Choose a scope">
    Choose a [scope](#choose-an-install-scope): your user account, this project, or local-only.
  </Step>
</Steps>

To enable, disable, or uninstall later, use **+ > Plugins > Manage plugins**. The plugin browser isn't available in the desktop app's cloud sessions. See [Install plugins in the desktop app](/docs/en/desktop#install-plugins).

In the Claude Code panel in VS Code:

<Steps>
  <Step title="Open Manage plugins">
    Type `/plugins` in the prompt box to open **Manage plugins**.
  </Step>

  <Step title="Install the plugin">
    On the **Plugins** tab, search for `commit-commands` and click **Install**. If the tab lists no plugins, add `anthropics/claude-plugins-official` on the **Marketplaces** tab first.
  </Step>

  <Step title="Choose a scope">
    Choose a [scope](#choose-an-install-scope): **Install for you**, **Install for this project**, or **Install locally**.
  </Step>
</Steps>

Your changes apply to open sessions without a restart. See [Manage plugins in VS Code](/docs/en/vs-code#manage-plugins).

A cloud session, including the browser at claude.ai/code, has no plugin browser and doesn't load the plugins you installed on your own machine or the ones your repository's .claude/settings.json turns on. For plugins your organization distributes through managed settings, see Manage plugins for your organization.

See [which parts of your setup are also available in a cloud session](/docs/en/cloud-environments#what-carries-over-from-your-setup) for the rest of your setup.

Choose an install scope

A plugin's install scope decides who gets the plugin and which settings file records it as enabled:

  • User scope: the plugin is enabled for you in every project on this machine. The entry goes in enabledPlugins in ~/.claude/settings.json.
  • Project scope: the plugin is enabled for everyone who works in this repository. The entry goes in .claude/settings.json, which you commit. Committing that entry turns the plugin on for your collaborators but doesn't download it to their machines, so each collaborator also runs claude plugin install <name>@<marketplace> --scope project once; see Enabled in project settings but not installed.
  • Local scope: the plugin is enabled for you in this repository only. The entry goes in .claude/settings.local.json.

Some plugins are set by their author to start turned off, through the defaultEnabled field. Such a plugin is installed but stays off until you turn it on with claude plugin enable <name> in your shell, or from the Installed tab of /plugin in a session.

When the same plugin is set at several scopes, the local setting overrides the project setting, and the project setting overrides the user setting. See Find where a plugin is enabled for the full rule.

The terminal, the desktop app's local sessions, and the VS Code extension on one computer read the same settings files, so a plugin you install at user scope in any of them is available in the other two.

JetBrains, non-interactive runs, and the Agent SDK

Some places you run Claude Code have no plugin browser of their own:

  • JetBrains IDEs: the JetBrains plugin runs Claude Code in the IDE's terminal, so use the Terminal tab's steps there.
  • claude -p and other non-interactive runs: /plugin doesn't run, and Claude replies /plugin isn't available in this environment. Plugins you already installed do load. Install and manage them from your shell with claude plugin commands.
  • Agent SDK: load plugins through the SDK's plugin option. See Load plugins in the Agent SDK.

If Claude Code reports that a plugin enabled in the repository's .claude/settings.json isn't installed, see Enabled in project settings but not installed.

If you're a plugin author testing a copy of your plugin on disk, start Claude Code from your shell with --plugin-dir to load it for one session instead of installing it. See Flags that load a plugin for one session.

Plugins from your claude.ai account

Your claude.ai account is a separate source of plugins, alongside the marketplaces you install from:

  • What arrives: every plugin you turn on for your claude.ai account, and every plugin your organization turns on for its members. In a terminal session they sync in the background each time you start Claude Code while signed in with that account; in Cowork sessions they download when the session starts.
  • Where you see them: in /plugin and claude plugin list under the ID <name>@synced. You can turn one off at your own scope unless your organization requires it.
  • What doesn't go the other way: plugins you install with /plugin or claude plugin install stay on this machine and aren't added to your claude.ai account.

For sync timing, sign-in requirements, and turning sync off, see Plugins synced from claude.ai.

Install from your shell

Run claude plugin install in your shell to install a plugin without starting a Claude Code session, for example from a setup script.

  • Scope: user scope by default. Pass --scope project or --scope local to change it.
  • When the plugins load: plugins it installs load the next time you start Claude Code, or when you run /reload-plugins in a session that's already open.
  • The marketplace must be added first: on a machine where no one has opened an interactive Claude Code session yet, the official marketplace isn't registered, so a script that installs from it runs claude plugin marketplace add anthropics/claude-plugins-official before the install.

```bash theme={null} claude plugin install formatter@your-org --scope project 

The command prints `Successfully installed plugin: formatter@your-org (scope: project)` when it finishes.

Some plugins install by running a command that their marketplace names, called a [`command` source](/docs/en/plugins/marketplace-reference#command-plugin-source). Claude Code shows you that command and asks you to accept it before it runs. A script has no one to answer that prompt, so pass `--yes` there to accept it.

For every `claude plugin install` flag, see [plugin install](/docs/en/plugins/cli-reference#plugin-install).

## Add a marketplace

You only need this section when the plugin you want isn't in Anthropic's official marketplace, for example one a coworker published or one from Anthropic's community marketplace.

A marketplace is a catalog of plugins, and Claude Code has to know about a marketplace before you can install from it. You add a marketplace once. After that, its plugins appear on the **Discover** tab and install with `/plugin install <plugin>@<marketplace>` in a session or `claude plugin install <plugin>@<marketplace>` in your shell, where `<marketplace>` is the name the marketplace registered under. To do both in one step, see [Add a marketplace and install in one command](#add-a-marketplace-and-install-in-one-command).

In a Claude Code session, run `/plugin marketplace add` followed by the marketplace's source: a GitHub repository, a git repository on any host, a local directory or file, or a hosted `marketplace.json`.

| Source | What you type | Example |
| :- | :- | :- |
| GitHub repository | `owner/repo`. Add `#ref` to pin a branch or tag. | `/plugin marketplace add anthropics/claude-code`, or `/plugin marketplace add your-org/plugins#v1.2.0` to pin the `v1.2.0` tag |
| Git repository on any host | The full clone URL. Add `#ref` to pin a branch or tag. | `/plugin marketplace add https://gitlab.example.com/your-group/your-marketplace.git#v1.0.0` |
| Local directory or file | A relative or absolute path to a directory that holds `.claude-plugin/marketplace.json`, or to the JSON file itself. Start a relative path with `./` or `../`, because Claude Code reads a bare `name/name` as a GitHub repository. | `/plugin marketplace add ./my-marketplace` |
| Hosted `marketplace.json` | Its `https://` URL | `/plugin marketplace add https://example.com/marketplace.json` |

From your shell, `claude plugin marketplace add` takes the same sources.

<Tip>
  `/plugin market` also works as a shorter form of `/plugin marketplace`.
</Tip>

Include the `https://` prefix on every URL, or use the `git@host:path` form for SSH. If you type a bare `gitlab.example.com/your-group/your-marketplace.git`, Claude Code reads it as GitHub `owner/repo` shorthand and rejects it.

When the command succeeds, it prints `Successfully added marketplace: <name>`, and the marketplace's plugins appear on the **Discover** tab the next time you open `/plugin`, with no reload needed. If it fails, match the error message in [Troubleshoot plugins](/docs/en/plugins/troubleshooting#add-a-marketplace).

### Add a marketplace and install in one command

To install a plugin from a marketplace you haven't added yet, run `/plugin install` in a Claude Code session and name the marketplace source with `--marketplace`. Requires Claude Code v2.1.275 or later.

```text theme={null}
/plugin install deploy-helper --marketplace your-org/plugins

The source takes the same forms as /plugin marketplace add, such as GitHub owner/repo, a git URL, or a local path, except that it can't contain spaces. Give the plugin name by itself, without an @marketplace suffix.

If you haven't added that marketplace yet, Claude Code shows the source it resolved and asks you to confirm before adding it. Once the marketplace is added, the plugin's details open and you choose an installation scope. If the source matches a marketplace you've already added, Claude Code skips the confirmation and opens the plugin's details in that marketplace.

Add a private marketplace

A private marketplace is one in a repository you need credentials to clone, on GitHub or any other git host. You add it with the same /plugin marketplace add or claude plugin marketplace add command as a public one. Claude Code clones it with the git credentials already on your machine and never prompts, so each way of connecting has a requirement:

  • HTTPS: your git credential helpers apply, so access you set up with gh auth login, the macOS Keychain, or git-credential-store works. Interactive prompts are suppressed, so a host you have never authenticated to fails instead of asking for a password.
  • SSH: the host must already be in your known_hosts file and the key must work without a passphrase prompt. If your git setup names an SSH program in GIT_SSH_COMMAND, GIT_SSH, or your git config's core.sshCommand, Claude Code runs that program.
  • GitHub owner/repo shorthand: Claude Code checks whether your SSH key authenticates to github.com, then clones over SSH if it does and over HTTPS if it doesn't. Set CLAUDE_CODE_PLUGIN_PREFER_HTTPS=1 to skip that check and always clone over HTTPS.

The same credentials apply when you run /plugin install, /plugin marketplace update, and claude plugin update.

On a GitHub Enterprise Server host, see Plugin marketplaces on GHES for the credentials each operation needs.

If your organization registers the marketplace for you through managed settings, you don't add it yourself. See Pre-install and require plugins.

Add a marketplace from claude.ai

In terminal sessions where plugins sync from your claude.ai account, claude.ai can also list plugin marketplaces for you, such as your organization's plugin library and your own claude.ai uploads. You add one of these by its name rather than by a source. Adding a marketplace from claude.ai requires Claude Code v2.1.273 or later.

Add a claude.ai marketplace from the /plugin panel or from your shell:

  • Inside a session: run /plugin and go to the Marketplaces tab, which lists the marketplaces from claude.ai. Select one there to add it.
  • From your shell: run claude plugin marketplace list, which prints them in a From claude.ai: section. Then run claude plugin marketplace add with the --claudeai flag and the name shown in the list.

For example, this command adds a marketplace named claudeai-organization-library:

```bash theme={null} claude plugin marketplace add --claudeai claudeai-organization-library 

Claude Code registers the marketplace under a local name that starts with `claudeai-`, derived from the name that claude.ai lists it under. For example, a marketplace listed as "Organization library" becomes `claudeai-organization-library`. Install its plugins by that name, for example with `claude plugin install <plugin>@claudeai-organization-library`.

If you sign out, or sign in to a different claude.ai organization, the marketplace stays configured but shows no plugins, and the plugins you already installed from it keep loading.

The `From claude.ai:` section can also list git-based marketplaces shared through claude.ai, and it prints a source for each of those. Add them by that source as in [Add a marketplace](#add-a-marketplace), not with `--claudeai`.

## Manage installed plugins

The **Installed** tab in `/plugin` lists your plugins with actions to enable, disable, update, or uninstall each one. In a Claude Code session, run `/plugin` and press **Tab** to reach it, or run `/plugin enable`, `/plugin disable`, or `/plugin uninstall` to open the panel and make that change there. Disabled plugins are grouped under a collapsed header at the bottom of the list. Use these keys on the list:

* Type to filter by name or description.
* Press **Space** to enable or disable the selected plugin, and **f** to favorite it.
* Press **Enter** to open a plugin's details.

A plugin's details menu offers **Disable plugin** or **Enable plugin**, **Update now**, and **Uninstall**. Two more items appear for plugins that take settings, and a plugin can show both:

* **Configure options**: shown when the plugin's manifest declares [`userConfig` options](/docs/en/plugins/manifest-reference#user-configuration). Opens the dialog for those options
* **Configure**: shown when the plugin includes a [bundled MCP server](/docs/en/plugins/components#include-a-packaged-mcpb-server). Sets that server's own `user_config` settings

The tab can also show plugins at **Managed** scope. Your organization installed those through [managed settings](/docs/en/settings#settings-files), and you can't enable, disable, or uninstall them here.

For a synced plugin that your organization requires on claude.ai, see [Manage plugins synced from claude.ai](#manage-plugins-synced-from-claude-ai).

When you close the `/plugin` panel with pending changes you made in it, Claude Code runs `/reload-plugins` for you to apply them. If the reload would [invalidate the prompt cache](/docs/en/prompt-caching#enabling-or-disabling-a-plugin), it warns and leaves the changes pending instead. Run `/reload-plugins --force` to apply them anyway.

### Manage plugins synced from claude.ai

The **Installed** tab in `/plugin` also lists the [plugins synced from your claude.ai account](/docs/en/plugins/loading#synced-plugins), with `synced` as their source. Synced plugins appear in terminal sessions on Claude Code v2.1.273 or later.

* **Enable or disable**: use the **Installed** tab, unless your organization marked the plugin as required.
* **Remove**: turn the plugin off on claude.ai.

When Claude Code syncs an added, updated, or removed plugin into an interactive session, you see `Plugins changed. Run /reload-plugins to activate.` Run `/reload-plugins` to load the change in that session, or leave it for the next time you start Claude Code.

### Uninstall a plugin the project enables

When you choose **Uninstall** for a plugin that this repository's `.claude/settings.json` enables, whether from the **Installed** tab or with `/plugin uninstall`, Claude Code asks whether to disable it for you or uninstall it for everyone:

* **Disable for me**: press **y**. Claude Code writes `false` for the plugin in your `.claude/settings.local.json` and leaves it installed for the project.
* **Uninstall for everyone**: press **u**. Claude Code removes the plugin from the shared `.claude/settings.json`.

### See what an installed plugin adds to your sessions

In your shell, run `claude plugin details <name>` for an installed plugin. The `Always-on` line is the number of tokens the plugin adds to every session where it's enabled, and the per-component rows show which skill or agent contributes most. For the full output and what each figure means, see [Measure what a plugin costs](/docs/en/plugins/measure#measure-what-a-plugin-costs).

### Find plugins you no longer use

On the **Installed** tab in `/plugin`, plugins you installed yourself and haven't used recently appear under a **Not used recently** header, and each plugin's details show a **Last used** line. Use that header and that line to find plugins that still add startup and context cost, then disable or uninstall them.

### Plugins with dependencies

A plugin can declare other plugins that it depends on. When you install, disable, or uninstall such a plugin from a marketplace, Claude Code acts on those dependencies too:

* **Install**: Claude Code also installs and enables the plugin's declared dependencies at the same scope. The success message lists them.
* **Enable**: Claude Code also enables the plugin's dependencies that are installed but disabled. If a declared dependency isn't installed, the enable fails and the message tells you to install it first.
* **Disable**: when another enabled plugin still needs the one you named, Claude Code refuses and prints a chained command that disables both in the right order.
* **Uninstall**: auto-installed dependencies stay until you run `claude plugin prune` in your shell; see [plugin prune](/docs/en/plugins/cli-reference#plugin-prune).

If you loaded the plugin with `--plugin-dir` instead, see [Test a plugin and its dependency locally](/docs/en/plugins/dependencies#test-a-plugin-and-its-dependency-locally).

### Manage plugins from your shell

You can also manage plugins without starting a Claude Code session. In your shell, run `claude plugin install`, `enable`, `disable`, or `uninstall` as ordinary terminal commands; they change the same settings the `/plugin` panel does. Each takes `--scope` to target one scope, and uses a default scope when you omit it:

* `enable` and `disable` act on the most specific scope whose settings already list the plugin.
* `install` and `uninstall` act on user scope.

For example, these commands disable and re-enable a plugin, then uninstall it at project scope:

```bash theme={null}
claude plugin disable formatter@your-org
claude plugin enable formatter@your-org
claude plugin uninstall formatter@your-org --scope project

Keep plugins updated

Plugins update automatically when the marketplace they came from has auto-update turned on. After a session starts, Claude Code refreshes those marketplaces and updates the on-disk copies of the plugins you installed from them.

The running session keeps the versions it already loaded. After an update, you see Plugin updated: <name> ยท Run /reload-plugins to apply, and the next session loads the new versions automatically.

These are the auto-update defaults for each kind of marketplace:

  • On by default: claude-plugins-official and the other official marketplace names except knowledge-work-plugins and first-party-plugins, plus marketplaces added from claude.ai.
  • Off by default: every other marketplace, including the community marketplace, third-party marketplaces, and local development marketplaces.

For when auto-update runs, which plugins it skips, and the environment variables that turn it off, see When auto-update runs.

Turn auto-update on or off for a marketplace

In a Claude Code session, run /plugin and go to the Marketplaces tab. Select the marketplace, then select Enable auto-update or Disable auto-update.

Update plugins now

To update one plugin, open it on the Installed tab in /plugin during a session and select Update now, or run claude plugin update <plugin>@<marketplace> in your shell.

There's no command that updates every plugin at once. To update the plugins you installed from one marketplace at once, go to the Marketplaces tab in /plugin, select the marketplace, and choose Update marketplace. That refreshes the marketplace's listing, updates the plugins you installed from it, and reports any plugin it left for you to update yourself. A plugin with a command source or with a marketplace entry that sets a headersHelper command isn't updated this way, so you update it from its view on the Installed tab or with claude plugin update <plugin>@<marketplace>.

If you run claude plugin marketplace update in your shell with no name, it refreshes every marketplace's listing but leaves your installed plugins at their current versions.

Auto-update from a private marketplace

For a private marketplace, see What background auto-update does with credentials for how background auto-updates authenticate over SSH and HTTPS, and Troubleshoot plugins for the messages you see when they fail.

Manage marketplaces

The Marketplaces tab in /plugin lists every marketplace you registered, along with its source. Select one to browse its plugins, update its listing, turn auto-update on or off, or remove it.

You can also list, update, and remove marketplaces with commands, from your shell or inside a session:

Action In your shell Inside a session
List marketplaces claude plugin marketplace list /plugin marketplace list
Update a marketplace's listing claude plugin marketplace update <name> /plugin marketplace update <name>
Remove a marketplace claude plugin marketplace remove <name> /plugin marketplace remove <name>

When you remove a marketplace, Claude Code uninstalls every plugin you installed from it and removes their enabledPlugins entries from your settings files. The Marketplaces tab names those plugins before it asks you to confirm.

Next steps