{"version":"2.1.319","anchor":"file-history-snapshots-can-use-the-forked-from-session-id","canonical_anchor":"file-history-snapshots-can-use-the-forked-from-session-id","heading":"Restoring file edits in a forked session looks in the original session","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/file-history-snapshots-can-use-the-forked-from-session-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Restoring file edits in a forked session looks in the original session\n\nWhen you restore earlier file versions in a forked session, Claude Code now looks up the saved copies under the session it was forked from\n\n**What**\n\nClaude Code saves copies of files before it edits them, so you can rewind those edits later. A forked session is a new session started as a copy of an existing one. When restoring files, Claude Code now uses the ID of the session it was forked from, if there is one, and only falls back to the ID on the latest message otherwise. The step that saves these copies also takes one more piece of information than before.\n\n**Why**\n\nThe saved copies in a forked session belong to the session it came from. Looking them up there should let rewinding file edits work in forked sessions.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}