{"version":"2.1.84","anchor":"powershell-tool-windows","canonical_anchor":"powershell-tool-windows","heading":"PowerShell Tool (Windows)","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.84\/e\/powershell-tool-windows","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.84","markdown":"### PowerShell Tool (Windows)\n\n**What**\n\nA dedicated PowerShell command execution tool for Windows users, providing native PowerShell syntax support with comprehensive security analysis.\n\n**Details**\n\n- Enabled via the `CLAUDE_CODE_USE_POWERSHELL_TOOL` environment variable on Windows\n- Uses `pwsh` (PowerShell 7+) for command parsing and execution\n- Full AST-based security analysis of PowerShell commands before execution\n- Validates PowerShell-specific patterns: cmdlet names, parameter types, pipeline chains, `.NET` type usage, script blocks\n- Recognizes dangerous patterns: `Invoke-Expression`, encoded commands, COM object creation, module loading, splatting, UNC paths\n- Read-only cmdlets (e.g. `Get-ChildItem`, `Get-Content`, `Select-String`, `Get-Process`) are auto-allowed\n- Handles PowerShell-specific security concerns: `-FilePath` execution, `-Command` re-invocation, `Start-Process` nesting\n- Provides PowerShell syntax guidance in tool description (variable syntax, pipe objects, here-strings, cmdlet naming)\n- Falls back gracefully if PowerShell is not installed\n- Enterprise policy enforcement: sandboxing policy blocks shell execution on native Windows when sandbox is unavailable\n\n**Evidence**\n\nPowerShell tool implementation (search for `\"PowerShell command\"`, `\"CLAUDE_CODE_USE_POWERSHELL_TOOL\"`, `\"Run PowerShell command\"`)"}