{"version":"2.1.251","anchor":"claude-plugin-update-distinguishes-a-deferred-plugin-from-a-","canonical_anchor":"claude-plugin-update-distinguishes-a-deferred-plugin-from-a-","heading":"claude plugin update distinguishes a deferred plugin from a skipped one","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/claude-plugin-update-distinguishes-a-deferred-plugin-from-a-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### `claude plugin update` distinguishes a deferred plugin from a skipped one\n\nPlugin update failures now tell you the exact command to rerun.\n\n**What**\n\nFor plugins that come from a command, update failures now separate a plugin the background update skipped but that a per-session re-resolve may still pick up, from one that is genuinely inactive, and print the exact `plugin update` command to run yourself.\n\n**Details**\n\n- Whether the per-session re-resolve happens is itself conditional, and the messaging says so rather than promising it.\n\n**Evidence**\n\n`it is left to the per-session re-resolve (when that is enabled) or an explicit update`\n\n- Area: Plugins\n- Names: `claude plugin update`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5"}