{"version":"2.1.314","anchor":"hook-source-reporting-distinguishes-pretooluse-only-hooks","canonical_anchor":"hook-source-reporting-distinguishes-pretooluse-only-hooks","heading":"Approval reasons now tell before-tool hooks apart from other causes","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/hook-source-reporting-distinguishes-pretooluse-only-hooks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Approval reasons now tell before-tool hooks apart from other causes\n\nWhen a tool call needs approval because of a hook, Claude Code now notes whether only a before-tool hook caused it\n\n**What**\n\nA hook is a command Claude Code runs automatically at set moments. A `PreToolUse` hook runs before a tool call and a `PostToolUse` hook runs after one. When a tool call needs your approval, Claude Code records what caused it. It now records `pre_tool_use_hook` when only a `PreToolUse` hook applies. It records `hook` when a path rule or several sources also apply. Before, any hook gave `hook` and everything else gave a path rule.\n\n**Why**\n\nThis is most likely used to keep track of approval reasons. You are unlikely to notice any change.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}