{"version":"2.1.281","anchor":"managed-settings-load-failure-has-a-second-wording-for-one-a","canonical_anchor":"managed-settings-load-failure-has-a-second-wording-for-one-a","heading":"Managed-settings load failure has a second wording for one auth context","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/managed-settings-load-failure-has-a-second-wording-for-one-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Managed-settings load failure has a second wording for one auth context\n\nThe error for managed settings that fail to load now drops the `claude auth login` advice in one sign-in situation\n\n**Unclear.** The finding does not say which sign-in situation produces the shorter wording.\n\n**What**\n\nSome organisations require remote managed settings, which are settings the organisation delivers from a server. When those cannot be loaded, Claude Code shows \"Your organization requires remote managed settings to load, but they could not be loaded.\" followed by advice. The advice now comes in two versions:\n\n- In one situation it ends with \"You can check your network connection or contact your admin.\"\n\n- Otherwise it still reads \"Run `claude auth login` to re-authenticate, check your network connection, or contact your administrator.\"\n\n**Why**\n\nIn the situation that gets the shorter wording, signing in again is no longer offered as a fix, so check your network or ask your admin."}