{"version":"2.1.287","anchor":"settings-change-detection-compares-tiers-and-normalized-sett","canonical_anchor":"settings-change-detection-compares-tiers-and-normalized-sett","heading":"Settings reloads now compare cleaned-up settings rather than raw ones","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/settings-change-detection-compares-tiers-and-normalized-sett","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Settings reloads now compare cleaned-up settings rather than raw ones\n\nWhen checking whether settings changed, Claude Code now compares normalized settings and which levels differ, instead of raw file contents\n\n**Unclear.** The exact rules for which project-level settings are skipped are not clear.\n\n**What**\n\nClaude Code re-reads its settings during a session and reloads them when something changed. The check for whether anything changed now works differently:\n\n- It compares normalized versions of the settings (put into a standard form first) instead of the raw values.\n\n- It checks which settings levels actually differ.\n\n- It skips some project-level settings that are not locked in place.\n\nBefore, it compared the raw settings, any errors and older-format settings against the last copy it had.\n\n**Why**\n\nSettings may now reload in different situations than before, most likely fewer times when nothing meaningful changed.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}