{"version":"2.1.299","anchor":"remote-settings-cache-write","canonical_anchor":"remote-settings-cache-write","heading":"Saving of remote managed settings changes when the server has none","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/remote-settings-cache-write","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Saving of remote managed settings changes when the server has none\n\nWhen the server has no managed settings, Claude Code now saves any settings it already has instead of always saving an empty set\n\n**Unclear.** What the extra step after saving does, and so the overall effect, is not stated.\n\n**What**\n\nRemote managed settings are settings your organization sends to Claude Code from a server, which Claude Code keeps a saved copy of. When the server answers that there are no settings, Claude Code used to save an empty set. It now saves the settings it is holding at that point, falling back to an empty set only when there are none. An extra step also now runs after the settings are saved.\n\n**Why**\n\nThis changes what ends up in Claude Code's saved copy of your organization's settings when the server reports none.\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"}