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.234 Home All releases olderv2.1.233 v2.1.235newer
Claude Code v2.1.234

Claude data-export import validates what it reads

You'll notice
Useful2 Signal1
Elsewhere

Importing a Claude data export now gives a clear error on a corrupt file instead of failing deep inside.

What

Importing a Claude data export now checks the file shapes up front, so a corrupt or partial export gives a clear error instead of failing somewhere deep in the import.

Details
  • Input that is not JSON, and a conversations.json that will not parse, each raise their own explicit error.
  • A missing manifest is rebuilt from the parsed conversations and projects rather than guessed from loosely typed fields.
  • Project directory names are checked against a name pattern and a length cap; ones that fail are skipped rather than aborting the import.
  • Directory entries inside the zip are excluded from the extracted file map.
  • Array contents are parsed leniently: a single malformed element is dropped instead of failing the whole list.
Evidence

export conversations.json is not valid JSON

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.234 →