{"version":"2.1.282","anchor":"remote-managed-settings-trigger-a-reapply-on-success-or-ruli","canonical_anchor":"remote-managed-settings-trigger-a-reapply-on-success-or-ruli","heading":"Managed settings can be reapplied after fetching them from the server","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/remote-managed-settings-trigger-a-reapply-on-success-or-ruli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Managed settings can be reapplied after fetching them from the server\n\nAfter fetching managed settings, Claude Code can now reapply them, on success or on a failure that carries rulings\n\n**Unclear.** The condition that triggers the reapply, and what exactly gets reapplied, are not stated.\n\n**What**\n\nManaged settings are settings an organization's administrator sets centrally. After Claude Code fetches them from the server, it now reapplies settings in some cases, where before it only recorded how the fetch went:\n\n- after a successful fetch, when a certain condition holds\n\n- after a failed fetch, when that condition holds or the failure includes rulings\n\n**Why**\n\nIn practice, changes to managed settings may take effect sooner.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}