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.238 Home All releases olderv2.1.237 v2.1.239newer
Claude Code v2.1.238

Sensitive-file detection now sees through Unicode look-alikes

You'll notice
Useful3 Signal3
Cloud Sync

Sensitive filenames disguised with Unicode look-alike letters are now caught.

What

A file named with a dotless i, a long s, a Kelvin sign or an ff/fi ligature no longer slips past the checks that classify a path as sensitive. Paths are normalised through a NFKD plus case round trip with invisible characters stripped, and tracked sensitive files get their own verdict, sensitive_tracked. The sync worker's filename-safety checks reject these look-alikes outright.

Details
  • The set of confusables differs by platform: Windows and WSL use one list, macOS adds ß.
  • Runs on every classification, with no flag.
Evidence

sensitive_tracked

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