{"version":"1.0.120","anchor":"file-history-persistence-across-sessions","canonical_anchor":"file-history-persistence-across-sessions","heading":"File History Persistence Across Sessions","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/1.0.120\/e\/file-history-persistence-across-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/1.0.120","markdown":"### File History Persistence Across Sessions\n\n**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.\n\n**How it works:**\n\n- During execution, file history snapshots are automatically saved to the session log file\n- 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\n- The file history UI state is fully restored, showing which files were tracked and their modification history\n\n**Details:**\n\n- Session log entries now include a new type: `\"file-history-snapshot\"` at `insertFileHistorySnapshot()` at line 438449\n- New function `a_1()` at line 384641 handles cross-session backup file migration\n- New function `t11()` at line 384611 generates session-specific backup file paths\n- New function `n_1()` at line 384636 processes snapshots to extract tracked files for UI restoration\n- Session log class now includes `fileHistorySnapshots` Map at line 438396\n- Backup files are stored per session in `~\/.config\/claude\/file-history\/<sessionId>\/`\n\n**Evidence**\n\n`insertFileHistorySnapshot()` at line 438449, `a_1()` at line 384641, `t11()` at line 384611, `n_1()` at line 384636, `fileHistorySnapshots` field at line 438396"}