{"version":"2.1.267","anchor":"hook-failure-reporting-split-into-separate-log-and-emit-step","canonical_anchor":"hook-failure-reporting-split-into-separate-log-and-emit-step","heading":"Hook-failure reporting split into separate log and emit steps","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/hook-failure-reporting-split-into-separate-log-and-emit-step","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Hook-failure reporting split into separate log and emit steps\n\nHook-failure handling now logs and reports failures as two separate steps\n\n**What**\n\nWhen a hook (a user-configured script that runs at certain points in Claude Code) fails, the code that handles this now performs two separate steps built from a shared failure report, instead of one combined step. This applies consistently both when a hook fails during normal use and during the startup\/bootstrap process.\n\n**Why**\n\nSplitting logging from reporting makes the failure-handling path clearer and more consistent between the two places it runs, though the finding does not indicate any visible change in behavior to the user.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}