{"version":"2.1.281","anchor":"startup-reorders-the-remote-managed-settings-checks","canonical_anchor":"startup-reorders-the-remote-managed-settings-checks","heading":"Startup reorders the remote managed-settings checks","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/startup-reorders-the-remote-managed-settings-checks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Startup reorders the remote managed-settings checks\n\nStartup now checks for required remote managed settings earlier and exits if they cannot be loaded, except for `auth`\n\n**What**\n\nSome organizations require Claude Code to load settings from a server before it can run. At startup, Claude Code now checks this sooner. If the required settings cannot be loaded, it stops and reports `remote_settings_required_unavailable`, or `force_refresh_failed`. When the request goes through a gateway and is rejected, that message now goes through the same shared exit step. The `auth` subcommand skips this check.\n\n**Why**\n\nIf your organization requires remote settings and they are unavailable, Claude Code stops early with a named reason. You can still run `auth` to sort out signing in.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}