Claude Code 2.1.163 adds managed version bounds for stricter rollout control
Claude Code 2.1.163 adds managed settings that can block unsupported CLI versions at startup, giving teams a clearer way to enforce approved upgrade windows.
Claude Code 2.1.163 adds requiredMinimumVersion and requiredMaximumVersion managed settings for teams that need tighter control over which CLI builds can run. The official changelog says Claude Code now refuses to start when its version falls outside the approved range and points the user to an approved version. That makes this release useful for organizations rolling out agentic coding tools under IT, compliance, or endpoint-security constraints.
Key takeaways
- Claude Code 2.1.163 adds managed version bounds through
requiredMinimumVersionandrequiredMaximumVersion. - The official changelog says the CLI blocks startup when the installed version is outside that managed range.
- The settings documentation already describes managed settings as the highest-priority scope, above user, project, and local settings.
- Havoptic independently lists Claude Code 2.1.163 on June 4, 2026 and summarizes the same managed-setting change.
- This is mainly an admin and rollout-control update, not a new coding model or prompt feature.
Practical LinkLoot angle
For teams using Claude Code across many workstations, version drift is a real operations problem. A bug fix may require a minimum version, while a regression may require a temporary maximum version until the next approved build lands. Managed version bounds turn that decision into policy instead of Slack reminders and manual audits.
| Tool or source | Best use | Limitation | Source |
|---|---|---|---|
| Claude Code changelog | Confirm what changed in 2.1.163 | Long page; extract only the relevant release note | Official changelog |
| Claude Code settings docs | Understand managed-setting priority and deployment scopes | The settings page is broader than this single release | Official docs |
| Havoptic | Cross-check release date and summary across AI coding tools | Third-party tracker, not the authority for product behavior | Independent tracker |
This matters most for organizations that already run managed settings through server policy, MDM, registry, or file-based deployment. A practical rollout path is to set a minimum version after smoke tests pass, keep a maximum version available as a brake during risky release windows, and document who owns policy changes.
What to verify before you act
Check the exact field names and supported release before deploying a policy. The changelog names requiredMinimumVersion and requiredMaximumVersion, while the broader settings page also documents minimumVersion; do not assume older settings names cover the same behavior. Test on one managed device first, because a strict version ceiling can block developers from starting Claude Code if auto-update already moved them beyond the approved range.
Also verify how your organization delivers managed settings. The settings docs describe server-managed settings, macOS managed preferences, Windows registry policy, and file-based managed settings; the right path depends on your fleet tooling. If you use third-party providers such as Bedrock, Vertex, or Foundry, test login and startup behavior separately from first-party Claude.ai accounts.
Source check
The official Claude Code changelog confirms the new managed version bounds and startup-blocking behavior in version 2.1.163. The settings documentation confirms the managed-settings scope and explains that managed settings take priority over command-line, local, project, and user settings. Havoptic independently lists Claude Code 2.1.163 on June 4, 2026 and repeats the required minimum and maximum version summary.
The release adds managed version bounds so organizations can block unsupported Claude Code versions at startup.
For more agent-tool rollout notes, see LinkLoot's AI agent tools guide.