{"version":"2.1.304","anchor":"remote-managed-settings-records-isansweredempty","canonical_anchor":"remote-managed-settings-records-isansweredempty","heading":"Claude Code notes when remote managed settings come back empty","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/remote-managed-settings-records-isansweredempty","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Claude Code notes when remote managed settings come back empty\n\nWhen a fetch of remote managed settings succeeds but returns no settings, Claude Code now records that the answer was empty\n\n**What**\n\nManaged settings are settings an organization's administrator delivers to Claude Code from a server. When Claude Code fetches them successfully and the server returns an empty set of settings, Claude Code now records that the server answered with nothing, instead of treating it like any other successful fetch.\n\n**Why**\n\nAn empty answer is now told apart from an answer that contains settings. Claude Code uses that difference to decide when to skip a cleanup step.\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"}