Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.299 ·

Clearer message when a hook is blocked because Git Bash is missing

A hook blocked on Windows because Git Bash wasn't found now gets its own explanation instead of being blamed on personal-config restrictions

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

A hook is a command of your own that Claude Code runs at set moments. On Windows, hooks normally run through Git Bash. When Git Bash isn't found and the hook doesn't set "shell" to "powershell", the hook is now described as blocked for that reason. Only an exit code of 0 or 2 counts as such a hook's verdict, unless it sets "shell" to "powershell".

The separate case of your own hooks being blocked under CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG keeps its own message. Before, any hook that wasn't required got that message.

Why

On Windows without Git Bash, the old message could wrongly point at personal-config restrictions. The new one names the real cause, and setting "shell" to "powershell" on the hook is the way around it.

Read from
Names in the bundleshell
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Manage multiple agents with agent view touched a line naming shell after this was published. Backgrounding starts a fresh process that resumes from the saved conversation, and in-flight background work moves to it. Running background shell commands, backgrounded subagents, dynamic workflows, scheduled tasks you created with [`/loo… agent-view see the edit
Confirmed since Anthropic's documentation has since written up shell, on Chat in Claude Desktop on 3P. * **Run code on the host.** There is no shell access. With advanced file analysis off (the default), the sandbox VM is never started for Chat; with it on, code runs only inside the sandbox described under [Advanced file analysis](#advanced… third-party/claude-desktop/chat see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up shell, on Chat in Claude Desktop on 3P.

See this entry in the whole of v2.1.299 →

Feedback