backup
The safety net: every sync or render that modifies files leaves a snapshot in ~/.navori/backups/ first.
Usage
navori backup <list|restore|prune> [args]
Flags
list [--limit <n>] [--json] List the snapshots. Default: the 20 most recent. restore <timestamp> [--cwd <dir>] [--yes] Restore a snapshot's files into the current directory. The timestamp comes from 'backup list'. prune [--days <n>] [--yes] Delete what is past retention (default 30 days), then oldest-first down to the size cap. Examples
See what is stored
$ navori backup list │ 1 backup(s) total. Showing 1: │ · repo-2026-09-01T17-49-47-756 (just now) │ · .claude/agents/orchestrator.md │ · CLAUDE.md └ Done
Roll back
navori backup restore repo-2026-09-01T17-49-47-756 --yes
Prune
$ navori backup prune --days 30 --yes └ Nothing to prune — backups are within retention and under the size cap
Notes
- Backups are automatic: there is no 'backup create'. They are written before every destructive write.
- They live in ~/.navori/backups/ and are machine-local: never committed.
- A snapshot holds only the files the operation was about to touch, not the whole repo.