{"version":"2.1.295","anchor":"plugin-scope-matching-for-disableuninstall-and-artifact-url","canonical_anchor":"plugin-scope-matching-for-disableuninstall-and-artifact-url","heading":"Disabling a plugin finds it even when its install location differs","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/plugin-scope-matching-for-disableuninstall-and-artifact-url","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Disabling a plugin finds it even when its install location differs\n\nDisabling a plugin now looks across install locations when there is no exact match, and the artifact tool gains a new check\n\n**Unclear.** It is not stated what the artifact tool's new check rejects or when that mode applies.\n\n**What**\n\nA plugin is an add-on package for Claude Code. It is installed at a scope, meaning a level such as your user account or one project. When you disable a plugin, Claude Code used to look only for an entry with exactly the same scope and project folder. It now tries other scopes if that exact match is not found.\n\nThe artifact tool also has a new check that, in one mode, rejects some requests with error code 23.\n\n**Why**\n\nThis may stop \"plugin not found\" errors when the scope you name does not match the one the plugin was installed at.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}