{"version":"2.1.292","anchor":"remote-settings-fetch-gets-prefetch-oauth-refresh-latch-and","canonical_anchor":"remote-settings-fetch-gets-prefetch-oauth-refresh-latch-and","heading":"Loading organization settings at startup can reuse an earlier fetch","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/remote-settings-fetch-gets-prefetch-oauth-refresh-latch-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Loading organization settings at startup can reuse an earlier fetch\n\nOrganization-managed settings can now come from a result fetched ahead of time, with login refreshed first so only one refresh runs at a time\n\n**Unclear.** It is not clear whether the early fetch is ever made by default, so the speed-up may not apply to everyone.\n\n**What**\n\nOrganizations can manage some Claude Code settings from a server, and Claude Code downloads them when it starts. Before, this was a plain download. Now:\n\n- If a result was already fetched ahead of time for the same settings version, server address and signed-in account, Claude Code uses it.\n\n- If such an early fetch is still under way, Claude Code first refreshes your login credentials.\n\n- Credential refreshes for this are shared, so they do not run twice at once.\n\nThe usage data Claude Code sends about this download now also records whether the result was fetched ahead of time.\n\n**Why**\n\nFor people whose organization manages their settings, this should make the settings load faster at startup.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}