Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.239 Home All releases ←olderv2.1.238 v2.1.240newer→
Claude Code v2.1.239

Hooks owned by a connected device now obey hook policy

You'll notice
Useful3 Signal3
Hooks

Hooks owned by a paired device are skipped when managed-hooks-only policy applies.

What

Hook definitions that carry a device-owner marker are skipped whenever the managed-hooks-only policy is in force, or when hooks are disabled for the settings file they came from. The skip applies both when hooks run and when Claude Code checks whether any hooks exist at all.

Details
  • Same treatment on both paths, so a suppressed device hook does not make the session look hook-enabled.
  • Device hooks travel over the connection to the device as tagged callback requests, each with an id, a deadline and a cancel handle.
  • Malformed and failed replies are counted, and a warning is logged once more than 512 such requests are outstanding at once.
Evidence

deviceOwner

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.239 →