Checkpoints and Restore
EngineForge captures file checkpoints around Crew turns so you can inspect a turn and undo the file changes attributed to it.
Checkpoint lifecycle
- Begin the task in the intended project and session.
- Let the specialist complete the bounded turn.
- Open the timeline entry to inspect its changed files or diff.
- Choose Undo only after reviewing the exact restore summary.
- Compile, import, or rerun the relevant behavior after the file restore.
What Undo targets
Undo targets the changes made by the selected turn rather than silently rewinding the entire project timeline. EngineForge identifies files to restore or remove and lists them in the confirmation. If a file changed again after that turn, the dialog warns that the later work would be overwritten.
Dirty files and conversation history
If an affected editor has unsaved changes, EngineForge asks whether to save or discard them before continuing. The restore dialog separately offers to remove later conversation content; that option starts off, because file restoration and conversation truncation are different decisions.
What checkpoints do not cover
- Generated engine folders and build output excluded by checkpoint rules.
- Media, binaries, secrets, caches, and other excluded file types.
- Live editor or running-game state outside the tracked files.
- External services and tools outside the workspace.
Safety notes
A successful restore is still a file operation, not proof that the editor has converged on the intended state. Review the reported outcome and rerun the relevant checks. Keep the project in source control for durable history beyond the EngineForge session.