{"version":"2.1.280","anchor":"hooks-module-skip-reasons-now-surface-to-the-plugin-author-v","canonical_anchor":"hooks-module-skip-reasons-now-surface-to-the-plugin-author-v","heading":"Hooks-module skip reasons now surface to the plugin author via a notification channel, not just debug logs","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/hooks-module-skip-reasons-now-surface-to-the-plugin-author-v","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Hooks-module skip reasons now surface to the plugin author via a notification channel, not just debug logs\n\nPlugins are now notified directly when their hooks module is skipped, not just via a debug log line\n\n**What**\n\nWhen a plugin's hooks module (the file defining its custom hooks) is skipped \u2014 because of the `CLAUDE_CODE_ENABLE_FUNCTION_HOOKS` gate, `disableAllHooks`, `--bare` mode, or `allowManagedHooksOnly` \u2014 Claude Code already logged the reason to a debug log. Now it also delivers that reason directly to the owning plugin, through a new notification path, deduplicated so the same message isn't repeated.\n\n**Why**\n\nThis makes it easier for a plugin author to find out why their hooks aren't loading without having to dig through debug logs.\n\n- Area: Hooks\n- Names: `CLAUDE_CODE_ENABLE_FUNCTION_HOOKS`, `--bare`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}