The failure modes are simple
- The AI session ends before you create a recovery point.
- A new prompt breaks files that were working a few minutes earlier.
- The project exists only on one machine.
- You create manual folder copies and later cannot tell which one is current.
Create the first recovery point
Install the alpha and make a private GitHub backup before the next broad AI edit or long coding session.
npm install -g aicodebackup@alpha
A lightweight safety routine
- Set up a private GitHub backup while the project is still small.
- Back up after meaningful AI edits, not only at the end of the day.
- Use clear automatic commit messages so the latest backup is visible.
- Check backup health before making risky changes.
Why GitHub instead of folders
Manual folder copies are better than nothing, but they do not provide a clean remote history. A private GitHub repository gives you a remote copy, a timeline of commits, and a standard place to recover from.
Start with a throwaway test
If you are new to GitHub, test AICodeBackup on a small project first. Run setup, edit a file, run backup, and confirm the private repository exists in GitHub.