{"version":"2.1.163","anchor":"organization-version-enforcement-requiredminimumversion-requ","canonical_anchor":"organization-version-enforcement-requiredminimumversion-requ","heading":"Organization Version Enforcement (requiredMinimumVersion \/ requiredMaximumVersion)","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.163\/e\/organization-version-enforcement-requiredminimumversion-requ","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.163","markdown":"### Organization Version Enforcement (requiredMinimumVersion \/ requiredMaximumVersion)\n\n**What**\n\nAdministrators can now enforce a minimum and\/or maximum Claude Code version through managed policy settings. If the running version is outside the allowed range, Claude Code exits at startup with instructions on how to update or downgrade.\n\n**Details**\n\n- `requiredMinimumVersion`: If the running version is older than this value, Claude Code exits with a message to update using the organization's approved method.\n- `requiredMaximumVersion`: If the running version is newer than this value, Claude Code exits with a message to install an approved version (`claude install <version>` may also work).\n- Both settings are only enforced from managed\/policy settings (`managed-settings.json` \/ MDM). They have no effect in user or project settings.\n- Exempt commands: `update`, `install`, and `doctor` bypass the version check so users can fix the problem.\n- Invalid semver values are logged as errors and ignored rather than blocking startup.\n\n**Evidence**\n\nVersion check at startup (search for `\"is older than the minimum version required by your organization\"` and `\"is newer than the maximum version allowed by your organization\"`)"}