PowerShell commands that run other commands get no permission prefix suggestion in some cases
Claude Code no longer suggests a permission prefix for a PowerShell command when it or its arguments are themselves commands, under one internal condition
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.310,
ImprovementsSection of the release
Unclear The internal condition that switches this behaviour on is not identified, so it is unclear when you will see it.
What
When Claude Code asks your permission to run a command, it can suggest a prefix to approve. A prefix is the start of a command, so that later commands beginning the same way are allowed too.
For PowerShell commands, Claude Code now suggests no prefix when the command or its arguments are themselves commands to be run, provided an internal condition is met.
Why
In those cases you are asked about the specific command rather than offered a broader rule covering everything that starts the same way.
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 doubtThe internal condition that switches this behaviour on is not identified, so it is unclear when you will see it.