{"version":"2.1.275","anchor":"npm-sourced-plugins-skip-the-local-plugin-cant-be-updated","canonical_anchor":"npm-sourced-plugins-skip-the-local-plugin-cant-be-updated","heading":"npm-sourced plugins skip the \"local plugin can't be updated remotely\" check","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/npm-sourced-plugins-skip-the-local-plugin-cant-be-updated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### npm-sourced plugins skip the \"local plugin can't be updated remotely\" check\n\nPlugins installed from npm are now treated like local plugins for update eligibility\n\n**What**\n\nWhen Claude Code checks whether a plugin can be updated remotely, plugins sourced from the npm marketplace are now special-cased: the check that normally blocks remote updates for local plugins returns immediately (no block) for npm-sourced plugins, and the plugin-info logic treats npm the same way it treats local plugins.\n\n**Why**\n\nThis avoids incorrectly treating npm-installed plugins the same as ordinary local plugins for the purposes of the \"can't update a local plugin remotely\" restriction.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}