Snapshots let you back up everything Crew knows and does — memory, crons, skills, config, agent settings — into a single portable file. Use them to move to a new machine, recover from a problem, or keep two instances in sync.
Open Settings → Backup & Restore and click Create Snapshot. The dashboard shows existing snapshots with timestamps and sizes.
kirocrew snapshot # → ~/.kiro/crew/snapshots/ kirocrew snapshot ~/my-snapshots --keep 3 # custom dir, prune to 3 kirocrew snapshot --list # list existing snapshots
| Component | What it covers |
|---|---|
| Memory | Episodic memory, semantic memory, FTS index |
| Workspace | Preferences, projects, history, knowledge library |
| Crons | All scheduled jobs |
| Config | Settings, session map, hooks, project/workspace paths |
| Skills | Custom skill definitions |
| Notifications | Dashboard notification history |
Open Settings → Backup & Restore and click Restore. Select a snapshot file.
kirocrew restore snapshot.tar.gz # auto-detect mode kirocrew restore snapshot.tar.gz --components memory,crons # selective kirocrew restore snapshot.tar.gz --dry-run # preview without writing
The mode is auto-detected. Override with --mode replace or --mode merge.
A built-in cron job runs at 08:00 UTC and keeps the last 7 snapshots:
kirocrew-daily-snapshot → kirocrew snapshot --keep 7
Disable or adjust from the Schedule panel.
# On the source kirocrew snapshot ~/migrate # Copy the tarball to the new machine, then: kirocrew restore ~/migrate/snapshot-*.tar.gz kirocrew doctor
kirocrew snapshot --list kirocrew restore ~/.kiro/crew/snapshots/kirocrew-2026-07-15.tar.gz --mode replace
Only want the crons from a snapshot, not the memory?
kirocrew restore snapshot.tar.gz --components crons
Some things live outside the data home and aren't included:
kiro-cli credentials — log in on the target machine separately~/.aws/*For a full migration: snapshot + kirocrew setup on the new machine + re-install apps.
Snapshot & restore