
Claude Code v2.1.173 to v2.1.175 Major Updates
This page has been translated by machine translation. View original
This is Ishikawa from the Cloud Business Division. Here is a summary of the Claude Code updates for v2.1.173 ~ v2.1.175 (2026-06-11 ~ 2026-06-12).
Update Summary
This covers 3 versions (v2.1.173 ~ v2.1.175, 2026-06-11 ~ 2026-06-12) with a total of 16 changes (3 new features · 13 fixes). Notable among the changes are model management and governance-related updates, including the addition of the enforceAvailableModels admin setting that enforces the availableModels allowlist on Default models as well, along with numerous stability-related fixes for the /model picker, background sessions, Bedrock GovCloud, and more.
Highlighted Updates
- New Feature: Usage attribution has been added to the VS Code extension's account and usage dialog (
/usage). You can now view breakdowns by cache miss, long context, sub-agents, and by Skills/Agents/Plugins/MCP for the past 24 hours or 7 days (v2.1.174) - Bug Fix: Fixed an issue where background sessions were inheriting
ANTHROPIC_*provider environment variables (gateway URL, custom headers,/modelaliases) from separate sessions that launched the background daemon (v2.1.174) - Security: The
enforceAvailableModelsadmin setting has been added. TheavailableModelsallowlist is now enforced on Default models as well, and users can no longer expand the managed list through user settings or project settings (v2.1.175)
Target Versions and Timeline
| Version | Release Date |
|---|---|
| v2.1.173 | 2026-06-11 |
| v2.1.174 | 2026-06-11 |
| v2.1.175 | 2026-06-12 |
Update Details
New Features
Addition of enforceAvailableModels Admin Setting (v2.1.175): A new enforceAvailableModels managed setting has been added for organization administrators. When enabled, the following 2 behaviors are enforced:
- The
availableModelsallowlist is applied to Default models as well. If Default resolves to a model that is not permitted, it falls back to the first model in the allowlist. - Users can no longer expand the managed
availableModelslist through user settings or project settings.
Previously, the availableModels allowlist restrictions did not apply to the resolution target of Default models, but this setting now allows the allowlist to be applied including Default. This is a useful setting for organizations that want to govern which models are available for use.
VS Code Extension: Added Usage Attribution to /usage Dialog (v2.1.174): Usage attribution has been added to the VS Code extension's account and usage dialog (/usage). In addition to cache miss, long context, and sub-agent usage, you can now view breakdowns by Skills/Agents/Plugins/MCP for the past 24 hours or 7 days.
This makes it easier to understand how much usage each skill or agent is consuming, which is helpful for monitoring usage status.
Setting to Disable Mouse Wheel Scroll Acceleration (v2.1.174): A wheelScrollAccelerationEnabled setting has been added to disable mouse wheel scroll acceleration in fullscreen mode.
Fixes
Here is a selection of the major fixes related to stability and usability.
- Fixed environment variable inheritance in background sessions: Fixed an issue where background sessions were inheriting
ANTHROPIC_*provider environment variables (gateway URL, custom headers,/modelaliases) from separate sessions originating from the shell that launched the background daemon (v2.1.174) - Fixed
[1m]suffix normalization for Fable 5 model names: Fixed an issue where Fable 5 model names with the[1m]suffix were not being normalized. Since Fable 5 includes 1M context by default, the suffix is now automatically removed (v2.1.173) - Fixed Default resolution target not appearing in
/modelpicker: Fixed an issue where the model family that Default resolves to was not displayed in the picker. For Max/Team Premium/Enterprise plans it is Opus, for Pro/Team plans it is Sonnet, and for pay-as-you-go API accounts it is Opus, each displayed as a separate row (v2.1.174) - Fixed 400 errors in Bedrock GovCloud regions: Fixed an issue where the inference profile prefix was incorrectly derived as
global(should beus-gov) in GovCloud regions (us-gov-*), causing 400 errors with the derived model ID (v2.1.174) - Fixed 1~2 second delay on exit: Fixed an issue on macOS and Linux where exiting Claude Code immediately after interrupting or force-killing a shell command caused a 1~2 second delay (v2.1.174)
- Fixed skill hot-reload re-transmission: Fixed an issue where a change to one skill caused the entire skills list to be re-sent, so that now only the changed skill is re-notified (v2.1.174)
- Fixed authentication errors in background workers: Fixed an issue where pre-warmed background workers failed with a "Could not resolve authentication method" error when assigned after being idle (v2.1.174)
- In addition, numerous minor bug fixes have been made, including Windows sandbox launch warnings,
/modelpicker label display, billing banner false positives, git commit co-author notation,/advisordialog model pre-selection, and Workflow tool attribution headers.
Breaking Changes · Deprecations
There are no entries in the CHANGELOG for the target versions (v2.1.173 ~ v2.1.175) that correspond to breaking changes or deprecations.
Note that for organizations that enable enforceAvailableModels (v2.1.175), users will no longer be able to expand availableModels through user settings or project settings, so administrators are advised to review the scope of impact before applying the setting.
Closing
v2.1.173 ~ v2.1.175 was an update centered on strengthening model governance with enforceAvailableModels and stability fixes around the /model picker and background sessions. If you use VS Code, be sure to also check the usage attribution in /usage. If any of the changes catch your interest, try updating and checking them out.
References
