{"version":"2.1.310","anchor":"powershell-command-prefix-skipped-for-command-typed-args-wh","canonical_anchor":"powershell-command-prefix-skipped-for-command-typed-args-wh","heading":"PowerShell commands that run other commands get no permission prefix suggestion in some cases","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/powershell-command-prefix-skipped-for-command-typed-args-wh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### PowerShell commands that run other commands get no permission prefix suggestion in some cases\n\nClaude Code no longer suggests a permission prefix for a PowerShell command when it or its arguments are themselves commands, under one internal condition\n\n**Unclear.** The internal condition that switches this behaviour on is not identified, so it is unclear when you will see it.\n\n**What**\n\nWhen 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.\n\nFor 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.\n\n**Why**\n\nIn those cases you are asked about the specific command rather than offered a broader rule covering everything that starts the same way.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}