{"version":"2.1.281","anchor":"account-set-permission-mode-is-now-recorded-for-remote-plan","canonical_anchor":"auto-mode-permission-context-rules-dropped-when-stripped-ru","heading":"Permission mode set on the account is now recorded and used for auto and plan decisions","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/account-set-permission-mode-is-now-recorded-for-remote-plan","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Permission mode set on the account is now recorded and used for auto and plan decisions\n\nClaude Code now records the account-set permission mode and uses it to decide auto-mode status and who answers remote plan-mode questions\n\n**Unclear.** The finding does not say what the additional check in plan mode tests.\n\n**What**\n\nThe permission mode controls how much Claude may do without asking you, for example auto mode or plan mode. Claude Code now keeps a record of the mode set for the account (`accountSetMode`), updated whenever the permission mode changes.\n\n- The check for whether the mode counts as auto now reads this account-set mode. Before, it only checked whether the mode was `auto`, or `plan` with a separate condition.\n\n- For remote tool calls, this recorded mode decides whether a host app may answer a plan-mode question or a person has to.\n\n- A new helper carries the current mode and the mode from before plan mode across a swap of permission settings, and keeps only the always-allow rules that are still present or were stripped.\n\n**Why**\n\nThis can change when auto mode is treated as active and who is asked to answer plan-mode questions in remote sessions. If you use auto or plan mode remotely, prompts may be routed differently than before.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}