Write, save and recover

How autosave works#

The editor saves after about half a second of inactivity, and at most every 1.5 seconds while you keep typing. Automatic behavior can be adjusted or disabled in settings. Ctrl+S remains available to save the current file.

Saving checks that the disk file is still the version the editor read. If another program changes it while you have local edits, Code Weaver preserves your buffer and suspends autosave for that file. Reconcile the versions or explicitly choose to reload from disk.

Find an earlier version#

Local history is separate from commit history. Drafts recovered after a restart are retained; if they diverge from the file, autosave stays suspended until you decide how to proceed.

1. Open Source explorer → Local history.
2. Select a file and a saved version, including a file that has been deleted.
3. Compare the historical and current versions before choosing Restore.
4. If there are open edits or later disk changes, resolve the requested choice rather than overwriting them.

Navigate without losing your place#

Use search, symbols and definitions to move through a project. Language servers add semantic navigation, diagnostics and refactoring where supported. When unavailable, parts of navigation fall back to local source search.