Claude Code Manager
Install

~/.claude/plugins/

Claude Code plugins: installed, enabled, and why not

A plugin can be installed but off, on in one scope and off in another, or listed in settings with nothing installed behind it. The Plugins tab shows each plugin's real state and points out the ones that don't add up.

Install from the Marketplace Get it on Open VSX

installed_plugins.json · enabledPlugins

Installed is not the same as enabled

Claude Code keeps what's installed in ~/.claude/plugins/ and what's switched on in enabledPlugins in your settings files — per scope. The Plugins tab puts both side by side.

  1. per scopeOn or off, whereSee whether each plugin is enabled at user, project or local scope, and change it.
  2. mismatchPlugins that don't add upA plugin enabled from a marketplace your policy doesn't allow, or a settings entry with nothing installed behind it, is flagged.
  3. marketplacesBrowse and installBrowse the marketplaces you've added and install with Claude Code's own claude plugin install, run in a terminal.
  4. openLook insideOpen a plugin's folder or the settings file that enables it, or copy its ID.

FAQ

Questions, answered

Where does Claude Code install plugins?

In ~/.claude/plugins/. Which plugins are switched on is stored separately, under enabledPlugins in your settings files.

How does it install a plugin?

It runs Claude Code's own command, claude plugin install <plugin> --scope <scope>, in a terminal, so Claude Code does the install exactly as it would by hand.

Related

Free, open source, and it stays on your machine.

Apache-2.0. No telemetry, no account, no network client. Works with the Claude Code CLI and the official extension.

Install from the Marketplace Get it on Open VSX
code --install-extension vishalguptax.claude-manager