Plugin loading reference changedplugins/loading
Upstream edited this page at 10 Oct 2026 18:25 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:37 UTC.
Upstream edited
Recorded here
Lines+8added
Lines−12removed
From line
4
where the diff opens
First seen
25 Sep 2026
this site's first read of the page
Recorded edits15to this page, all time
### Plugins synced from claude.ai ### Hooks when two enabled plugins share a name
The whole hunk
from line 4, old and new numbered
/
from line 4
44
55Use this page when a plugin didn't load, loaded a different copy than you expected, or didn't pick up an update, and you want to see which source, settings scope, or file on disk decided that. It gives the rules Claude Code applies when a session starts and each time you run `/reload-plugins`. You can also ask Claude to read this page and diagnose your setup.
66
7<Note>
8 These cases are covered on other pages:
7> [!NOTE]
8>
9> These cases are covered on other pages:
10>
11> * **Install, enable, disable, and update steps**: see [Install and manage plugins](/docs/en/plugins/install)
12> * **You have a specific error message**: see [Troubleshoot plugins](/docs/en/plugins/troubleshooting)
913
10 * **Install, enable, disable, and update steps**: see [Install and manage plugins](/docs/en/plugins/install)
11 * **You have a specific error message**: see [Troubleshoot plugins](/docs/en/plugins/troubleshooting)
12</Note>
13
1414Start with [Check which stage a plugin reached](#check-which-stage-a-plugin-reached) for the three stages an installed plugin passes through, or go to the section that matches what you're seeing:
1515
1616* A plugin you turned off still loads: [Find where a plugin is enabled](#find-where-a-plugin-is-enabled)
from line 82
8282
8383For how to write `--plugin-dir` and skills-directory plugins, see [Create plugins](/docs/en/plugins/create).
8484
85<h3 id="synced-plugins">
86 Plugins synced from claude.ai
87</h3>
85### Plugins synced from claude.ai
8886
8987A plugin you turn on for your claude.ai account also loads in Claude Code, alongside the plugins you install from marketplaces. That includes plugins your organization turns on for its members. Each of these plugins loads as `<name>@synced`, with no marketplace and no [install record](#check-which-stage-a-plugin-reached).
9088
from line 367
369367
370368Because 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"`.
371369
372<h3 id="hooks-when-two-enabled-plugins-share-a-name">
373 Hooks when two enabled plugins share a name
374</h3>
370### Hooks when two enabled plugins share a name
375371
376372When 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](/docs/en/plugins/mods/overview). 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.
377373
No line in this hunk matches that.