{"version":"2.1.280","anchor":"new-hooks-module-did-not-load-error-path","canonical_anchor":"new-hooks-module-did-not-load-error-path","heading":"New \"hooks module did not load\" error path","tier":"internal","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-hooks-module-did-not-load-error-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New \"hooks module did not load\" error path\n\nClaude Code logs a clearer \"hooks module did not load\" error with the specific reason when a hooks module fails to load\n\n**What**\n\nWhen a hooks module (a script that plugs custom automation into Claude Code's tool calls) fails to load, Claude Code now builds and logs an error message reading \"hooks module did not load\" along with the specific reason for the failure. The failure can also be passed along to a callback function so other code can react to it.\n\n**Why**\n\nThis makes it easier to see why a hooks module failed to load instead of the failure happening silently or without a clear reason attached.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}