{"version":"2.1.281","anchor":"plugin-update-infers-scope-when-none-is-given","canonical_anchor":"plugin-update-infers-scope-when-none-is-given","heading":"Plugin update infers scope when none is given","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/plugin-update-infers-scope-when-none-is-given","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Plugin update infers scope when none is given\n\nUpdating a plugin without naming a scope now picks local, project or user, whichever has an install, then falls back to managed\n\n**What**\n\nA plugin can be installed in different scopes, meaning different places it applies: `local`, `project`, `user`, or `managed` by an organisation. Updating a plugin no longer requires you to say which scope. When none is given, Claude Code:\n\n- Checks `local`, then `project`, then `user`, and uses the first one that has an install.\n\n- Prefers installs that match the current directory.\n\n- Falls back to `managed` if none match.\n\n**Why**\n\nYou can update a plugin without first working out where it was installed."}