{"version":"2.1.321","anchor":"hooks-module-removal-now-cancels-pending-plugin-notify","canonical_anchor":"hooks-module-removal-now-cancels-pending-plugin-notify","heading":"Removing a plugin's hooks now also cancels its pending notifications","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/hooks-module-removal-now-cancels-pending-plugin-notify","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Removing a plugin's hooks now also cancels its pending notifications\n\nWhen a plugin stops naming a hooks module, Claude Code reloads it and cancels any notification still pending for that plugin\n\n**What**\n\nPlugins add features to Claude Code, and some include hooks, scripts that run at set moments. When a plugin's manifest (its description file) no longer names a hooks module, Claude Code now reloads it and cancels any notification still pending for that plugin. Before, it reloaded only when the plugin was already known, and nothing was cancelled.\n\n**Why**\n\nThis is a small fix to how plugins are tidied up when their hooks are removed.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}