Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeDocsClaude Code CLI 10 Nov 2026
One change · claude-code

Plugin loading reference changedplugins/loading

Nearest release: v2.1.322, published an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 10 Nov 2026 03:40 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 10 Nov 2026 04:07 UTC.

Upstream edited
Recorded here
Lines+21added
Lines−5removed
From line 171 where the diff opens
First seen 25 Sep 2026 this site's first read of the page
Recorded edits20to this page, all time

The whole hunk

from line 171, old and new numbered
/
lines
from line 171
171171 
172172### Enabled in project settings but not installed
173173 
174When a plugin's only `true` is in the project's `.claude/settings.json`, Claude Code doesn't fetch it onto a machine where it isn't installed, unless its marketplace entry has a [relative-path source](https://code.claude.com/docs/en/plugins/marketplace-reference.md#plugin-sources) or a [seed directory](https://code.claude.com/docs/en/plugins/org.md#seed-containers-and-ci) already holds it. Instead, the `/plugin` **Errors** tab shows `Plugin "<name>" is enabled in project settings but isn't installed here`.
174By default, a plugin enabled only in your project's `.claude/settings.json` doesn't load at session start until you install it on your machine. With the marketplace on your machine, the `/plugin` **Errors** tab shows [`Plugin "<name>" is enabled in project settings but isn't installed here`](https://code.claude.com/docs/en/plugins/troubleshooting#plugin-is-enabled-in-project-settings-but-isnt-installed-here) or [`Plugin "<name>" not cached at <path>`](https://code.claude.com/docs/en/plugins/troubleshooting#plugin-not-cached-at).
175175 
176A relative-path plugin needs no install record because it loads from the marketplace itself.
176> [!NOTE]
177>
178> If the tab shows neither message, [add the marketplace](https://code.claude.com/docs/en/plugins/install.md#add-a-marketplace) before you install. Find its source in the `extraKnownMarketplaces` setting of `.claude/settings.json`, or ask your maintainer.
177179 
178Claude Code fetches a plugin with an external source only when one of these sources sets it to `true`:
180To install, run this in a shell from the project, using the plugin's key in `enabledPlugins`:
181 
182```shell theme={null}
183claude plugin install <name>@<marketplace> --scope project
184```
185 
186To load the plugin, run `/reload-plugins` in your session or start a new session. Repeat the install in each of your clones, or use `--scope user` to cover all your projects.
187 
188You can load a plugin without an install in these cases:
189 
190* **In a [seed directory](https://code.claude.com/docs/en/plugins/org.md#seed-containers-and-ci)**: you have nothing to run
191* **Listed by a [relative path](https://code.claude.com/docs/en/plugins/marketplace-reference.md#plugin-sources) in a marketplace you added from a local path**: you have nothing to run, because the plugin loads at session start
192* **Listed by a relative path, such as `./plugins/formatter`, in the `marketplace.json` of a git marketplace you've added**: run `/reload-plugins` to load it for the current session only. To load it for one [non-interactive `-p` run](https://code.claude.com/docs/en/headless), set [`CLAUDE_CODE_SYNC_PLUGIN_INSTALL=1`](https://code.claude.com/docs/en/env-vars).
193 
194Claude Code fetches a plugin with an external source only when one of these sources sets the plugin to `true`:
179195 
180196* Your user settings
181197* A `.claude/settings.local.json` that git doesn't track
Feedback