{"version":"2.1.295","anchor":"home-settings-seed-replaced-field-dropped","canonical_anchor":"home-settings-seed-replaced-field-dropped","heading":"Cloud home-settings seeding no longer reports whether settings were replaced","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/home-settings-seed-replaced-field-dropped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Cloud home-settings seeding no longer reports whether settings were replaced\n\nThe result of seeding home settings from the cloud no longer reports whether existing settings were replaced\n\n**What**\n\nWhen Claude Code seeds your home settings from the cloud, the result no longer says whether existing settings were replaced. The decision to clear the recorded checksum of the settings file (a fingerprint used to tell whether the file has changed) now depends on more conditions than before.\n\n**Why**\n\nThis is a change to how cloud settings are passed through behind the scenes. It does not add anything you can set or see.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}