{"version":"2.1.290","anchor":"permission-cards-can-be-marked-persononly","canonical_anchor":"permission-cards-can-be-marked-persononly","heading":"Some permission requests can now be reserved for a person to answer","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/permission-cards-can-be-marked-persononly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Some permission requests can now be reserved for a person to answer\n\nA permission request marked `personOnly` now skips automatic handling and goes straight to a person\n\n**Unclear.** It is not clear what sets the `personOnly` marking.\n\n**What**\n\nWhen Claude wants to do something that needs approval, Claude Code raises a permission request, which an automatic handler may answer. A request, or an ask result, marked with `personOnly` now skips that automatic handler and is sent to a person instead. Before, the handler was always called.\n\n**Why**\n\nSome approvals can be forced to a human rather than answered automatically.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}