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.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

Plain-language reasons why a local hook is not offered to a cloud session

You'll notice
Useful3 Signal3
Hooks

Local hooks held back from a cloud session now tell you in plain words why.

What

When your local hooks are forwarded to a cloud session, each one that is held back now says why in prose rather than being quietly dropped.

Details
  • Reasons include: after-edit hooks stay on this machine; only command and http hook types can be forwarded; a matcher written as a pattern rather than a plain list is refused; a script living somewhere the cloud session can write on this machine is held unless pinned; duplicates and registrations past the cap are dropped; an entry marked cloud: "skip" is skipped.
  • Standing states get their own wording too: paused, declined, disabled, unsupported, invalid and stale registrations.
Evidence

only command and http hooks can run for a cloud session

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.242 →