Claude docs changes for June 14th, 2026 [diff]
Executive Summary
- New
enforceAvailableModelssetting (v2.1.175+) allows administrators to constrain the Default model option to theavailableModelsallowlist, closing the bypass where users could always pick "Default" regardless of model restrictions - Changed merge behavior: when
availableModelsis set in managed or policy settings, it now replaces (not merges with) lower-precedence entries, enabling strict enterprise allowlists - Blocked
--modelflag now shows a warning naming both the requested and substituted models, instead of silently ignoring the flag
New Claude Code versions
None today.
Claude Code changes
Changed documents
admin-setup [Source]
- Clarified that after configuring managed settings, developers should check the Status tab's
Setting sourcesline in/statusto verify enterprise managed settings are active. [line 97] [Source]
claude-platform-on-aws [Source]
- Removed the marketing banner ("Deploying Claude Code across your organization?") with links to pricing and sales contact from the top of the page.
model-config [Source]
- A blocked
--modelflag orANTHROPIC_MODELvalue now shows a warning at startup naming both the requested and substituted models, instead of being silently ignored. [line 100] [Source] - New
enforceAvailableModelssetting: whentruealongside a non-emptyavailableModelslist in managed or policy settings, the Default model option is also constrained to the allowlist rather than resolving to the tier default. Requires v2.1.175+. [lines 110-112] [Source] - Updated guidance for fully controlling the model experience now includes
enforceAvailableModelsas a required component alongsideavailableModels,model, and theANTHROPIC_DEFAULT_*env vars. [lines 115-145] [Source] - Changed merge behavior: when
availableModelsis set in managed or policy settings, the managed/policy value now replaces the merged result from user/project/local settings entirely. Prior to v2.1.175, the managed list was merged with lower-precedence entries. [lines 148-150] [Source] - Added behavior note for
opusplan: whenavailableModelsexcludes Opus,opusplanstays on Sonnet in plan mode instead of switching; similarly if Sonnet is excluded, the implicit Haiku-to-Sonnet plan-mode upgrade is skipped. [line 174] [Source]
settings [Source]
- Added
availableModelsandenforceAvailableModelsto the security-enforcement fields table: invalidavailableModelsentries fall back to an empty allowlist (only Default available), and invalidenforceAvailableModelsis treated astrue. Both apply in v2.1.175+. [lines 155-156] [Source] - Updated
availableModelssetting description to remove the previous note that it "does not affect the Default option" (now controlled viaenforceAvailableModels). [line 194] [Source] - New
enforceAvailableModelssetting entry added to the settings reference table. Requires v2.1.175+. [line 219] [Source] - Clarified array merge behavior:
availableModelsis now documented as a second exception (alongsidefallbackModel) where a managed/policy value replaces lower-precedence entries instead of merging. [line 547] [Source] - Improved
/statusdocumentation: restructured into a bulleted list explaining what each layer's presence or absence means, with clearer separation between the Status tab and Config tab purposes. [lines 554-561] [Source]
API changes
Changed documents
No significant changes today. (Only obfuscated email URL updates in adaptive-thinking, extended-thinking, and files.)