Claude Code v2.1.223 ·
Managed-settings tier merge no longer falls through for two keys
Two admin-managed settings now come only from the top policy tier, so lower tiers can't sneak values in.
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Managed SettingsArea: what it touches
Bug FixesKind: in v2.1.223,
Bug FixesSection of the release
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.
See this entry in the whole of v2.1.223 →
