{"version":"2.1.317","anchor":"hook-errors-hide-commands-for-typed-hooks","canonical_anchor":"hook-errors-hide-commands-for-typed-hooks","heading":"Some hook errors no longer show the command that was run","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/hook-errors-hide-commands-for-typed-hooks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Some hook errors no longer show the command that was run\n\nFor hooks with a type label, warnings and errors now leave out the command text and say its program could not be started\n\n**Unclear.** It is not clear which hooks get a type label, so you may not know whether your own hook errors are affected.\n\n**What**\n\nHooks are commands that Claude Code runs automatically at set points, such as before or after a tool runs. When a hook has a type label, its warnings and errors no longer include the command text. If its program fails to launch, the error now says \"its program could not be started\". Before, these messages always included the command.\n\n**Why**\n\nThis changes the error text you see when such a hook fails, so the command itself may not appear in the message.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}