Local File History in Flame IDE. Select the image to enlarge.
WHY IT HELPS
Keep the next decision in context.
Git history begins when you commit, but useful work happens between commits too. Flame's file History view brings committed revisions and local snapshots into one timeline. Inspect the selected change and recover a file version when a format, edit, or agent change removed something you wanted to keep.
See two histories in one place
Git revisions preserve committed work. Local snapshots record meaningful edit moments separately. The History view identifies the source of each entry so you know what you are reviewing.
Compare before restoring
Select an entry to inspect its content and diff. A local snapshot provides a file-level recovery path without moving the repository's branch or resetting unrelated files.
Keep the timeline useful
Snapshots capture meaningful events such as saves, before formatting, and before supported destructive Git operations. Configure snapshot retention instead of collecting every keystroke.
HOW TO USE IT
A practical starting point.
Check snapshot settings
In Settings, search for snapshots and confirm capture is enabled. Review retention settings for entry count and age. Older snapshots can be pruned according to that policy.
Open the file's History
Open the file you want to investigate and its History view. Look for the Git revision or local snapshot around the change you are trying to understand.
Inspect the selected version
Select an entry to read its details and compare the code. Distinguish a local snapshot from a committed Git revision, then decide which content to recover.
Restore and review
For an available local snapshot, choose Restore this version after reviewing it. Check the restored file, inspect its working-tree diff, and run the relevant validation before committing.
REQUIREMENTS & LIMITS
Know what the tool depends on.
Snapshots are local, best-effort edit history with configurable retention. They do not replace Git commits, off-device backups, or a recovery guarantee.
Recovery depends on a snapshot having been captured and retained. A version that was never captured or was pruned cannot be promised by the History view.
Restoring a file affects its current contents. Review unsaved work and the selected version before applying the restore.
FAQ
Local File History: common questions
You can restore a retained local snapshot when one exists. Capture must have been enabled, and the relevant version must still be within the configured retention policy.
No. Editor undo follows an editing session; Git history follows commits. Snapshots provide an additional local file timeline. Restoring a snapshot does not reset an entire repository.
No. They are local convenience history and can be pruned. Keep important work in commits and use your normal backup process.