Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.290 ·

Safer handling of unreadable settings files when setting up a home folder

When writing starting settings into a home folder, Claude Code now handles settings files it cannot read whole instead of writing over them blindly

You'll notice Improvements
JSON All of v2.1.290
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection of the release

Unclear It is not clear what starts home seeding or whether it is switched on.

What

Claude Code can seed a home folder, meaning it writes starting settings into it. That step now handles awkward existing settings files more carefully:

  • A settings file that is not an ordinary file, or that cannot be read, is reported as unreadable.
  • When some settings were refused, the new settings are rebuilt against the file already there rather than written as first prepared.
  • A file that cannot be read in full is not replaced, and Claude Code logs that it could not be replaced.
  • When an existing settings file that came from elsewhere is overwritten, the record of the file's contents after the write is left empty.

Before, the step only reported when removing a file failed, and wrote the settings as first prepared.

Why

This makes writing settings safer when your existing settings file is unusual or was not made by Claude Code.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what starts home seeding or whether it is switched on.

See this entry in the whole of v2.1.290 →

Feedback