What automatic should mean for code safety
For early AI coding projects, automatic backup should reduce friction without hiding what matters. Users should know where the code goes, whether the repository is private, and whether the latest backup succeeded.
Install the backup command first
Start with manual, visible backups. Install the alpha, run setup, then use watch or backup when AI coding sessions become risky.
npm install -g aicodebackup@alpha
AICodeBackup V0.1 automation
- Environment checks for Git and GitHub CLI.
- Guided GitHub login through the browser when needed.
- Private repository creation when no remote exists.
- A single backup command that adds, commits, and pushes changes.
- A doctor command that reports the health of the backup path.
When to trigger a backup
Run a backup after working features, before risky prompts, before dependency upgrades, and before ending a long AI session. Future versions may add watch and reminders, but the first useful habit is manual confirmation that the backup happened.
Why not silently push everything all the time
Early AI projects can contain accidental files, local notes, or secrets. A clear command gives the user a moment to understand that code is about to be committed and pushed to GitHub.