{"version":"2.1.296","anchor":"pretooluse-hook-stop-reason-is-appended-correctly","canonical_anchor":"pretooluse-hook-stop-reason-is-appended-correctly","heading":"Blocking PreToolUse hooks now show their full reason","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/pretooluse-hook-stop-reason-is-appended-correctly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Blocking `PreToolUse` hooks now show their full reason\n\nWhen a `PreToolUse` hook blocks a tool, the hook's extra text is now added to the error message instead of being lost\n\n**What**\n\nA `PreToolUse` hook is a command you configure to run before each tool call. A tool call is an action Claude takes, such as running a command or editing a file, and the hook can block it. When it does, the error begins \"Execution stopped by PreToolUse hook\". Any extra text from the hook is now added to that message. Before, the text could be lost. Images the hook returns are also now handled correctly.\n\n**Why**\n\nIf you use blocking hooks, the tool result now shows the full reason the hook gave.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}