{"version":"2.1.311","anchor":"hooks-module-loader-handles-errors-differently-and-orders-mo","canonical_anchor":"hooks-module-loader-handles-errors-differently-and-orders-mo","heading":"Plugin hooks that fail to load can now drop their plugin","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/hooks-module-loader-handles-errors-differently-and-orders-mo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Plugin hooks that fail to load can now drop their plugin\n\nSome kinds of hook load failure now drop the plugin they came from, and hook modules are put in order before loading\n\n**Unclear.** Which kinds of load failure cause a plugin to be dropped is not stated.\n\n**What**\n\nHooks are scripts that plugins can run automatically at certain moments, for example before or after Claude uses a tool. When Claude Code loads the code behind these hooks, it used to report every failure in the same way. It now treats some kinds of failure differently and drops the plugin they came from.\n\nThe hook modules are also sorted into an order before they are loaded.\n\n**Why**\n\nThis is about loading plugin hooks reliably. If a plugin of yours stops appearing, a hook that failed to load may be the reason.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}