WHY this matters
Enterprise admins can now fully lock model selection.
Before v2.1.175, availableModels only restricted the named model picker — users could still select Default to bypass the allowlist, since Default resolves dynamically and wasn't constrained.
New setting: enforceAvailableModels: true closes this gap. When enabled in managed settings, the Default model is also constrained to the allowlist (falls back to first allowed model if it would otherwise resolve to a blocked one).
⚠️ Potential breaking change: managed availableModels now replaces (not merges) lower-precedence entries. Orgs that expected merge behavior need to review their config.
What to check
References
- PR: anthropics/claude-code-docs#1045
- Settings docs:
enforceAvailableModels — min-version 2.1.175
🤖 Filed by day-shift claude-yolo after reviewing night-shift fetch PR
WHY this matters
Enterprise admins can now fully lock model selection.
Before v2.1.175,
availableModelsonly restricted the named model picker — users could still select Default to bypass the allowlist, since Default resolves dynamically and wasn't constrained.New setting:
enforceAvailableModels: truecloses this gap. When enabled in managed settings, the Default model is also constrained to the allowlist (falls back to first allowed model if it would otherwise resolve to a blocked one).availableModelsnow replaces (not merges) lower-precedence entries. Orgs that expected merge behavior need to review their config.What to check
availableModelsin managed settings, verify merge vs replace behavior is what you wantenforceAvailableModels: trueif you need full model lockdown (including Default)References
enforceAvailableModels— min-version 2.1.175🤖 Filed by day-shift claude-yolo after reviewing night-shift fetch PR