guideHow to manage Claude Code plugins after installation
Translated from Korean. View original
If an installed plugin does not appear, or keeps appearing in other projects, check its installation scope first. This guide covers finding and managing plugins in terminal-based Claude Code. Separating installed features, external-service connections and current activation status helps identify where a problem occurs.
Where do I open plugin management?
Enter /plugin in the Claude Code conversation input, not the terminal prompt before launching the program. Discover is for finding plugins to install; Installed manages items already installed.
Menu names here follow the official documentation. If your screen differs, check the version with claude --version in the terminal and consult the update instructions for your installation method.
Which installation scope should I choose?
User applies to your own use across projects, Project is shared with collaborators in the repository, and Local is for your own use in that repository. When testing privately in a company repository, check whether your choice changes shared configuration.
Before installing, check both the plugin's name and provider so you can distinguish similarly named tools. Start with one plugin and test it on a task you actually need.
What should I check after installation?
Check that the plugin is enabled under Installed and read its component list. If it provides a skill, try a small task using the invocation name in its description. A short note is easier to check than a task changing many files.
A plugin that needs an external service may require separate authentication. Do not assume installation completed the connection; verify that a read operation actually works.
- Check which features were added.
- Check required account connections or separate programs.
- Check the result with one small input.
Should I reinstall if it does not work?
First check the error in /plugin under Errors. Reinstalling repeatedly will not fix a missing required program. Record the error, plugin name and Claude Code version to narrow the cause.
Example question: ‘I see the error below with this plugin. My Claude Code version is … and I installed it with Local scope. Is the issue installation, authentication or a separate program? Original error: …’
How is temporarily disabling different from removing?
Disabling an item under Installed lets you turn it back on later. Disabling plugins one by one can also help identify which one causes a problem. To remove a feature you no longer use, check its scope first.
Removing a plugin may be separate from revoking access in an external service. To disconnect the account, also check that service's connected-app settings. Removing a marketplace can affect plugins installed from it, so distinguish that from managing an individual plugin.
Frequently asked questions
Q. A teammate installed it; why does it not work on my computer? A. Even with shared configuration, a required local program or your own authentication may be missing. Check the error and the provider's installation guide.
Q. Should I enter /plugin in Claude on the web? A. This guide is for Claude Code. Follow the relevant product instructions for web and other apps.