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.251 Home All releases ←olderv2.1.250
Claude Code v2.1.251

Blocked commands can now say which org policy blocked them

Under the hood
Useful2 Signal3
Policy

Org-disabled built-in commands now carry a policy name and label for explaining why they're gone.

What

Built-in commands that an organization can switch off, including heap dumps, team onboarding, and the design consent and revoke commands, now carry the policy name and a readable label such as "Heap dumps" next to their existing enabled check. This is the plumbing for telling you why a command is unavailable rather than just hiding it.

Details
  • Each entry pairs a policy key like allow_heap_dump or allow_team_onboarding with a display label and a verb, so a message can be assembled grammatically.
  • The generic builder used for locally defined commands carries the same fields.
  • Whether a command runs is still decided by the existing policy checks; this only adds the wording.
Evidence

featureLabel: "Heap dumps"

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