{"version":"2.1.295","anchor":"plugin-lookup-falls-back-to-a-looser-scope-match","canonical_anchor":"plugin-lookup-falls-back-to-a-looser-scope-match","heading":"Matching a plugin to a project is less strict before falling back","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/plugin-lookup-falls-back-to-a-looser-scope-match","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Matching a plugin to a project is less strict before falling back\n\nWhen an exact match fails, Claude Code now tries a looser match to find which installed plugin applies, instead of taking the first one listed\n\n**What**\n\nWhen Claude Code works out which installed plugin something belongs to, it first looks for a plugin installed with exactly the same scope and project folder. A plugin is an add-on package that extends Claude Code, and its scope is where it was installed, such as for you or for one project. If no exact match was found, Claude Code used to take the first plugin in the list. It now tries an additional, looser match before falling back to that first entry.\n\n**Why**\n\nPlugins installed for a project may now be matched correctly even when the project path does not line up exactly.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}