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 v1.0.120 Home All releases olderv1.0.119 v1.0.122newer
Claude Code v1.0.120

File History Persistence Across Sessions

What: File backup snapshots are now persisted to session logs and restored when resuming previous sessions, preserving the complete file modification history across Claude Code restarts.

How it works:

  • During execution, file history snapshots are automatically saved to the session log file
  • When resuming a session (e.g., claude --resume <session-id>), backup files from the previous session are hard-linked or copied to the new session directory
  • The file history UI state is fully restored, showing which files were tracked and their modification history

Details:

  • Session log entries now include a new type: "file-history-snapshot" at insertFileHistorySnapshot() at line 438449
  • New function a_1() at line 384641 handles cross-session backup file migration
  • New function t11() at line 384611 generates session-specific backup file paths
  • New function n_1() at line 384636 processes snapshots to extract tracked files for UI restoration
  • Session log class now includes fileHistorySnapshots Map at line 438396
  • Backup files are stored per session in ~/.config/claude/file-history/<sessionId>/
Evidence

insertFileHistorySnapshot() at line 438449, a_1() at line 384641, t11() at line 384611, n_1() at line 384636, fileHistorySnapshots field at line 438396

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v1.0.120 →