{"version":"2.1.323","anchor":"hooks-module-deny-reason-no-longer-logged","canonical_anchor":"hooks-module-deny-reason-no-longer-logged","heading":"Debug logs no longer record a hook's reason for denying an action","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/hooks-module-deny-reason-no-longer-logged","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Debug logs no longer record a hook's reason for denying an action\n\nWhen a hook denies an action, the debug log now records only the length of the reason, not the reason itself\n\n**What**\n\nA hook is a command you set up for Claude Code to run automatically at certain moments, and it can deny an action. When a hook module denies one, the debug log, a detailed file Claude Code writes for troubleshooting, used to record the full reason. It now records only how long the reason is. The reason itself is left out because it can quote the tool's input.\n\n**Why**\n\nWhatever was in a tool's input, such as file contents or commands, no longer ends up in your debug logs through a hook's deny reason.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}