{"version":"2.1.323","anchor":"plugin-load-synced-copy-can-give-way-to-own-copy","canonical_anchor":"plugin-load-synced-copy-can-give-way-to-own-copy","heading":"Your own copy of a plugin can now win over a synced copy","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugin-load-synced-copy-can-give-way-to-own-copy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Your own copy of a plugin can now win over a synced copy\n\nWhen a synced plugin and your own copy share a name, Claude Code can now keep your own copy, and disables plugins outside allowed folders\n\n**What**\n\nPlugins add features to Claude Code, and the same plugin can arrive both as a synced copy and as your own copy. Claude Code now handles this differently:\n\n- The name can stay with your own copy rather than the synced one. This is controlled by a setting Claude Code receives from its server.\n\n- Claude Code records when a synced copy gives way to your own.\n\n- Plugins outside the allowed folders are disabled.\n\n**Why**\n\nThis changes which copy you get when a synced plugin and a local one clash.\n\n- Flag `tengu_snug_starfish`: Not enough to say (read for one account on one subscription tier against v2.1.323; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}