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.239 Home All releases ←olderv2.1.238 v2.1.240newer→
Claude Code v2.1.239

A file whose attributes cannot be read is now a named sync outcome

Under the hood
Useful1 Signal1
File Sync

Files whose attributes cannot be read now get a proper named sync outcome instead of an unclassified error.

What

attributes_unreadable joins the existing sync failure reasons such as lock contention and unreadable peer journals, in the retry decision, the human-readable formatter and the terminal-state classifier, so it is no longer an unclassified error.

Evidence

attributes_unreadable

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