Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.299entry #185

Claude Code v2.1.299 ·

Hooks that look written for bash can now be flagged on PowerShell setups

On a machine whose default shell is PowerShell, a command hook that isn't set up for PowerShell can now be flagged with a "noBash" reason

You'll notice Improvements
JSON All of v2.1.299
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
WindowsArea: what it touches
ImprovementsKind: in v2.1.299,
ImprovementsSection of the release

Unclear How the "noBash" reason is shown to the user, or what it does to the hook, is not stated.

What

A hook is a command you set to run automatically at a given moment, for example before a tool runs. A shell is the program that runs typed commands, such as bash or PowerShell. Claude Code now flags a command hook with the reason "noBash" when all of these are true:

  • The default shell is PowerShell.
  • The hook does not set its shell to powershell.
  • The hook has no args.
  • The hook does not set onFailure to continue.
  • A further check on the hook's event passes.

Before, this check could only report a problem with a setting, or nothing.

Why

On Windows setups that use PowerShell, a hook written for bash can now be picked out instead of being run in the wrong shell without notice.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtHow the "noBash" reason is shown to the user, or what it does to the hook, is not stated.

See this entry in the whole of v2.1.299 →

Feedback