{"version":"2.1.307","anchor":"model-switch-permission-decision-rewritten-to-return-an-ap","canonical_anchor":"model-switch-permission-decision-rewritten-to-return-an-ap","heading":"Approval decisions now name who is meant to approve","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/model-switch-permission-decision-rewritten-to-return-an-ap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Approval decisions now name who is meant to approve\n\nThe step that decides whether an approval request becomes a refusal now names the approver: the host, a person, or nobody\n\n**Unclear.** Whether this changes which requests are refused in runs where no one can answer a prompt is not settled.\n\n**What**\n\nWhen Claude wants to do something that needs your approval, Claude Code decides whether to ask or to refuse. That step used to turn the request into a refusal when a person had to decide but no prompt could be shown. It now says who should approve instead: the host program running Claude Code, a person, or nobody. It also checks whether the host can approve, and takes into account runs where requests should not go to the host.\n\n**Why**\n\nThis could change who gets asked to approve Claude's actions in runs with no one at the keyboard, such as scripted runs or runs inside another program.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}