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.246 Home All releases ←olderv2.1.245 v2.1.247newer→
Claude Code v2.1.246

Clearer reason when an administrator has blocked plugin hooks

You'll notice
Useful2 Signal1
Hooks

When managed settings block plugin hooks, the message now says that explicitly.

What

When plugin hook modules are refused because managed settings only permit hooks from enterprise-managed sources, the message now says so explicitly instead of reusing a generic reason.

Details
  • Sits alongside the existing reasons for --bare and disableAllHooks.
  • Driven by the allowManagedHooksOnly and disableAllHooks settings; no other gate.
Evidence

an admin stood the guard down (safe mode / managed allowManagedHooksOnly)

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