Note plugin hooks skipped by duplicate name
CHANGELOG · original
Added a note in /plugin on a plugin whose hooks are left out because another enabled plugin has the same name Open official changelog ↗ Documentation
Documentation excerpt
Name conflicts
When enabled plugins from different origins share a manifest name, this order decides which one loads, from highest precedence to lowest:
- A plugin whose id appears in managed settings
enabledPlugins, astrueorfalse. A--plugin-dircopy whose manifest name matches the id's name part isn't loaded, and you see--plugin-dir copy of "<name>" ignored: plugin is locked by managed settings - An enabled
--plugin-dir,--plugin-url, orCLAUDE_CODE_PLUGIN_DIRSplugin. It replaces a same-named installed marketplace plugin or skills-directory plugin:- An installed marketplace plugin: replaced silently.
claude plugin liststill shows the marketplace row as enabled, because that row reflects your settings. Only the log Claude Code writes under~/.claude/debug/when you start with--debugrecordsPlugin "<name>" from --plugin-dir overrides installed version - A skills-directory plugin: replaced with a
/pluginErrors tab row that readsNot loaded — the name "<name>" is already taken by a session-only plugin (--plugin-dir / --plugin-url), which takes precedence
- An installed marketplace plugin: replaced silently.
- An installed marketplace plugin. A skills-directory plugin of the same name gets the same
Not loadedrow, naming the installed plugin - A skills-directory plugin. Between two of these, the copy under
~/.claude/skills/loads and the project's.claude/skills/copy is dropped, with a row that says which path shadowed it - A plugin synced from claude.ai. When an enabled plugin from any other origin matches its name, Claude Code loads that plugin and reports the synced copy as not loaded. To use the claude.ai copy instead, disable your own copy
Because the order compares manifest names, a --plugin-dir plugin named hello-plugin replaces hello@example-marketplace when that plugin's manifest also says "name": "hello-plugin".
Hooks when two enabled plugins share a name
When you install and enable two plugins with the same manifest name from different marketplaces, both appear as enabled in /plugin, but the hooks of one of them are left out. One plugin per name registers the hooks in its hooks/hooks.json, and one plugin per name loads a hooks module. When your organization's managed settings turn on one of the copies, that copy holds the name. Otherwise the copy Claude Code loads first holds it.
To see which copy holds the name, run /plugin in your session and open the Errors tab. A note there for the copy whose hooks were left out names the copy that holds the name, and the left-out copy's details show the same note. For hooks/hooks.json hooks the note begins Its hooks.json hooks do not run, and for a hooks module it begins Its hooks module does not load. The note requires Claude Code v2.1.296 or later.
To run the left-out copy's hooks instead, disable or uninstall the copy that holds the name, then run /reload-plugins in your session. The reload registers the remaining copy's hooks and clears the note. When the copy that holds the name is one your managed settings turn on, you can't disable it, and the other copy's hooks stay off while both are installed.
Keep a session-only plugin from loading
To keep a --plugin-dir plugin from shadowing anything, or to turn one off when a parent process passes the flag for you, set its id to false in any settings file. For a plugin whose manifest name is hello-plugin, the entry is "enabledPlugins": {"hello-plugin@inline": false}. A disabled session-only plugin doesn't shadow, so the marketplace or skills-directory copy loads instead.
Documentation snapshot · 2026-11-20