{"version":"2.1.295","anchor":"powershellshell-command-parsing-uses-a-different-whitespace","canonical_anchor":"powershellshell-command-parsing-uses-a-different-whitespace","heading":"Command names may be split differently when checking permissions","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/powershellshell-command-parsing-uses-a-different-whitespace","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Command names may be split differently when checking permissions\n\nUnder an internal check, Claude Code splits shell and PowerShell commands into words a new way when finding the command name\n\n**Unclear.** What the internal check tests and what the new splitting rule matches are not known.\n\n**What**\n\nTo decide whether a command is safe or matches a permission rule, Claude Code first picks out the command's name, its first word. In the PowerShell safe-command check, PowerShell being the Windows command shell, and in a second place that reads command names, Claude Code now uses a different rule for splitting on spaces and trimming the start of the command when an internal check is true. Before, it split on any whitespace.\n\n**Why**\n\nThe command name decides which permission rules apply, so a change here can change which commands are allowed without asking.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}