Follow Discord
Sweep 30 Oct 2026 · 01:02Z Build v2.1.314 532 read Stable v2.1.308 Latest v2.1.314 Next v2.1.314 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.314 ·

Hooks sent from another machine wait until your organization's settings are read

A hook sent from another machine is not run until this machine has read its organization's managed settings

You'll notice Improvements
JSON All of v2.1.314
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.314,
ImprovementsSection of the release

Unclear It is unclear in which setups hooks are sent from another machine, so it is unclear who will see this.

What

A hook is a command that Claude Code runs automatically at set moments, for example just before it uses a tool. Managed settings are the rules an organization sets for every machine it manages.

When another machine sends a person's hook, Claude Code no longer runs it straight away. It waits until this machine has read its organization's managed settings. Until then:

  • the tool call is reported as not run, because the organization's managed settings have not been read yet
  • a PreToolUse hook, which runs before a tool call, produces a permission "ask" instead, so you are asked to approve the tool call
  • in bypass mode, where approvals are normally skipped, the hook produces a decision that holds the call back instead of running
Why

This stops a hook from slipping past the organization's policy while Claude Code is still starting up.

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 unclear in which setups hooks are sent from another machine, so it is unclear who will see this.

See this entry in the whole of v2.1.314 →

Feedback