Create and restore checkpoints
Save a project checkpoint before a large change, compare it with current files, and understand restoration and retention boundaries.
Guides follow the current project source. Check the release notes for your installed version.
What a checkpoint captures
A checkpoint records the project state that RepoTunnel’s AI access layer can safely read. Protected secrets and ignored build/dependency folders are outside that accessible snapshot.
Use checkpoints as local recovery points for a selected approved project. They complement Git commits and ordinary file-edit versions; they do not capture the entire machine or every external service.
Create one before a large change
Choose the correct project, open Home and select Create checkpoint. Wait for RepoTunnel’s saved result, then open History to find the new checkpoint.
Give a useful checkpoint a recognizable name. The manager supports renaming and pinning records so an important recovery point is easier to identify.
- Confirm the selected project before creating the snapshot.
- Use a name that describes the working state you intend to preserve.
- Check that the saved record appears before starting the larger task.
Compare before restoring
In History’s Checkpoints section, select the record and inspect its comparison with the current project. The comparison reports modified files, files added since the checkpoint and files now missing.
Search, date grouping and Load More help locate an older checkpoint. Use All projects or Active project only to choose the visible scope, and review the affected paths before approving a restore.
Restore and verify the result
Restoration requires read/write access to the checkpoint’s project. It returns the AI-accessible files to the captured state, including removing new accessible files created after the checkpoint. Protected and ignored files remain outside that restoration.
Select the intended checkpoint, review the affected paths and read the local confirmation. RepoTunnel creates a fresh pre-restore checkpoint first. Inspect the returned restored/removed-file result and run relevant verification before resuming work; running services and remote actions are separate state.
Delete only the recovery data you intend
Deleting one checkpoint removes that recovery point without changing current project files. Clear All Checkpoints uses the manager’s current scope: all approved projects in All projects view or when no project is selected, otherwise the active project.
The local confirmation identifies that scope, and clearing includes pinned checkpoints. Check it before confirming. Retention is configured in Settings; protected-file rules remain in force during capture, comparison and restoration.