{"version":"2.1.314","anchor":"always-allow-rule-offered-on-host-dialog-accept","canonical_anchor":"always-allow-rule-offered-on-host-dialog-accept","heading":"Accepting a permission prompt in a host app can now save an always-allow rule","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/always-allow-rule-offered-on-host-dialog-accept","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Accepting a permission prompt in a host app can now save an always-allow rule\n\nApproving a permission request shown by an IDE or SDK host now also creates and saves an always-allow rule, with some exceptions\n\n**Unclear.** It is not clear which host apps show this dialog, so it is unclear whether your setup saves rules this way.\n\n**What**\n\nA permission prompt is the question Claude Code asks before it does something like running a command or editing a file. Some prompts are shown by the program hosting Claude Code, such as an editor (IDE) or an app built with the SDK. When you accept one of these host prompts, Claude Code now also creates and saves an always-allow rule, which lets the same action through later without asking. Before, accepting recorded only the permission for that request and for the session.\n\nNo rule is saved in these cases:\n\n- the action runs remotely\n\n- the tool that asked does not allow permission changes\n\n- `askSuppressesAlwaysAllowRule` is set\n\n**Why**\n\nAccepting a prompt in a host app may now leave a saved rule behind. Later requests of the same kind would then go through without asking. Check your saved permission rules if you approve prompts this way.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}