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.301 ·

Simpler check for which hooks get the organization's shell prefix

Whether a hook counts as your organization's, and so gets CLAUDE_CODE_SHELL_PREFIX, no longer depends on the hook's type or its plugin

Under the hood Internal Changes
JSON All of v2.1.301
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
HooksArea: what it touches
Internal ChangesKind: in v2.1.301,
Internal ChangesSection of the release

Unclear It is not clear what the new check tests, so it is not known which hooks now count as the organization's.

What

Hooks are commands Claude Code runs automatically at set points. Claude Code uses a simpler check to decide whether a hook belongs to your organization. Hooks that pass get the organization's shell prefix from CLAUDE_CODE_SHELL_PREFIX, a command placed in front of every hook command, along with the organization's environment variables.

The check no longer looks at the kind of hook or at the plugin or skill it came from. Before, status line and file suggestion hooks were always left out. Claude Code can also now report when an organization hook starts without the environment variables a person's plugin set.

Why

This can change which hooks run with your organization's shell prefix and environment.

Read from
Names in the bundleCLAUDE_CODE_SHELL_PREFIX
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 doubtIt is not clear what the new check tests, so it is not known which hooks now count as the organization's.

See this entry in the whole of v2.1.301 →

Feedback