You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.305,
ImprovementsSection of the release
Unclear It is not clear whether this path includes the SDK permission answers that can switch the mode.
What
When 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.
Rule additions in the answer still apply
A mode switch in the answer is ignored, so the session keeps its current permission mode
Why
Approving a single request this way cannot quietly change how later requests are handled.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up acceptEdits, on Connect Claude Code to tools via MCP.* **Tool set to `ask`**: Claude Code prompts on every call with the reason `Your organization requires approval for this tool`. The prompt appears even in `acceptEdits`, `auto`, and `bypassPermissions` [permission modes](/docs/en/permissio…mcpsee the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether this path includes the SDK permission answers that can switch the mode.
Anthropic's documentation agreesAnthropic's documentation has since written up acceptEdits, on Connect Claude Code to tools via MCP.