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.223 Home All releases ←olderv2.1.222 v2.1.224newer→
Claude Code v2.1.223

Managed-settings tier merge no longer falls through for two keys

You'll notice
Useful3 Signal0
Managed Settings

Two admin-managed settings now come only from the top policy tier, so lower tiers can't sneak values in.

forceLoginOrgUUIDallowedMcpServers
What

Two admin-controlled keys are now read only from the highest-precedence tier, so a lower tier can no longer supply them when the top tier omits them.

Details
  • forceLoginOrgUUID and allowedMcpServers now follow the rule availableModels already used, reading from tier index 0 only
  • previously each was taken from the first tier that happened to define it
  • the merge result gained a present field with remote, mdm and file booleans reporting which tiers were found
Evidence

forceLoginOrgUUID: u[0]?.forceLoginOrgUUID

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