Plugins reference changedplugins-reference
Nearest release: v2.1.239, published 5 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+10added
Lines−10removed
From line
340
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits37to this page, all time
The whole hunk
from line 340, old and new numbered
/
from line 340
340340
341341When you install a plugin, you choose a **scope** that determines where the plugin is available and who else can use it:
342342
343| Scope | Settings file | Use case |
344| :-------- | :---------------------------------------------- | :-------------------------------------------------------------------------- |
345| `user` | `~/.claude/settings.json` | Personal plugins available across all projects (default) |
346| `project` | `.claude/settings.json` | Team plugins shared via version control |
347| `local` | `.claude/settings.local.json` | Project-specific plugins, gitignored when Claude Code saves a setting to it |
348| `managed` | [Managed settings](/docs/en/settings#settings-files) | Managed plugins (read-only, update only) |
343| Scope | Settings file | Use case |
344| :-------- | :--------------------------------------- | :-------------------------------------------------------------------------- |
345| `user` | `~/.claude/settings.json` | Personal plugins available across all projects (default) |
346| `project` | `.claude/settings.json` | Team plugins shared via version control |
347| `local` | `.claude/settings.local.json` | Project-specific plugins, gitignored when Claude Code saves a setting to it |
348| `managed` | [Managed settings](/docs/en/managed-settings) | Managed plugins (read-only, update only) |
349349
350Plugins use the same scope system as other Claude Code configurations. For installation instructions and scope flags, see [Install plugins](/docs/en/discover-plugins#install-plugins). For a complete explanation of scopes, see [Configuration scopes](/docs/en/settings#configuration-scopes).
350Plugins use the same scope system as other Claude Code configurations. For installation instructions and scope flags, see [Install plugins](/docs/en/discover-plugins#install-plugins). For a complete explanation of scopes, see [Configuration scopes](/docs/en/settings#where-settings-live).
351351
352352***
353353
from line 570
570570
571571Before v2.1.207, these fields substituted `${user_config.KEY}` values; update plugins that relied on this.
572572
573Non-sensitive values are stored under the [`pluginConfigs`](/docs/en/settings#pluginconfigs) key in your user `settings.json` as `pluginConfigs[<plugin-id>].options`.
573Non-sensitive values are stored under the [`pluginConfigs`](/docs/en/settings-reference#pluginconfigs) key in your user `settings.json` as `pluginConfigs[<plugin-id>].options`.
574574
575575Sensitive values go to the macOS Keychain, or to `~/.claude/.credentials.json` on platforms where no supported keychain is available. Keychain storage is shared with OAuth tokens and has an approximately 2 KB total limit, so keep sensitive values small.
576576
from line 582
582582
583583When more than one source sets the same key, managed settings take precedence, then `--settings`, then user settings. The [`--setting-sources`](/docs/en/cli-reference#cli-flags) flag narrows the list further.
584584
585Entries in a project's `.claude/settings.json` or `.claude/settings.local.json` are ignored. Both files live in the workspace, so a cloned repository could supply values there, and those values would flow into plugin hook commands, MCP server configs, LSP commands, and monitor commands. Before v2.1.207, these entries were read. The restriction is specific to `pluginConfigs`: [`enabledPlugins`](/docs/en/settings#enabledplugins) still honors project and local settings.
585Entries in a project's `.claude/settings.json` or `.claude/settings.local.json` are ignored. Both files live in the workspace, so a cloned repository could supply values there, and those values would flow into plugin hook commands, MCP server configs, LSP commands, and monitor commands. Before v2.1.207, these entries were read. The restriction is specific to `pluginConfigs`: [`enabledPlugins`](/docs/en/settings-reference#enabledplugins) still honors project and local settings.
586586
587587### Channels
588588
No line in this hunk matches that.