Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.277 ·

FileHistory backup restore returns structured outcomes instead of throwing

File-history backup restore now reports structured failure reasons instead of crashing

Under the hood Internal Changes
JSON All of v2.1.277
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.277,
Internal ChangesSection of the release
What

When Claude Code restores a backup file during a rewind or checkpoint, the restore step now returns a structured result describing what happened, instead of throwing an error. The result says whether the restore failed, was already present, or was migrated, and, on failure, at which stage it failed: a bad backup source, or a problem at the source, link, copy, or rename step.

Rename failures now log a clearer explanation of the likely cause, such as a scanner or sync tool still holding the newly written file, or a mount that allows creating files but not renaming them.

Why

This makes backup-restore failures easier to diagnose instead of surfacing as a generic crash, and it explains real-world causes like antivirus scanners or cloud-sync tools interfering with file operations.

See this entry in the whole of v2.1.277 →

Feedback