{"version":"2.1.323","anchor":"remote-managed-settings-no-settings-answers-and-misreads-ha","canonical_anchor":"remote-managed-settings-no-settings-answers-and-misreads-ha","heading":"Managed settings show fewer false \"settings changed\" notices","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/remote-managed-settings-no-settings-answers-and-misreads-ha","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Managed settings show fewer false \"settings changed\" notices\n\nOrganization-managed settings now handle empty server answers and inconsistent file reads better, and skip the change notice when nothing changed\n\n**What**\n\nOrganizations can send managed settings to Claude Code from a server. Claude Code now handles a few cases differently:\n\n- An answer from the server saying no settings are set up is now treated as a real, empty answer.\n\n- If the server holds no settings but two reads of a settings file disagree, one finding settings and one finding none, Claude Code applies the settings again and logs a message.\n\n- The notice that settings changed is no longer shown when nothing actually changed. Before, it showed in more cases.\n\n**Why**\n\nIf your organization manages your settings, you should see fewer misleading notices saying your settings changed.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}