You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PowerShellArea: what it touches
ImprovementsKind: in v2.1.280,
ImprovementsSection of the release
What
Claude Code's shell error classifier can now recognize two more ways a "command not found" error can look:
PowerShell's own wording, such as "is not recognized as the name of a cmdlet" or "internal or external command"
.NET's CommandNotFoundException
Why
When 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.
