{"version":"2.1.265","anchor":"new-hook-registration-validators-for-plugin-event-handlers","canonical_anchor":"new-hook-registration-validators-for-plugin-event-handlers","heading":"New hook-registration validators for plugin event handlers","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-hook-registration-validators-for-plugin-event-handlers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New hook-registration validators for plugin event handlers\n\nNew validators catch plugin hooks registered for events or hook types that don't actually exist\n\n**What**\n\nPlugins can register handlers for events (using `on(\"event\")`) and hooks. Two new validators now check this registration at load time: one confirms that a plugin's event patterns actually match a real, known event or method, and the other confirms that hooks the plugin declares were actually found when its hooks module was scanned. If either check fails, Claude Code now throws a descriptive error, such as one saying a pattern 'selects no event' or that a hook 'the scan of its hooks module did not see'.\n\n**Why**\n\nThis gives plugin authors clearer, more specific errors when they misconfigure event or hook registrations, instead of the problem failing silently or surfacing as a confusing downstream error.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}