Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.238 Home All releases ←olderv2.1.237 v2.1.239newer→
Claude Code v2.1.238

A failed backup no longer aborts corrupt-config recovery

You'll notice
Useful3 Signal2
Configuration

Recovery from a corrupt ~/.claude.json now continues even if backing up the broken file fails.

What

When ~/.claude.json is corrupt, a failure while backing up the broken file is now logged and recovery continues, instead of stopping there.

Details
  • The message includes the underlying error text.
  • The watcher behind the config was also tightened: it now drops its freshness subscription if the storage backend changed underneath it, and ignores an update event that matches the version this process just loaded.
  • Its fallback log line now reads "using the fs.watchFile poll" rather than "staying on" it.
Evidence

Could not back up corrupted config (

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.238 →