{"version":"2.1.310","anchor":"permission-asks-policy-budget-no-longer-depends-on-userdriv","canonical_anchor":"permission-asks-policy-budget-no-longer-depends-on-userdriv","heading":"Change to how many times a policy may ask for permission","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/permission-asks-policy-budget-no-longer-depends-on-userdriv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Change to how many times a policy may ask for permission\n\nWhich limit applies to policy-driven permission asks now depends on one signal from the caller, not on whether the action came from a person\n\n**Unclear.** It is not shown what now decides which of the two limits applies.\n\n**What**\n\nA policy can ask you for permission a limited number of times. There is one limit for asks after something a person did and another for asks after an event from the server. Claude Code used to choose between them by checking whether the action was driven by a person or passed a remote check. It now chooses based on a single signal passed in when the ask is made.\n\n**Why**\n\nThis changes when a policy-driven ask is allowed to follow something you did.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}