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.236 Home All releases ←olderv2.1.235 v2.1.237newer→
Claude Code v2.1.236

Reporting a corrupted config can no longer crash Claude Code

You'll notice
Useful3 Signal1
Configuration

A corrupted config file now gets reported and backed up without crashing Claude Code.

What

The path that handles a corrupted Claude config file (telemetry for the parse error, backing up the bad file, and the "Claude configuration file at ... is corrupted" message) is now wrapped so a failure inside it is logged instead of thrown.

Details
  • Previously an error while reporting the corruption escaped and could take down the surrounding operation.
  • Failures now log at error level and reporting continues.
Evidence

Could not report the corrupt 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.236 →