Unclear Which hosts or commands lead to these new messages is not stated.
Claude Code has three new permission messages for when it cannot tell which files a command opens on a host (the machine the command runs on):
- Two ask you first before the command runs.
- One refuses the command outright when managed deny rules apply. Managed rules are permission rules set by an organisation's administrator.
The suggestions Claude Code offers for adding an allow rule are also handled differently when the request comes from an MCP skill. An MCP skill is a skill provided through an MCP server, which is an outside service that adds tools to Claude Code.
This sits behind the same server-controlled setting that already affected the "always allow" choice in permission prompts. It is off unless it is switched on remotely.
This tightens how commands from forwarded MCP skills get approved, especially when Claude Code cannot see which files they will touch.
tengu_valiant_crayon 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.312: off
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.312. It isn't a statement about your account. What a flag value here can and cannot tell you
Which hosts or commands lead to these new messages is not stated.