{"version":"2.1.301","anchor":"plugin-autoupdate-notification-now-distinguishes-reload-fail","canonical_anchor":"plugin-autoupdate-notification-now-distinguishes-reload-fail","heading":"Plugin auto-update tells you when reloading the updated plugins failed","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/plugin-autoupdate-notification-now-distinguishes-reload-fail","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Plugin auto-update tells you when reloading the updated plugins failed\n\nAfter plugins update themselves, a failed reload now gets its own notice telling you to run \/reload-plugins instead of a restart message\n\n**What**\n\nPlugins are add-ons that extend Claude Code, and they can update themselves in the background. After an update, Claude Code tries to reload them and then shows a notice. That notice now depends on how the reload went:\n\n- ok: the plugins were reloaded\n\n- with errors: the plugins were reloaded but had errors, and the notice points you to `\/plugin`\n\n- failed: the reload did not work, and the notice says to run `\/reload-plugins` to apply the update\n\n- skipped: the reload did not run\n\nBefore, a failed reload and a skipped reload both showed the message asking you to restart. The plugin names in the notice now come from the list of plugins that were actually updated.\n\n**Why**\n\nIf the background reload fails, you now see that clearly and get a fix that does not need a restart.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}