Source Intelligence

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.232 Home All releases olderv2.1.231 v2.1.233newer
Claude Code v2.1.232

Managed policy CLI documents are checked for alias collisions

You'll notice
Useful2 Signal2
Managed Settings

Gateway configs now fail validation if a setting appears under both an alias and its canonical name.

What

Each managed.policies[].cli document in a gateway config is scanned for a setting written under both an alias and its canonical name. Every collision is a validation error naming both spellings and telling the operator to keep the canonical one.

Details
  • Previously the alias map was applied with no complaint when both spellings were present, so which one won was not obvious.
Evidence

which are the same setting

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