{"version":"2.1.295","anchor":"always-allow-permission-changes-now-trigger-an-emit","canonical_anchor":"always-allow-permission-changes-now-trigger-an-emit","heading":"Choosing to always allow an action now sends an update signal right away","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/always-allow-permission-changes-now-trigger-an-emit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Choosing to always allow an action now sends an update signal right away\n\nWhen you choose to always allow an action, Claude Code now signals the change immediately, before the rule is saved\n\n**Unclear.** What visible effect the new update signal has is not known.\n\n**What**\n\nWhen you answer a permission prompt by choosing to always allow an action, Claude Code saves a permission rule. It now also sends out an update signal straight away, before the rule is written to disk. Previously it only saved the rule.\n\n**Why**\n\nThis may make new permission rules show up in Claude Code right away instead of after saving finishes.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}