{"version":"2.1.299","anchor":"powershell-new-object-argument-with-empty-text-after-colon-n","canonical_anchor":"powershell-new-object-argument-with-empty-text-after-colon-n","heading":"PowerShell New-Object commands with an empty type name now ask first","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/powershell-new-object-argument-with-empty-text-after-colon-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### PowerShell New-Object commands with an empty type name now ask first\n\nClaude Code now asks permission for a PowerShell New-Object argument with nothing after its colon, since it cannot tell what would be created\n\n**What**\n\nPowerShell is the Windows command shell. Before Claude Code runs a PowerShell command, it checks whether the command is safe enough to run without asking you. It used to skip over any argument to `New-Object` that contained a colon. It now asks for your permission when nothing follows that colon, because it cannot tell which kind of .NET object the command would create. .NET is the Windows programming framework that PowerShell builds on.\n\n**Why**\n\nThis closes a gap in the safety check, so some PowerShell commands that used to run straight away will now ask you first.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}