{"version":"2.1.295","anchor":"permission-request-hook-denials-get-the-hook-label-rewritten","canonical_anchor":"permission-request-hook-denials-get-the-hook-label-rewritten","heading":"Denials from permission hooks no longer show the hook's raw command","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/permission-request-hook-denials-get-the-hook-label-rewritten","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Denials from permission hooks no longer show the hook's raw command\n\nWhen a hook denies a permission request, its message is now labelled by hook type instead of showing the command\n\n**What**\n\nA hook is a command or script you configure Claude Code to run at set moments, and some hooks can answer permission requests, which are the prompts Claude Code raises before an action. When a hook blocks something, Claude Code replaces the `[command]:` label at the start of its message with a label naming the kind of hook, such as `[command hook]:`. Before, this applied only to blocking error messages. It now also applies to the message a hook gives when it denies a permission request.\n\n**Why**\n\nDeny messages from permission hooks no longer expose the raw command the hook runs.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}