New managed setting `enforceAvailableModels` tightens model management!
New Features in Claude Code v2.1.175
Original: v2.1.175
Importance: 新しい管理設定が追加され、モデル管理に影響を与えるため。
Summary
The new version v2.1.175 of Claude Code has been released. This update adds the `enforceAvailableModels` managed setting, which impacts the Default model based on the `availableModels` allowlist. If a Default resolves to a disallowed model, it now falls back to the first allowed model. Additionally, user or project settings can no longer widen a managed `availableModels` list. This change is particularly significant for users who want stricter management of models.
Key Points
- `enforceAvailableModels` setting added
- Impacts Default model selection
- User settings can no longer widen
- Stricter model management
- Important for specific users
View developer notes (APIs, breaking changes, migration)
This version introduces a new managed setting called `enforceAvailableModels`. When enabled, this setting constrains the Default model based on the `availableModels` allowlist. If the Default resolves to a disallowed model, it now falls back to the first allowed model. Furthermore, user or project settings can no longer widen a managed `availableModels` list. Developers need to consider this setting when selecting models and ensure proper model management in operations.
Source: https://github.com/anthropics/claude-code/releases/tag/v2.1.175
Outlet: Claude Code Releases
This article is an AI-generated summary (OpenAI GPT-4o-mini) of publicly available information from Anthropic, OpenAI, Google, Meta, Mistral, DeepSeek, Sakana, and other vendors. The original source URL is always provided in accordance with fair-use citation requirements. Summaries are AI-generated and may contain mistranslations or misinterpretations. Always verify details with the original source.