{"version":"2.1.305","anchor":"permission-dialog-rule-updates-no-longer-carry-mode-changes","canonical_anchor":"permission-dialog-rule-updates-no-longer-carry-mode-changes","heading":"Approvals through remote permission dialogs no longer change the permission mode","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/permission-dialog-rule-updates-no-longer-carry-mode-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Approvals through remote permission dialogs no longer change the permission mode\n\nWhen a remote permission dialog returns changes, Claude Code now drops any mode switch and applies only the rule changes\n\n**Unclear.** It is not clear whether this path includes the SDK permission answers that can switch the mode.\n\n**What**\n\nWhen a permission question is answered through a remote or served dialog and the answer includes changes, Claude Code now removes any change of type `setMode` before applying the rest. A permission mode controls how Claude Code asks before acting, for example `acceptEdits`.\n\n- Rule additions in the answer still apply\n\n- A mode switch in the answer is ignored, so the session keeps its current permission mode\n\n**Why**\n\nApproving a single request this way cannot quietly change how later requests are handled.\n\n- Area: Permissions\n- Names: `acceptEdits`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}