Text of code.claude.com › docs › en › plugins › install as Styx crawled it on Nov 20, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Install and manage plugins - Claude Code Docs

Documentation Index Fetch the complete documentation index at: /docs/llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. 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: You use claude.ai chat or Cowork, not Claude Code : see Plugins on claude.ai and in Cowork Claude Code printed an error : find it in Troubleshoot plugins 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. Terminal Desktop app VS Code Cloud session Start Claude Code with claude in your project, then: 1 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. /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.

2 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 . 3 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 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, then prints an install summary. 4 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 a note that starts Its bundled MCP server needs . The plugin’s bundled MCP server can’t start until you set its options.

Select the plugin on the Installed tab in /plugin and choose Configure . 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 , it warns and leaves the plugin pending instead. Run /reload-plugins --force to activate it anyway, which costs one uncached request. Load failed : the summary includes The plugin couldn't . Open the Errors tab in /plugin for the reason, then see After install: plugin not working .

5 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 .

Installing from any other marketplace requires one extra step first: add the 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 , its Claude Code button copies the install command in its shell form , claude plugin install <name>@claude-plugins-official .

In a local or SSH session in the desktop app’s Code tab: 1 Open the plugin browser 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 . If Browse plugins is missing, select Manage plugins . The plugin browser opens with the plugins from your marketplaces. 2 Select the plugin Find commit-commands and select it. 3 Choose a scope Choose a scope : your user account, this project, or local-only.

To enable, disable, or uninstall a plugin later, see Install plugins in the desktop app . In the Claude Code panel in VS Code: 1 Open Manage plugins Type /plugins in the prompt box to open Manage plugins . 2 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. 3 Choose a scope Choose a scope : Install for you , Install for this project , or Install locally .

Your changes apply to open sessions without a restart. See Manage plugins in VS Code . 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 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.

Each collaborator also runs claude plugin install <name>@<marketplace> --scope project once per clone; 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 fo

The rest of this page is on the live site.