Install and manage plugins changedplugins/install
Nearest release: v2.1.304, published under an hour after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 19 Oct 2026 19:44 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:37 UTC.
Upstream edited
Recorded here
Lines+115added
Lines−129removed
From line
6
where the diff opens
First seen
25 Sep 2026
this site's first read of the page
Recorded edits12to this page, all time
### JetBrains, non-interactive runs, and the Agent SDK ### Plugins from your claude.ai account ### Add a marketplace from claude.ai
The whole hunk
from line 6, old and new numbered
/
from line 6
66
77This 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.
88
9<Note>
10 These cases are covered on other pages:
9> [!NOTE]
10>
11> These cases are covered on other pages:
12>
13> * **You use claude.ai chat or Cowork, not Claude Code**: see [Plugins on claude.ai and in Cowork](https://claude.com/docs/plugins/overview)
14> * **Claude Code printed an error**: find it in [Troubleshoot plugins](/docs/en/plugins/troubleshooting)
1115
12 * **You use claude.ai chat or Cowork, not Claude Code**: see [Plugins on claude.ai and in Cowork](https://claude.com/docs/plugins/overview)
13 * **Claude Code printed an error**: find it in [Troubleshoot plugins](/docs/en/plugins/troubleshooting)
14</Note>
15
1616Start with [Install a plugin](#install-a-plugin). If someone sent you an install command whose `@` name isn't `claude-plugins-official`, [add that marketplace](#add-a-marketplace) first.
1717
1818## Install a plugin
from line 23
2323
2424Pick the tab for where you run Claude Code.
2525
26<Tabs>
27 <Tab title="Terminal">
28 Start Claude Code with `claude` in your project, then:
26**Terminal**
2927
30 <Steps>
31 <Step title="Open the plugin's details with the install command">
32 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.
28Start Claude Code with `claude` in your project, then:
3329
34 ```text theme={null}
35 /plugin install commit-commands@claude-plugins-official
36 ```
30**1. Open the plugin's details with the install command**
3731
38 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.
39 </Step>
32Run `/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.
4033
41 <Step title="Review what the plugin adds">
42 The details pane shows the plugin's description. It can also show:
34```text theme={null}
35/plugin install commit-commands@claude-plugins-official
36```
4337
44 * **Will install**: the commands, agents, skills, hooks, and MCP and LSP servers the plugin adds.
45 * **Last updated**: shown for a plugin in Anthropic's official marketplace.
46 * **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.
38To 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.
4739
48 Plugins from a local or custom marketplace can show `Components will be discovered at installation` instead.
40**2. Review what the plugin adds**
4941
50 A plugin can run hooks and MCP servers, so read the pane before you install. See [Plugin security and trust](/docs/en/plugins/security).
51 </Step>
42The details pane shows the plugin's description. It can also show:
5243
53 <Step title="Choose a scope">
54 Select one of the three install options:
44* **Will install**: the commands, agents, skills, hooks, and MCP and LSP servers the plugin adds.
45* **Last updated**: shown for a plugin in Anthropic's official marketplace.
46* **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.
5547
56 * **Install for you (user scope)**: you get the plugin in every project on this machine
57 * **Install for all collaborators on this repository (project scope)**: it's enabled for everyone who works in this repository
58 * **Install for you, in this repo only (local scope)**: you get it in this repository only
48Plugins from a local or custom marketplace can show `Components will be discovered at installation` instead.
5949
60 [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.
50A plugin can run hooks and MCP servers, so read the pane before you install. See [Plugin security and trust](/docs/en/plugins/security).
6151
62 After you select a scope, Claude Code installs the plugin along with any dependencies it declares, then prints an install summary.
63 </Step>
52**3. Choose a scope**
6453
65 <Step title="Read the install summary">
66 The last sentence of the summary tells you whether the plugin is usable in this session yet:
54Select one of the three install options:
6755
68 * **Active now**: `Plugin is now active.` No reload is needed.
69 * **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.
70 * **Reload needed**: `Run /reload-plugins to apply.` 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.
71 * **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).
72 </Step>
56* **Install for you (user scope)**: you get the plugin in every project on this machine
57* **Install for all collaborators on this repository (project scope)**: it's enabled for everyone who works in this repository
58* **Install for you, in this repo only (local scope)**: you get it in this repository only
7359
74 <Step title="Confirm the plugin works">
75 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:
60[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.
7661
77 * Open the **Installed** tab in `/plugin`, which lists the plugin with its scope.
78 * In your shell, run `claude plugin list`, which prints the same list with `Version`, `Scope`, and `Status` lines.
62After you select a scope, Claude Code installs the plugin along with any dependencies it declares, then prints an install summary.
7963
80 If `/commit-commands:commit` doesn't appear, see [After install: plugin not working](/docs/en/plugins/troubleshooting#plugin-installed-but-not-working).
81 </Step>
82 </Steps>
64**4. Read the install summary**
8365
84 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`.
85 </Tab>
66The last sentence of the summary tells you whether the plugin is usable in this session yet:
8667
87 <Tab title="Desktop app">
88 In a local or SSH session in the desktop app's **Code** tab:
68* **Active now**: `Plugin is now active.` No reload is needed.
69* **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.
70* **Reload needed**: `Run /reload-plugins to apply.` 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.
71* **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).
8972
90 <Steps>
91 <Step title="Open the plugin browser">
92 Click the **+** button next to the prompt box and select **Add plugins**. If the **+** menu shows **Plugins** instead of **Add plugins**, select **Plugins**, then **Browse plugins**. The plugin browser opens with the plugins from your marketplaces.
93 </Step>
73**5. Confirm the plugin works**
9474
95 <Step title="Select the plugin">
96 Find `commit-commands` and select it.
97 </Step>
75Type `/` 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:
9876
99 <Step title="Choose a scope">
100 Choose a [scope](#choose-an-install-scope): your user account, this project, or local-only.
101 </Step>
102 </Steps>
77* Open the **Installed** tab in `/plugin`, which lists the plugin with its scope.
78* In your shell, run `claude plugin list`, which prints the same list with `Version`, `Scope`, and `Status` lines.
10379
104 To enable, disable, or uninstall a plugin later, see [Install plugins in the desktop app](/docs/en/desktop#install-plugins).
105 </Tab>
80If `/commit-commands:commit` doesn't appear, see [After install: plugin not working](/docs/en/plugins/troubleshooting#plugin-installed-but-not-working).
10681
107 <Tab title="VS Code">
108 In the Claude Code panel in VS Code:
82Installing 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`.
10983
110 <Steps>
111 <Step title="Open Manage plugins">
112 Type `/plugins` in the prompt box to open **Manage plugins**.
113 </Step>
84**Desktop app**
11485
115 <Step title="Install the plugin">
116 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.
117 </Step>
86In a local or SSH session in the desktop app's **Code** tab:
11887
119 <Step title="Choose a scope">
120 Choose a [scope](#choose-an-install-scope): **Install for you**, **Install for this project**, or **Install locally**.
121 </Step>
122 </Steps>
88**1. Open the plugin browser**
12389
124 Your changes apply to open sessions without a restart. See [Manage plugins in VS Code](/docs/en/vs-code#manage-plugins).
125 </Tab>
90Click the **+** button next to the prompt box and select **Add plugins**. If the **+** menu shows **Plugins** instead of **Add plugins**, select **Plugins**, then **Browse plugins**. The plugin browser opens with the plugins from your marketplaces.
12691
127 <Tab title="Cloud session">
128 A [cloud session](/docs/en/cloud-environments), including [the browser at claude.ai/code](/docs/en/claude-code-on-the-web), 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](/docs/en/plugins/org).
92**2. Select the plugin**
12993
130 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.
131 </Tab>
132</Tabs>
94Find `commit-commands` and select it.
13395
96**3. Choose a scope**
97
98Choose a [scope](#choose-an-install-scope): your user account, this project, or local-only.
99
100To enable, disable, or uninstall a plugin later, see [Install plugins in the desktop app](/docs/en/desktop#install-plugins).
101
102**VS Code**
103
104In the Claude Code panel in VS Code:
105
106**1. Open Manage plugins**
107
108Type `/plugins` in the prompt box to open **Manage plugins**.
109
110**2. Install the plugin**
111
112On 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.
113
114**3. Choose a scope**
115
116Choose a [scope](#choose-an-install-scope): **Install for you**, **Install for this project**, or **Install locally**.
117
118Your changes apply to open sessions without a restart. See [Manage plugins in VS Code](/docs/en/vs-code#manage-plugins).
119
120**Cloud session**
121
122A [cloud session](/docs/en/cloud-environments), including [the browser at claude.ai/code](/docs/en/claude-code-on-the-web), 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](/docs/en/plugins/org).
123
124See [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.
125
134126### Choose an install scope
135127
136128A plugin's install scope decides who gets the plugin and which settings file records it as enabled:
from line 137
145137
146138The 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.
147139
148<h3 id="other-places-you-run-claude-code">
149 JetBrains, non-interactive runs, and the Agent SDK
150</h3>
140### JetBrains, non-interactive runs, and the Agent SDK
151141
152142Some places you run Claude Code have no plugin browser of their own:
153143
from line 147
157147
158148If 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](/docs/en/plugins/loading#enabled-in-project-settings-but-not-installed).
159149
160<Tip>
161 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](/docs/en/plugins/cli-reference#flags-that-load-a-plugin-for-one-session).
162</Tip>
150> [!TIP]
151>
152> 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](/docs/en/plugins/cli-reference#flags-that-load-a-plugin-for-one-session).
163153
164<h3 id="plugins-from-your-claude-ai-account">
165 Plugins from your claude.ai account
166</h3>
154### Plugins from your claude.ai account
167155
168156Your claude.ai account is a separate source of plugins, alongside the marketplaces you install from:
169157
from line 196
208196
209197From your shell, `claude plugin marketplace add` takes the same sources.
210198
211<Tip>
212 `/plugin market` also works as a shorter form of `/plugin marketplace`.
213</Tip>
199> [!TIP]
200>
201> `/plugin market` also works as a shorter form of `/plugin marketplace`.
214202
215203Include 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.
216204
from line 244
256244
257245If your organization registers the marketplace for you through managed settings, you don't add it yourself. See [Pre-install and require plugins](/docs/en/plugins/org#pre-install-and-require-plugins).
258246
259<h3 id="add-from-claude-ai">
260 Add a marketplace from claude.ai
261</h3>
247### Add a marketplace from claude.ai
262248
263249In terminal sessions where [plugins sync from your claude.ai account](/docs/en/plugins/loading#synced-plugins), 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.
264250
No line in this hunk matches that.