{"version":"2.1.290","anchor":"home-seed-settings-replacement-handles-unreadable-and-partia","canonical_anchor":"home-seed-settings-replacement-handles-unreadable-and-partia","heading":"Safer handling of unreadable settings files when setting up a home folder","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/home-seed-settings-replacement-handles-unreadable-and-partia","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Safer handling of unreadable settings files when setting up a home folder\n\nWhen writing starting settings into a home folder, Claude Code now handles settings files it cannot read whole instead of writing over them blindly\n\n**Unclear.** It is not clear what starts home seeding or whether it is switched on.\n\n**What**\n\nClaude Code can seed a home folder, meaning it writes starting settings into it. That step now handles awkward existing settings files more carefully:\n\n- A settings file that is not an ordinary file, or that cannot be read, is reported as unreadable.\n\n- When some settings were refused, the new settings are rebuilt against the file already there rather than written as first prepared.\n\n- A file that cannot be read in full is not replaced, and Claude Code logs that it could not be replaced.\n\n- When an existing settings file that came from elsewhere is overwritten, the record of the file's contents after the write is left empty.\n\nBefore, the step only reported when removing a file failed, and wrote the settings as first prepared.\n\n**Why**\n\nThis makes writing settings safer when your existing settings file is unusual or was not made by Claude Code.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}