{"version":"2.1.277","anchor":"hooks-module-not-loaded-diagnostics-reformatted-to-identify","canonical_anchor":"hooks-module-not-loaded-diagnostics-reformatted-to-identify","heading":"Hooks-module-not-loaded diagnostics reformatted to identify the module, not just the plugin name","tier":"internal","area":"Plugin Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/hooks-module-not-loaded-diagnostics-reformatted-to-identify","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Hooks-module-not-loaded diagnostics reformatted to identify the module, not just the plugin name\n\nLog messages about skipped plugin hooks now name the specific hooks module, not just the plugin\n\n**What**\n\nWhen a plugin's hooks module (the file defining its custom hooks) doesn't get loaded, Claude Code logs why. Previously the message used a fixed phrasing naming just the plugin and its source; now it uses a generated identifier that names the specific module instead. This applies across all three cases: the rollout flag being off, a duplicate plugin name, and `disableAllHooks` being set.\n\n**Why**\n\nMore specific log output makes it easier to tell exactly which hooks module was skipped and why, especially for plugins that define more than one.\n\n- Area: Plugin Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}