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

Hooks wait for your organisation's managed settings before running

Startup hooks and plugin hooks now wait for organisation managed settings, and are skipped with a warning if those never arrive

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

Unclear Whether this waiting applies to every setup or only to some is not stated.

What

Hooks are your own commands that Claude Code runs at set moments, such as when a session starts. Managed settings are settings your organisation's administrator sets for everyone. Claude Code now holds back these until the organisation's managed settings have answered:

  • hooks that run at startup
  • command sources
  • hooks that come from plugins

If the managed settings never answer, Claude Code shows a warning and does not run the hooks. A failure because the organisation did not answer is treated the same as a policy block.

Why

If your organisation manages Claude Code, hooks may start a little later, or not run at all, when its settings cannot be reached at startup. This stops hooks from running before the organisation's rules are known.

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 doubtWhether this waiting applies to every setup or only to some is not stated.

See this entry in the whole of v2.1.300 →

Feedback