Source Intelligence

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.191 Home All releases olderv2.1.190 v2.1.193newer
Claude Code v2.1.191

Config Corruption Auto-Repair (GH #3117)

What changed: When ~/.claude.json is found corrupted during a locked save operation, Claude Code now automatically repairs it from the in-memory cached config rather than leaving the file in a corrupted state.

Previously, hitting a parse error on the re-read inside saveConfigWithLock would block the write and leave the file unchanged. Now:

  1. If a parse error is detected during the locked re-read, the cached in-memory config is used as the recovery source.
  2. The repair is logged and reported to telemetry (tengu_config_auto_repaired).
  3. A timestamped .corrupted. backup is still saved so the original can be inspected.
  4. The error message changed from "Config file corrupted, resetting to defaults" to "Config file corrupted" and separately "Could not back up corrupted config" for backup failures — more accurate since defaults are no longer the only fallback.
Evidence

Auto-repair path in saveConfigWithLock (search for "saveConfigWithLock: re-read hit a parse error; auto-repairing from cached config under lock. See GH #3117.")

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

See this entry in the whole of v2.1.191 →