{"version":"2.1.280","anchor":"new-powershell-specific-error-classifiers-for-command-not-fo","canonical_anchor":"new-powershell-specific-error-classifiers-for-command-not-fo","heading":"New PowerShell-specific error classifiers for command-not-found","tier":"notice","area":"PowerShell","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-powershell-specific-error-classifiers-for-command-not-fo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New PowerShell-specific error classifiers for command-not-found\n\nClaude Code now recognizes PowerShell's own \"command not found\" errors\n\n**What**\n\nClaude Code's shell error classifier can now recognize two more ways a \"command not found\" error can look:\n\n- PowerShell's own wording, such as \"is not recognized as the name of a cmdlet\" or \"internal or external command\"\n\n- .NET's `CommandNotFoundException`\n\n**Why**\n\nWhen Claude Code runs a shell command that fails, it tries to classify the error so it can respond appropriately (for example, recognizing that a program simply isn't installed). Previously this matching was tuned for Unix-style shells; with these additions, the same kind of failure on Windows PowerShell is now caught too.\n\n- Area: PowerShell\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}