Plan mode is the mode where Claude plans its work before making changes. In plan mode, calling a tool that can change things used to trigger the "Cannot call ... while in plan mode." prompt only for MCP tools, which come from external tool servers. It now also applies to tools that can change things and have a setting of their own for the current session. For those tools, the sandbox also no longer approves Bash commands on its own.
There is also a change for computer use, where Claude controls your screen, mouse and keyboard. A permission rule that allows a whole tool no longer approves computer-use actions automatically, unless the action only looks at the screen. This applies when computer-use checks are on: either through a remotely controlled switch that is off unless it is switched on remotely, or through the computerUseChecks setting.
Permission handling is stricter for tools served into a session and for computer-use actions, so you may see more approval prompts for them.
tengu_quirky_shore Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.284: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.284. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not clear what makes a tool count as having a session-level setting of its own.
New in this build: tengu_quirky_shore