discover-plugins.md +0 −589 deleted
File Deleted View Diff
1> ## Documentation Index
2> Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt
3> Use this file to discover all available pages before exploring further.
4
5# Discover and install prebuilt plugins through marketplaces
6
7> Find and install plugins from marketplaces to extend Claude Code with new skills, agents, and capabilities.
8
9Plugins extend Claude Code with skills, agents, hooks, and MCP servers. Plugin marketplaces are catalogs that help you discover and install these extensions without building them yourself.
10
11You can also enable plugins on claude.ai, for yourself or through your organization. Claude Code syncs those into your sessions without a marketplace install, as [Plugins synced from claude.ai](/docs/en/plugins-reference#synced-plugins) describes.
12
13Looking to create and distribute your own marketplace? See [Create and distribute a plugin marketplace](/docs/en/plugin-marketplaces).
14
15## How marketplaces work
16
17A marketplace is a catalog of plugins that someone else has created and shared. Using a marketplace is a two-step process:
18
19<Steps>
20 <Step title="Add the marketplace">
21 This registers the catalog with Claude Code so you can browse what's available. No plugins are installed yet.
22 </Step>
23
24 <Step title="Install individual plugins">
25 Browse the catalog and install the plugins you want.
26 </Step>
27</Steps>
28
29## Official Anthropic marketplace
30
31Claude Code adds the official Anthropic marketplace (`claude-plugins-official`) automatically the first time you start it interactively. If Claude Code can't add it, for example because your network blocks the download or a [marketplace policy](/docs/en/plugin-marketplaces#managed-marketplace-restrictions) blocked an earlier attempt, add it yourself with `/plugin marketplace add anthropics/claude-plugins-official`.
32
33To browse what's available, run `/plugin` and go to the **Discover** tab, or view the catalog at [claude.com/plugins](https://claude.com/plugins).
34
35To install a plugin from the official marketplace, use `/plugin install <name>@claude-plugins-official`. For example, to install the GitHub integration:
36
37```shell theme={null}
38/plugin install github@claude-plugins-official
39```
40
41`/plugin` opens an interactive panel in the terminal CLI. If Claude replies that `/plugin` isn't available in this environment, install the plugin another way:
42
43* **Claude desktop app**: use the [plugin browser](/docs/en/desktop#install-plugins).
44* **VS Code extension**: install from the [**Manage plugins** dialog](/docs/en/vs-code#manage-plugins).
45* **Cloud sessions**: enable the plugin for your claude.ai account so Claude Code loads it as a [synced plugin](/docs/en/plugins-reference#synced-plugins).
46
47If the install fails, match the message Claude Code reports:
48
49* `Marketplace "claude-plugins-official" not found`: add the marketplace with `/plugin marketplace add anthropics/claude-plugins-official`, then retry the install.
50* The plugin is [not found in the marketplace](#install-plugins): check the plugin name.
51
52<Note>
53 The official marketplace is curated by Anthropic, and inclusion is at Anthropic's discretion. The in-app submission forms add plugins to the [community marketplace](#community-marketplace), not the official one. To distribute plugins independently, [create your own marketplace](/docs/en/plugin-marketplaces) and share it with users.
54</Note>
55
56The official marketplace includes several categories of plugins:
57
58### Code intelligence
59
60Code intelligence plugins enable Claude Code's built-in LSP tool, giving Claude the ability to jump to definitions, find references, and see type errors immediately after edits. These plugins configure [Language Server Protocol](https://microsoft.github.io/language-server-protocol/) connections, the same technology that powers VS Code's code intelligence. In [cloud sessions](/docs/en/claude-code-on-the-web), Claude Code doesn't start plugin language servers, so Claude doesn't get the LSP tool there.
61
62Install the language server binary from the table below before using these plugins; the plugin doesn't install it for you. If you already have a language server installed, Claude may prompt you to install the corresponding plugin when you open a project.
63
64| Language | Plugin | Binary required |
65| :--------- | :------------------ | :--------------------------- |
66| C/C++ | `clangd-lsp` | `clangd` |
67| C# | `csharp-lsp` | `csharp-ls` |
68| Go | `gopls-lsp` | `gopls` |
69| Java | `jdtls-lsp` | `jdtls` |
70| Kotlin | `kotlin-lsp` | `kotlin-language-server` |
71| Lua | `lua-lsp` | `lua-language-server` |
72| PHP | `php-lsp` | `intelephense` |
73| Python | `pyright-lsp` | `pyright-langserver` |
74| Rust | `rust-analyzer-lsp` | `rust-analyzer` |
75| Swift | `swift-lsp` | `sourcekit-lsp` |
76| TypeScript | `typescript-lsp` | `typescript-language-server` |
77
78You can also [create your own LSP plugin](/docs/en/plugins-reference#lsp-servers) for other languages.
79
80<Note>
81 If you see `Executable not found in $PATH` in the `/plugin` Errors tab after installing a plugin, install the binary the [code intelligence](#code-intelligence) table lists for that plugin.
82</Note>
83
84#### What Claude gains from code intelligence plugins
85
86Once a code intelligence plugin is installed and its language server binary is available, Claude gains two capabilities:
87
88* **Automatic diagnostics**: after every file edit Claude makes, the language server reports errors and warnings back, so Claude sees type errors, missing imports, and syntax issues without running a compiler or linter. If Claude introduces an error, it notices and fixes it in the same turn.
89* **Code navigation**: Claude can use the language server to jump to definitions, find references, get type info on hover, list symbols, find implementations, and trace call hierarchies. These operations give Claude more precise navigation than grep-based search, though availability may vary by language and environment.
90
91You don't need to configure diagnostics beyond installing the plugin. To read them yourself, press **Ctrl+O** when Claude Code shows an indicator such as **Found 3 new diagnostic issues in 2 files**.
92
93If you run into issues, see [Code intelligence troubleshooting](#code-intelligence-issues).
94
95### External integrations
96
97These plugins bundle pre-configured [MCP servers](/docs/en/mcp) so you can connect Claude to external services without manual setup:
98
99* **Source control**: `github`, `gitlab`
100* **Project management**: `atlassian` (Jira/Confluence), `asana`, `linear`, `notion`
101* **Design**: `figma`
102* **Infrastructure**: `vercel`, `firebase`, `supabase`
103* **Communication**: `slack`
104* **Monitoring**: `sentry`
105
106### Automatic security review
107
108The `security-guidance` plugin reviews each change Claude makes for common vulnerabilities and instructs Claude to fix what it finds in the same session. See [Catch security issues as Claude writes code](/docs/en/security-guidance) for what it checks and how to add project-specific rules.
109
110### Development workflows
111
112Plugins that add skills and agents for common development tasks:
113
114* **commit-commands**: Git commit workflows including commit, push, and PR creation
115* **pr-review-toolkit**: specialized agents for reviewing pull requests
116* **agent-sdk-dev**: tools for building with the Claude Agent SDK
117* **plugin-dev**: toolkit for creating your own plugins
118
119### Output styles
120
121Customize how Claude responds:
122
123* **explanatory-output-style**: educational insights about implementation choices
124* **learning-output-style**: interactive learning mode for skill building
125
126## Community marketplace
127
128The community marketplace at [`anthropics/claude-plugins-community`](https://github.com/anthropics/claude-plugins-community) hosts third-party plugins that have passed Anthropic's automated validation and safety screening. Each plugin is pinned to a specific commit SHA in the catalog. Unlike the official marketplace, you add it manually:
129
130```shell theme={null}
131/plugin marketplace add anthropics/claude-plugins-community
132```
133
134Then install plugins from it using the `claude-community` marketplace name:
135
136```shell theme={null}
137/plugin install <plugin-name>@claude-community
138```
139
140To submit your own plugin to the community marketplace, see [Submit your plugin to the community marketplace](/docs/en/plugins#submit-your-plugin-to-the-community-marketplace) in the create-plugins guide.
141
142## Try it: add the demo marketplace
143
144Anthropic also maintains a [demo plugins marketplace](https://github.com/anthropics/claude-code/tree/main/plugins) (`claude-code-plugins`) with example plugins that show what's possible with the plugin system. Unlike the official marketplace, you need to add this one manually.
145
146<Steps>
147 <Step title="Add the marketplace">
148 From within Claude Code, run the `plugin marketplace add` command for the `anthropics/claude-code` marketplace:
149
150 ```shell theme={null}
151 /plugin marketplace add anthropics/claude-code
152 ```
153
154 This downloads the marketplace catalog and makes its plugins available to you.
155 </Step>
156
157 <Step title="Browse available plugins">
158 Run `/plugin` to open the plugin manager. This opens a tabbed interface you can cycle through using **Tab**, or **Shift+Tab** to go backward:
159
160 * **Discover**: browse available plugins from all your marketplaces
161 * **Installed**: view and manage your installed plugins
162 * **Marketplaces**: add, remove, or update your added marketplaces
163 * **Errors**: view any plugin loading errors
164 * **Stats**: see [what each of your skills costs in context and how often it gets used](/docs/en/skills#find-unused-skills), in sessions where `/skill-doctor` is available
165
166 Go to the **Discover** tab to see plugins from the marketplace you just added. When your administrator has allowlisted the marketplace via the [`pluginSuggestionMarketplaces`](/docs/en/settings-reference#pluginsuggestionmarketplaces) managed setting, plugins marked as relevant to your current working directory are pinned at the top with a **suggested for this directory** label.
167 </Step>
168
169 <Step title="Install a plugin">
170 Select a plugin to view its details. The details pane shows what the plugin contains and what it costs:
171
172 * A **Context cost** estimate so you can see how many tokens the plugin will add to your [context window](/docs/en/features-overview#understand-context-costs) every turn
173 * The plugin's **Last updated** date
174 * A **Will install** section listing the plugin's commands, agents, skills, hooks, and MCP and LSP servers, so you can review exactly what it adds before installing
175
176 Not every plugin provides the data behind these fields. For plugins from local or custom marketplaces, you may not see the **Context cost** and **Last updated** rows, and the **Will install** section may show **Components will be discovered at installation** instead.
177
178 Choose an installation scope:
179
180 * **User scope**: install for yourself across all projects
181 * **Project scope**: install for all collaborators on this repository
182 * **Local scope**: install for yourself in this repository only
183
184 For example, select **commit-commands**, a plugin that adds git workflow skills, and install it to your user scope.
185
186 You can also start the install from the command line:
187
188 ```shell theme={null}
189 /plugin install commit-commands@claude-code-plugins
190 ```
191
192 See [Settings files](/docs/en/settings#where-settings-live) to learn more about scopes.
193 </Step>
194
195 <Step title="Use your new plugin">
196 If the install summary reports `Run /reload-plugins to activate.`, Claude Code then runs that reload for you. If the reload warns that your next message would re-read the conversation, run `/reload-plugins --force` to activate the plugin.
197
198 Plugin skills are namespaced by the plugin name, so **commit-commands** provides skills like `/commit-commands:commit`.
199
200 Try it out by making a change to a file and running:
201
202 ```shell theme={null}
203 /commit-commands:commit
204 ```
205
206 This stages your changes, generates a commit message, and creates the commit.
207
208 Each plugin works differently. Check the plugin's details in the **Discover** tab to see the commands and skills it provides, or visit its homepage for usage guidance.
209 </Step>
210</Steps>
211
212## Add marketplaces
213
214Use the `/plugin marketplace add` command to add marketplaces from different sources.
215
216<Tip>
217 **Shortcuts**: You can use `/plugin market` instead of `/plugin marketplace`, and `rm` instead of `remove`.
218</Tip>
219
220* **GitHub repositories**: `owner/repo` format, for example `anthropics/claude-code`
221* **Git URLs**: any git repository URL, including GitLab, Bitbucket, and self-hosted servers
222* **Local paths**: directories or direct paths to `marketplace.json` files
223* **Remote URLs**: direct URLs to hosted `marketplace.json` files
224* **claude.ai**: marketplaces hosted on claude.ai for your account, such as your organization's plugin library, which you [add by name from the **Marketplaces** tab or your shell](#add-from-claude-ai) rather than by source
225
226### Add from GitHub
227
228Add a GitHub repository that contains a `.claude-plugin/marketplace.json` file using the `owner/repo` format, where `owner` is the GitHub username or organization and `repo` is the repository name.
229
230For example, `anthropics/claude-code` refers to the `claude-code` repository owned by `anthropics`:
231
232```shell theme={null}
233/plugin marketplace add anthropics/claude-code
234```
235
236### Add from other Git hosts
237
238Add a git marketplace repository by providing its full URL. For an `https://` URL, whether to include the `.git` suffix depends on the host:
239
240* **`github.com` and `gitlab.com`**: Claude Code recognizes a repository URL with or without the `.git` suffix and clones it. Adding a `gitlab.com` URL without the suffix requires Claude Code v2.1.232 or later. Before v2.1.232, Claude Code treated it as a direct link to a hosted `marketplace.json` file.
241* **Azure DevOps**: omit the suffix. Claude Code clones any URL whose path contains `/_git/`. If you append `.git` to a `/_git/` path, the clone fails.
242* **Every other host, including self-managed GitLab servers**: include the `.git` suffix so Claude Code clones the repository rather than treating the URL as a direct link to a hosted `marketplace.json` file. For a host whose clone URLs don't carry the suffix, such as AWS CodeCommit, add the marketplace as a git entry in [`extraKnownMarketplaces`](/docs/en/settings-reference#extraknownmarketplaces) instead. Claude Code clones a git entry whether or not its URL ends in `.git`.
243
244Claude Code also clones a `gitlab.com` URL with nested subgroups, such as `https://gitlab.com/group/subgroup/project`.
245
246Include the `https://` prefix. Claude Code v2.1.196 and later reject a host typed without it, such as `gitlab.com/company/plugins.git`, as an invalid GitHub `owner/repo` shorthand, and the error tells you to add the prefix. Earlier versions misread it as a GitHub repository path and fail at clone time.
247
248Using HTTPS:
249
250```shell theme={null}
251/plugin marketplace add https://gitlab.com/company/plugins.git
252```
253
254Using SSH:
255
256```shell theme={null}
257/plugin marketplace add git@gitlab.com:company/plugins.git
258```
259
260Claude Code clones an SSH address whether or not it ends in `.git`.
261
262To add a specific branch or tag, append `#` followed by the ref:
263
264```shell theme={null}
265/plugin marketplace add https://gitlab.com/company/plugins.git#v1.0.0
266```
267
268### Add from local paths
269
270Add a local directory that contains a `.claude-plugin/marketplace.json` file:
271
272```shell theme={null}
273/plugin marketplace add ./my-marketplace
274```
275
276You can also add a direct path to a `marketplace.json` file:
277
278```shell theme={null}
279/plugin marketplace add ./path/to/marketplace.json
280```
281
282### Add from remote URLs
283
284Add a remote `marketplace.json` file via URL:
285
286```shell theme={null}
287/plugin marketplace add https://example.com/marketplace.json
288```
289
290<Note>
291 URL-based marketplaces have some limitations compared to Git-based marketplaces. If plugin installs from a URL-based marketplace fail, see [Troubleshooting](/docs/en/plugin-marketplaces#plugins-with-relative-paths-fail-in-url-based-marketplaces).
292</Note>
293
294### Add from claude.ai
295
296In terminal sessions where [plugins sync from your claude.ai account](/docs/en/plugins-reference#synced-plugins), claude.ai can also list marketplaces for you, such as your organization's plugin library and your own claude.ai uploads. `claude plugin marketplace list` prints them in a `From claude.ai:` section, and the `/plugin` **Marketplaces** tab lists them. Select one there to add it. Adding a marketplace from claude.ai requires Claude Code v2.1.273 or later.
297
298To add a marketplace from that list in your shell instead, run `claude plugin marketplace add` with the `--claudeai` flag and the name the list shows:
299
300```bash theme={null}
301claude plugin marketplace add --claudeai claudeai-organization-library
302```
303
304Claude Code registers the marketplace under a local name that starts with `claudeai-`, derived from the name that claude.ai lists it under: a marketplace listed as "Organization library" registers as `claudeai-organization-library`. Install its plugins by that name, for example with `claude plugin install <plugin>@claudeai-organization-library`.
305
306If you sign out or sign in with a different account, the marketplace stays configured but shows no plugins, and the plugins you already installed from it keep loading.
307
308The `From claude.ai:` section can also list git-based marketplaces shared through claude.ai. You add those with the ordinary `marketplace add` command, using the source that the list prints.
309
310## Install plugins
311
312Once you've added marketplaces, you can install a plugin by name. For a marketplace you haven't added yet, you can instead [add it and install in one command](#add-a-marketplace-and-install-in-one-command).
313
314To install by name:
315
316```shell theme={null}
317/plugin install plugin-name@marketplace-name
318```
319
320The command opens that plugin's details, where you choose an [installation scope](/docs/en/settings#where-settings-live). You see the same choices when you run `/plugin`, go to the **Discover** tab, and press **Enter** on a plugin:
321
322* **User scope**: install for yourself across all projects
323* **Project scope**: install for all collaborators on this repository, which adds the plugin to `.claude/settings.json`
324* **Local scope**: install for yourself in this repository only, not shared with collaborators
325
326To install without an interactive step, use the [`claude plugin install`](/docs/en/plugins-reference#plugin-install) shell command, which installs to user scope unless you pass `--scope`. For a plugin with a [`command` source](/docs/en/plugin-marketplaces#how-users-accept-the-command), pass `--yes` to accept the command it displays.
327
328You may also see plugins with **managed** scope. These are installed by administrators via [managed settings](/docs/en/managed-settings) and can't be modified.
329
330Claude Code looks the plugin up in its local copy of the marketplace catalog. How you name the plugin controls whether Claude Code refreshes that copy first:
331
332* **With a marketplace name**: when you install `plugin-name@marketplace-name`, in a session or with `claude plugin install`, Claude Code refreshes that marketplace before the lookup. Claude Code runs the refresh even if you turned off [auto-update](#configure-auto-updates) for the marketplace or set `DISABLE_AUTOUPDATER`. Before v2.1.232, Claude Code didn't refresh the marketplace before the lookup. Claude Code skips this refresh when:
333 * The marketplace wasn't [added from GitHub, another Git host, a remote URL](#add-marketplaces), or [claude.ai](#add-from-claude-ai).
334 * A [seed directory](/docs/en/plugin-marketplaces#pre-populate-plugins-for-containers) supplies the marketplace.
335 * Claude Code refreshed the marketplace within the last 30 seconds.
336 * You set [`CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC`](/docs/en/env-vars).
337 * [Managed settings](/docs/en/plugin-marketplaces#managed-marketplace-restrictions) block the marketplace, in which case Claude Code also refuses the install.
338* **Plugin name only**: when you run `/plugin install plugin-name` in a session, Claude Code refreshes only the marketplaces it also [updates in the background](#configure-auto-updates), and only after the lookup misses. When you run `claude plugin install plugin-name`, Claude Code reads the cached catalogs without refreshing. To install a plugin that was published after your last refresh, run `/plugin marketplace update <marketplace-name>` in a session or [`claude plugin marketplace update <marketplace-name>`](/docs/en/plugin-marketplaces#plugin-marketplace-update) in your shell, then retry the install.
339
340If the refresh before a named install fails, for example because you're offline, Claude Code looks the plugin up in the cached catalog anyway. `claude plugin install` reports `marketplace not refreshed` in its success message, and `/plugin install` shows the failure above the plugin's details or in its not-found message.
341
342When you install from the `/plugin` interface, the install summary tells you whether the plugin is active in your current session:
343
344* `Plugin is now active.`: Claude Code activated the plugin as part of the install.
345* `Run /reload-plugins to activate.`: the plugin isn't active yet, because activating it would [invalidate the prompt cache](/docs/en/prompt-caching#enabling-or-disabling-a-plugin) or because the activation attempt failed. Claude Code then runs `/reload-plugins` for you. If that reload warns about the prompt cache, run `/reload-plugins --force` to [activate the plugin anyway](#apply-plugin-changes-without-restarting).
346* If the plugin fails to load, the summary reports the failure and the `/plugin` **Errors** tab shows the detail.
347
348Before v2.1.221, no install took effect in the current session until you ran `/reload-plugins` or restarted.
349
350The `claude plugin install` shell command doesn't run in a session, so Claude Code loads the plugins it installs the next time you start Claude Code, or when you run `/reload-plugins` in a session that's already open.
351
352<Warning>
353 Make sure you trust a plugin before installing it. Anthropic doesn't control what MCP servers, files, or other software are included in plugins and can't verify that they work as intended. Check each plugin's homepage for more information.
354</Warning>
355
356### Add a marketplace and install in one command
357
358To install a plugin from a marketplace you haven't added yet, name the marketplace source with `--marketplace`. Requires Claude Code v2.1.275 or later.
359
360```shell theme={null}
361/plugin install quality-review-plugin --marketplace your-org/plugins
362```
363
364The source takes [the same forms as `/plugin marketplace add`](#add-marketplaces), such as GitHub `owner/repo`, a git URL, or a local path, except that it can't contain spaces. Give the plugin name bare, without an `@marketplace` suffix.
365
366Claude Code shows the source it resolved and asks you to confirm before adding the marketplace. Declining cancels the install and adds nothing. Once the marketplace is added, the plugin's details open and you choose an [installation scope](/docs/en/settings#where-settings-live). If the source matches a marketplace you've already added, Claude Code skips the confirmation and opens the plugin's details in that marketplace.
367
368## Manage installed plugins
369
370Run `/plugin` and go to the **Installed** tab to view, enable, disable, or uninstall your plugins. The list is grouped by scope and sorted so you see problems first: plugins with load errors or unresolved dependencies appear at the top, followed by your favorites, with disabled plugins folded behind a collapsed header at the bottom.
371
372From the list you can:
373
374* press `f` to favorite or unfavorite the selected plugin
375* type to filter by plugin name or description
376* press Enter to open a plugin's detail view and enable, disable, or uninstall it
377
378Claude Code also lists the [plugins synced from your claude.ai account](/docs/en/plugins-reference#synced-plugins) in the **Installed** tab, with `synced` as their source. You can enable or disable one there unless your organization marked it as required. To remove one, turn it off on claude.ai. Synced plugins appear in terminal sessions on Claude Code v2.1.273 or later.
379
380When you uninstall a plugin that a project's `.claude/settings.json` enables, Claude Code asks which scope you mean: disable it for you alone, which writes an override to your `.claude/settings.local.json` and leaves the plugin installed for the project, or uninstall it for everyone, which removes it from the shared `.claude/settings.json`.
381
382The detail view shows the components the plugin contributes: commands, skills, agents, hooks, MCP servers, and LSP servers. The same inventory is available from the command line with `claude plugin details`.
383
384Claude Code also lists marketplace plugins you installed yourself but haven't used in at least two weeks, over a span of at least 10 sessions, under a **Not used recently** header in the **Installed** tab. The detail view shows a **Last used** line for each plugin. Use these to find plugins that still add startup and context cost even though you no longer use them, then disable or uninstall them.
385
386Two kinds of plugins are never listed as unused:
387
388* plugins that your organization manages or that you load with `--plugin-dir`
389* plugins that contribute a theme, output style, monitor, or workflow, since those deliver value without an invocation to track
390
391The **Not used recently** header and the **Last used** line are both hidden when your organization restricts marketplaces with [`strictKnownMarketplaces`](/docs/en/settings-reference#strictknownmarketplaces).
392
393A plugin's [language server](/docs/en/plugins#add-lsp-servers-to-your-plugin) counts as used when it delivers diagnostics or answers a code navigation request, so an LSP plugin whose server is active in your sessions isn't listed as unused. Before v2.1.203, language server activity couldn't be counted as use, so plugins that contribute an LSP server were exempt from the group entirely, the same way theme and output style plugins still are.
394
395The first session on a version that counts language server activity also resets the usage record of each LSP plugin that hadn't recorded any use yet, so Claude Code doesn't judge a plugin you installed earlier as unused based on data recorded before its server activity was tracked.
396
397When you install a plugin that declares dependencies, the install output lists which dependencies were auto-installed alongside it.
398
399You can also manage plugins with direct commands:
400
401* When you run `/plugin disable`, `/plugin enable`, or `/plugin uninstall`, Claude Code opens the plugin panel to make the change and leaves it open. Press **Esc** to close the panel before typing another command. [Apply plugin changes without restarting](#apply-plugin-changes-without-restarting) describes when the change takes effect in your session.
402* For scripting, use the `claude plugin` shell commands instead, which don't open the panel.
403
404List installed plugins without opening the menu:
405
406```shell theme={null}
407/plugin list
408```
409
410Pass `--enabled` or `--disabled` to show only plugins in that state.
411
412Disable a plugin without uninstalling:
413
414```shell theme={null}
415/plugin disable plugin-name@marketplace-name
416```
417
418Re-enable a disabled plugin:
419
420```shell theme={null}
421/plugin enable plugin-name@marketplace-name
422```
423
424In these identifiers, `plugin-name` is the plugin's `name` in the [marketplace entry](/docs/en/plugin-marketplaces#plugin-entries), which can differ from the `name` in the plugin's own `plugin.json`.
425
426As of Claude Code v2.1.195, **Enable** and **Disable** in the `/plugin` interface work for plugins whose two names differ, and `/plugin enable` and `/plugin disable` accept either name. When you disable such a plugin in an earlier version, Claude Code reports `already disabled` and leaves it enabled.
427
428Completely remove a plugin:
429
430```shell theme={null}
431/plugin uninstall plugin-name@marketplace-name
432```
433
434The `--scope` option lets you target a specific scope with CLI commands:
435
436```shell theme={null}
437claude plugin install formatter@your-org --scope project
438claude plugin uninstall formatter@your-org --scope project
439```
440
441### Apply plugin changes without restarting
442
443When you close the `/plugin` menu, Claude Code runs `/reload-plugins` for you to apply the changes you made in it, such as installing, enabling, disabling, and uninstalling plugins. 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. If Claude is still responding when you close the menu, the reload runs after the response finishes.
444
445For plugin changes that happen outside the menu, run `/reload-plugins` yourself. These changes include:
446
447* A `claude plugin` command you ran in another terminal
448* Edits to a plugin you loaded with [`--plugin-dir`](/docs/en/plugins#test-your-plugins-locally) while you develop it
449* A plugin [auto-update](#configure-auto-updates) whose notification asks you to reload
450* A [sync from your claude.ai account](/docs/en/plugins-reference#synced-plugins) that added, updated, or removed a plugin and showed a notification asking you to reload
451* A change in a [`--plugin-dir` folder](/docs/en/plugins#test-your-plugins-locally) that Claude Code held because applying it would invalidate the prompt cache
452
453Before v2.1.268, plugins you enabled, disabled, or uninstalled in the menu, and installs that didn't activate during the install, stayed pending until you ran `/reload-plugins`.
454
455`/reload-plugins` also runs in sessions without an interactive terminal, such as the desktop app, the Agent SDK, and [non-interactive mode](/docs/en/headless) with `-p`. Requires Claude Code v2.1.260 or later. Two limits apply in those sessions:
456
457* The command runs only when you type it directly into the session, such as in the `-p` prompt or the desktop app's prompt box. When you send it over a remote connection instead, such as [Remote Control](/docs/en/remote-control) or a relayed chat message, the command declines without reloading anything.
458* The reload doesn't connect or disconnect plugin MCP servers. Those changes take effect in your next session.
459
460Claude Code reloads all active plugins and shows counts for plugins, skills, agents, hooks, plugin MCP servers, and plugin LSP servers, omitting the plugin MCP server count in a session without an interactive terminal. In the skills count, Claude Code includes every skill a plugin provides: both its `commands/` entries and its `SKILL.md` skills. Before v2.1.246, Claude Code counted only `commands/` entries, so it could reload a plugin's `SKILL.md` skills and still report `0 skills` in the summary.
461
462Reloading has a token cost on the next request: newly loaded components announce themselves in content appended to the conversation, while the existing history still reads from the prompt cache. A plugin that provides MCP servers costs more when its tools aren't deferred by [tool search](/docs/en/mcp#scale-with-mcp-tool-search): the change invalidates the cache and the next request re-reads the entire conversation. See [enabling or disabling a plugin](/docs/en/prompt-caching#enabling-or-disabling-a-plugin) for details.
463
464## Manage marketplaces
465
466You can manage marketplaces through the interactive `/plugin` interface or with CLI commands.
467
468### Use the interactive interface
469
470Run `/plugin` and go to the **Marketplaces** tab to:
471
472* View all your added marketplaces with their sources and status
473* Add new marketplaces
474* Update marketplace listings to fetch the latest plugins
475* Remove marketplaces you no longer need
476
477### Use CLI commands
478
479You can also manage marketplaces with direct commands.
480
481List all configured marketplaces:
482
483```shell theme={null}
484/plugin marketplace list
485```
486
487Refresh plugin listings from a marketplace:
488
489```shell theme={null}
490/plugin marketplace update marketplace-name
491```
492
493Remove a marketplace:
494
495```shell theme={null}
496/plugin marketplace remove marketplace-name
497```
498
499<Warning>
500 Removing a marketplace will uninstall any plugins you installed from it.
501</Warning>
502
503### Configure auto-updates
504
505Claude Code can automatically update marketplaces and their installed plugins in the background after startup. When auto-update is enabled for a marketplace, Claude Code refreshes the marketplace data and updates installed plugins to their latest versions on disk.
506
507Claude Code checks for marketplace and plugin updates after your session starts, with a random delay of up to ten minutes, so the running session keeps using the versions it loaded at launch. If any plugins were updated, you'll see a notification prompting you to run `/reload-plugins`, or the new versions load on your next launch.
508
509Auto-update also leaves out a plugin whose marketplace entry declares a `headersHelper`: Claude Code [neither runs the command nor downloads the archive](/docs/en/plugin-marketplaces#installs-and-updates-that-refuse-the-command-instead-of-asking) on that path; that section says when Claude Code lists the plugin in the `/plugin` Errors tab so you can update it from its own view.
510
511Claude Code updates plugins that have a [`command` source](/docs/en/plugin-marketplaces#command-sources) on a separate cadence from the marketplace auto-update setting and from `DISABLE_AUTOUPDATER`. Instead, it [re-runs the command once per session](/docs/en/plugin-marketplaces#when-claude-code-re-runs-the-command) and installs the output as a new plugin version when its [hash](/docs/en/plugins-reference#version-management) has changed.
512
513Toggle auto-update for individual marketplaces through the UI:
514
5151. Run `/plugin` to open the plugin manager
5162. Select **Marketplaces**
5173. Choose a marketplace from the list
5184. Select **Enable auto-update** or **Disable auto-update**
519
520`claude-plugins-official`, most other official Anthropic marketplaces, and [marketplaces added from claude.ai](#add-from-claude-ai) have auto-update enabled by default. Other third-party marketplaces and local development marketplaces have auto-update disabled by default.
521
522Administrators can also set `"autoUpdate": true` on each [`extraKnownMarketplaces`](/docs/en/settings-reference#extraknownmarketplaces) entry in managed settings to enable auto-update for an organization marketplace without requiring each user to toggle it.
523
524To disable automatic updates for Claude Code and for plugins fetched from marketplaces, set the `DISABLE_AUTOUPDATER` environment variable. Plugins with a [`command` source](/docs/en/plugin-marketplaces#command-sources) follow their own once-per-session re-resolve. See [Auto updates](/docs/en/setup#auto-updates) for details.
525
526To keep plugin auto-updates enabled while disabling Claude Code auto-updates, set `FORCE_AUTOUPDATE_PLUGINS=1` along with `DISABLE_AUTOUPDATER`:
527
528```bash theme={null}
529export DISABLE_AUTOUPDATER=1
530export FORCE_AUTOUPDATE_PLUGINS=1
531```
532
533## Configure team marketplaces
534
535Team admins can set up automatic marketplace installation for projects by adding marketplace configuration to `.claude/settings.json`. Once a team member [trusts the repository folder](/docs/en/permissions#what-runs-before-you-trust-a-folder), Claude Code adds these marketplaces without a further prompt.
536
537As of Claude Code v2.1.195, adding the marketplace doesn't install plugins that come from an external source, on any path that loads plugins. A plugin that only the project's `.claude/settings.json` enables, and that comes from an external source such as a GitHub repository or npm package, doesn't load until the team member installs it. Until then, Claude Code reports the plugin as not installed and shows the `claude plugin install` command to run.
538
539Add `extraKnownMarketplaces` to your project's `.claude/settings.json`:
540
541```json theme={null}
542{
543 "extraKnownMarketplaces": {
544 "my-team-tools": {
545 "source": {
546 "source": "github",
547 "repo": "your-org/claude-plugins"
548 }
549 }
550 }
551}
552```
553
554For full configuration options including `extraKnownMarketplaces` and `enabledPlugins`, see [Plugin settings](/docs/en/settings-reference#plugin-settings).
555
556## Security
557
558Plugins and marketplaces are highly trusted components that can execute arbitrary code on your machine with your user privileges. Only install plugins and add marketplaces from sources you trust. Organizations can restrict which marketplaces users are allowed to add using [managed marketplace restrictions](/docs/en/plugin-marketplaces#managed-marketplace-restrictions).
559
560## Troubleshooting
561
562### /plugin command not recognized
563
564If you see "unknown command" or the `/plugin` command doesn't appear:
565
5661. **Check your version**: run `claude --version` to see what's installed.
5672. **Update Claude Code**:
568 * **Homebrew**: `brew upgrade claude-code`, or `brew upgrade claude-code@latest` if you installed that cask
569 * **npm**: `npm install -g @anthropic-ai/claude-code@latest`
570 * **Native installer**: re-run the install command from [Setup](/docs/en/setup)
5713. **Restart Claude Code**: after updating, restart your terminal and run `claude` again.
572
573### Common issues
574
575If plugin skills don't appear, clear the cache with `rm -rf ~/.claude/plugins/cache`, restart Claude Code, and reinstall the plugin.
576
577For detailed troubleshooting with solutions, see [Troubleshooting](/docs/en/plugin-marketplaces#troubleshooting) in the marketplace guide. For debugging tools, see [Debugging and development tools](/docs/en/plugins-reference#debugging-and-development-tools).
578
579### Code intelligence issues
580
581* **Language server not starting**: verify the binary is installed and available in your `$PATH`. Check the `/plugin` Errors tab for details.
582* **High memory usage**: language servers like `rust-analyzer` and `pyright` can consume significant memory on large projects. If you experience memory issues, disable the plugin with `/plugin disable <plugin-name>` and rely on Claude's built-in search tools instead.
583* **False positive diagnostics in monorepos**: language servers may report unresolved import errors for internal packages if the workspace isn't configured correctly. These don't affect Claude's ability to edit code.
584
585## Next steps
586
587* **Build your own plugins**: see [Plugins](/docs/en/plugins) to create skills, agents, and hooks
588* **Create a marketplace**: see [Create a plugin marketplace](/docs/en/plugin-marketplaces) to distribute plugins to your team or community
589* **Technical reference**: see [Plugins reference](/docs/en/plugins-reference) for complete specifications