Installing and Managing Plugins
Installing a plugin adds its Skills, Agents, Hooks, and MCP servers directly into Claude Code. This guide covers the full lifecycle from installation to marketplace addition, updates, and removal.
ํ๋ฌ๊ทธ์ธ ์ค์นโ
Here is an example installing the commit-commands plugin from the official Anthropic marketplace. Other plugins follow the same process.
ํฐ๋ฏธ๋์์ ์ค์นโ
# Open details panel and select scope to install inside a session
/plugin install commit-commands@claude-plugins-official
Running this command opens the plugin details view. You can review the bundled components and estimated context cost before selecting an installation scope.
Installation Status Messages:
| Message | Meaning |
|---|---|
Plugin is now active. | Immediately activated in the current session |
Run /reload-plugins to activate. | Panel closes and automatically reloads |
The plugin couldn't be loaded | Error occurred โ check the /plugin Errors tab |
VS Code์์ ์ค์นโ
- Type
/pluginsin the prompt input โ open the Manage plugins panel - Under the Plugins tab, search for the plugin and click Install
- Select an installation scope to complete
Changes take effect in open sessions immediately without a restart.
์ ธ์์ ์ง์ ์ค์น (๋น์ธํฐ๋ํฐ๋ธ)โ
For non-interactive terminal scripting without an active Claude Code session:
# Default is user scope
claude plugin install commit-commands@claude-plugins-official
# Install into project scope
claude plugin install formatter@your-org --scope project
If you have never run an interactive session on this machine, the official marketplace may not be registered. Run this before scripting:
claude plugin marketplace add anthropics/claude-plugins-official
์ค์น ๋ฒ์ ์ ํโ
| Scope | Location | Target |
|---|---|---|
| User scope (default) | ~/.claude/settings.json | All projects on this machine |
| Project scope | .claude/settings.json | All collaborators in this repo (git-committable) |
| Local scope | .claude/settings.local.json | Current user in this repo only |
Committing settings.json enables the plugin for collaborators, but each collaborator must still install the plugin on their machine.
๋ง์ผํ๋ ์ด์ค ์ถ๊ฐโ
To install plugins outside the official catalog (team-internal or community plugins), add the marketplace first:
# GitHub repository
/plugin marketplace add your-org/plugins
# Pin to branch or tag
/plugin marketplace add your-org/plugins#v1.2.0
# Git URL (GitLab, etc.)
/plugin marketplace add https://gitlab.example.com/group/marketplace.git
# Local directory
/plugin marketplace add ./my-marketplace
# Add marketplace and install plugin simultaneously (v2.1.275+)
/plugin install deploy-helper --marketplace your-org/plugins
Once added, find plugins under the /plugin Discover tab.
ํ๋ฌ๊ทธ์ธ ๊ด๋ฆฌโ
๋ชฉ๋ก ํ์ธโ
# Inside a session
/plugin
# From shell
claude plugin list
ํ์ฑํยท๋นํ์ฑํยท์ญ์ โ
# From shell
claude plugin enable formatter@your-org
claude plugin disable formatter@your-org
claude plugin uninstall formatter@your-org --scope project
Inside a session, navigate to /plugin โ Installed tab, press Space to toggle enable/disable, and Enter for the detailed menu to uninstall.
์ค์น๋ ํ๋ฌ๊ทธ์ธ์ ์ปจํ ์คํธ ๋น์ฉ ํ์ธโ
claude plugin details commit-commands@claude-plugins-official
The Always-on line indicates the token footprint added to every session.
์ ๋ฐ์ดํธโ
Plugins from the Anthropic official marketplace update automatically at session launch. Run /reload-plugins to apply updates to your active session.
To update an individual plugin immediately:
# Inside a session
/plugin โ Installed tab โ Update now
# From shell
claude plugin update commit-commands@claude-plugins-official
To turn off auto-updates for a marketplace, go to /plugin โ Marketplaces tab, select the marketplace, and choose Disable auto-update.
์์กด์ฑ(Dependencies) ๊ด๋ฆฌโ
When a plugin depends on other plugins, dependencies are installed automatically.
| Error | Cause | Solution |
|---|---|---|
dependency-unsatisfied | Dependency not installed or disabled | Run the claude plugin install command in the error message |
range-conflict | Conflicting versions required by multiple plugins | Update or uninstall one of the conflicting plugins |
dependency-version-unsatisfied | Installed version out of required range | Re-resolve with claude plugin install <dependency>@<marketplace> |
Automatically installed dependencies remain on disk after the parent plugin is removed. To clean them up:
# List and prune orphaned dependencies
claude plugin prune
# Uninstall and prune dependencies at the same time
claude plugin uninstall deploy-kit --prune
๋ค์ ๋จ๊ณโ
์ด ์ฑํฐ๋ฅผ ์๋ฃํ์ จ๋์?
ํ์ต ์ง๋๋ฅผ ์ฒดํฌํ์ฌ ๋์ ๋ก๋๋งต ๋ฌ์ฑ๋ฅ ์ ๋์ฌ๋ณด์ธ์.