{"version":"2.1.323","anchor":"powershell-parser-detects-in-string-constants","canonical_anchor":"powershell-parser-detects-in-string-constants","heading":"PowerShell permission checks catch the stop-parsing marker in more places","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/powershell-parser-detects-in-string-constants","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### PowerShell permission checks catch the stop-parsing marker in more places\n\nClaude Code now spots the PowerShell `--%` marker inside quoted text too, not only as a separate word\n\n**What**\n\nIn PowerShell, `--%` tells PowerShell to stop interpreting the rest of a line and pass it on as written. Claude Code looks for this marker when it checks whether a PowerShell command needs your permission. Before, it only found the marker as a separate word. It now also finds it when it appears as a text value in the command.\n\n**Why**\n\nThis makes the permission check for PowerShell commands stricter.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}