{"version":"2.1.296","anchor":"powershell-parser-passes-command-via-stdin-and-verifies-it","canonical_anchor":"powershell-parser-passes-command-via-stdin-and-verifies-it","heading":"PowerShell commands are checked to arrive intact before permission decisions","tier":"notice","area":"Windows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/powershell-parser-passes-command-via-stdin-and-verifies-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### PowerShell commands are checked to arrive intact before permission decisions\n\nClaude Code now sends PowerShell commands to its parser as plain input and checks the parser saw exactly the command it was sent\n\n**What**\n\nBefore deciding whether a PowerShell command needs your permission, Claude Code asks PowerShell to break the command into its parts. It used to embed the command inside an encoded script. It now sends the command as plain input and checks that PowerShell reports back the same command. If the two do not match, Claude Code treats the result as a failure (\"PowerShell parser did not receive the command intact\") instead of using it.\n\n**Why**\n\nPermission checks are only as good as the reading of the command behind them. This change makes sure Claude Code judges the command that will actually run, not a garbled copy of it.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}