Claude Code 2.1.325 skips plugins' unsafe paths and links and warns about plugin code
Plugin loading now skips some unsafe paths and links in a plugin's folder, claude plugin validate reports them, and plugin prompts say plugins can run code on the computer.
Claude Code 2.1.325, dated November 13, 2026, changes how the tool loads plugins. Plugin loading now skips some unsafe paths and links inside a plugin's folder, and the claude plugin validate command reports them. The same release rewrites the warnings shown around plugins so they say plugins can run code on the user's computer, with access to files and the shell. The release notes don't say which paths or links count as unsafe. A reader can't tell from the notes how broad the skipping is or what happens to a plugin that depends on a skipped file.
The warning change is listed under improvements. Add-marketplace confirmations, plugin recommendation prompts and the plugin install warning now carry the new wording. In the VS Code extension, the install link's marketplace confirmation button now reads Trust marketplace and continue. The notes list this as an improvement and don't say whether anything about how plugins run has changed. The warning describes running code with access to files and the shell.
Packaging changes matter for a different reason. Plugin MCP bundles, which use the .mcpb and .dxt extensions, now unpack under the plugins directory instead of a folder named .mcpb-cache inside the plugin's own folder. The notes say this lets read-only plugin folders load. A bundle fetched by URL downloads again once after the update. Two other plugin-adjacent changes also affect existing setups. Nested .claude/skills folders in plugins loaded with --plugin-dir no longer load when Claude Code is started above the plugin, so users should start it in the plugin folder instead. Plugins from a remote marketplace listed in managed settings' prependPlugins or appendPlugins now count as the organization's, and pluginDigests is deprecated and ignored.
Marketplace ref pinning also changes. The ref field now accepts the full ID of any commit on a branch or tag. The notes say clients before this version can't clone such a pin, so a marketplace pinned that way stops loading on older versions.
What changed
Plugin loading now skips some unsafe paths and links in a plugin's folder, and plugin MCP bundles now unpack under the plugins directory instead of a .mcpb-cache folder inside the plugin's own folder.
Type: Breaking change · Takes effect: Friday, November 13, 2026 · Applies to: Claude Code 2.1.325, .mcpb, .dxt
Why it matters
Companies distributing or installing internal Claude Code plugins face stricter checks and clearer warnings about the access plugins receive.
What you can do
Run claude plugin validate on internal plugins before the next rollout to see which paths or links are now skipped.
Original source
Where we saw it
Claude Code changelog
AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it. How it works