{"version":"2.1.290","anchor":"hook-ask-decisions-now-also-cover-toolhost-person-only-asks","canonical_anchor":"hook-ask-decisions-now-also-cover-toolhost-person-only-asks","heading":"Hook permission message now mentions ToolHost person-only asks","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/hook-ask-decisions-now-also-cover-toolhost-person-only-asks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Hook permission message now mentions ToolHost person-only asks\n\nA permission log message now lists a ToolHost's person-only ask with ask rules and safety checks as needing the full permission check\n\n**Unclear.** Only the message wording is known to have changed, not whether the permission decision itself now behaves differently.\n\n**What**\n\nA hook is a script you configure to run at certain points, and it can approve or ask about a tool call. A tool call is one action Claude takes, such as running a command. Some cases still send the decision through Claude Code's full permission check. The log message for those cases used to mention only an ask rule or a safety check. It now reads \"an ask rule, a safety check or a ToolHost's person-only ask requires the full permission pipeline\".\n\n**Why**\n\nThe wording now treats a ToolHost's request to ask a person in the same way as ask rules and safety checks. These are all cases where a hook's approval alone is not enough.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}