{"version":"2.1.314","anchor":"permission-prompts-may-skip-asking-when-only-a-person-can-an","canonical_anchor":"permission-prompts-may-skip-asking-when-only-a-person-can-an","heading":"Permission checks handle questions only a person can answer differently","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/permission-prompts-may-skip-asking-when-only-a-person-can-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Permission checks handle questions only a person can answer differently\n\nPermission checks now pass along whether a question can only be answered by a person, which changes the flow in some cases\n\n**Unclear.** It is not clear what the new signal does, so whether you will be asked more or less often is unknown.\n\n**What**\n\nA permission check is when Claude Code decides whether an action needs your approval. Some of these questions are marked as ones only a person can answer. When that is so, and there is a way to settle the question without asking, and hooks cannot refuse it, the permission check is now told something different. Hooks are your own scripts that run at set points. One tool also gained a step that prepares how permission rules are matched against it.\n\n**Why**\n\nThis changes how Claude Code handles permission questions that only a person can answer.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}