Unclear It is not clear whether this check applies to plugins from every source or only some.
What
When Claude Code loads a plugin, it now checks that these files really sit inside the plugin's own folder:
- the plugin manifest, the file that describes the plugin
monitors/monitors.jsonsettings.json
The check matters when the plugin uses a symlink or junction, which is a shortcut that makes a file appear in one place while it lives in another. If the manifest points outside the folder, the plugin is not loaded and you see a message beginning "Plugin not loaded: its manifest". Before, these files were read directly with no such check.
Why
This is a security safeguard. It stops a plugin from pulling files from elsewhere on your computer. If a plugin you use relies on shortcuts that point outside its folder, it may stop loading.
settings.json
Desktop application modified, high confidence
* **Local sessions**: you can edit files inside the session's working directory, except some view-only ones such as `.mcp.json` and `.claude/settings.json`. To change one, [open it in another app](#open-files-in-other-apps).see the edit
settings.json
Create custom subagents modified, high confidence
1. Turn [fork mode](#turn-fork-mode-on-or-off) off by setting `CLAUDE_CODE_FORK_SUBAGENT` to `0`, for example in [`settings.json`](/docs/en/settings):see the edit
settings.json
Configure permissions modified, high confidence
Converts any permission prompt into a denial, without calling `canUseTool`, though a [mod](/docs/en/plugins/mods/overview) you installed can still approve [some of those calls](/docs/en/permissions#precedence-among-rules-hooks-and-mods). T…see the edit
settings.json
Manage mods for your organization modified, high confidence
* **Repositories can't set them**: Claude Code reads both settings from managed settings, never from a repository's settings file. A user can set them in `~/.claude/settings.json` to order their own mods only on a machine with no managed s…see the edit
settings.json
Code in Claude Desktop on 3P modified, high confidence
Claude Code can also be configured directly by deploying a [`managed-settings.json` file](https://code.claude.com/docs/en/settings#settings-files), an OS configuration profile for Claude Code, or, with the Claude API as the inference provi…see the edit
settings.json
Claude for Government changelog modified, high confidence
* Changed plugin uploads to ask for the Runs code confirmation when a plugin's `settings.json` sets anything other than its default agent or a `$schema` reference, such as a status line.see the edit
settings.json
Code in Claude Desktop on 3P modified, high confidence
> Without a Claude Code `managed-settings.json` file, OS profile, or server-managed settings, Claude Desktop's policy applies automatically and you don't need to set `parentSettingsBehavior`.see the edit
settings.json
Set up Claude Code for your organization modified, high confidence
| File-based managed | macOS: `/Library/Application Support/ClaudeCode/managed-settings.json` Linux and WSL: `/etc/claude-code/managed-settings.json` Windows: `C:\Program Files\ClaudeCode\managed-settings.json` | Medium | All |see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear whether this check applies to plugins from every source or only some.
Anthropic's documentation agrees
settings.json on Desktop application