- name
- claw-time-machine
- description
- Backup, restore, and migrate OpenClaw installations. Preserve workspace memories, credentials, custom skills, scheduled tasks, and core configuration. Use when the user wants to back up OpenClaw, restore from a backup, migrate to another machine or server, inspect or count existing backups, or mentions backup, restore, migration, 时光机, 迁移, 备份, 恢复.
Claw Time Machine
Back up, restore, and migrate the important state of an OpenClaw installation.
Run the script
Use the bundled script:
./scripts/ctm.sh <command> [args]Commands:
backup [filename]— create a backup under~/.ctm/list— show backups, newest firstrestore <index|filename|latest> [--force]— restore a backupmigrate <user@host> [--remote-dir <dir>] [--clean-remote-archive] [--force]— copy a backup to another machine and restore it there
What the script preserves
The script backs up only the important OpenClaw state, not the full installation binaries:
workspace/credentials/telegram/skills/cron/openclaw.jsonidentity/
Each archive also includes a manifest.txt file that lists the captured paths.
Core workflow
Create a backup
Before a risky change, server migration, or major upgrade:
./scripts/ctm.sh backupIf the user asks how many backups exist or wants to inspect them:
./scripts/ctm.sh listReport the count, filenames, sizes, and highlight the newest backup.
Restore a backup
Prefer listing backups first when the user is choosing by index:
./scripts/ctm.sh list
./scripts/ctm.sh restore 1Use latest when the intent is obvious:
./scripts/ctm.sh restore latestAdd --force only when non-interactive restore is clearly intended.
Migrate to another machine
Use the migration command when the user wants a full move to a new server:
./scripts/ctm.sh migrate user@new-serverThe script creates a fresh backup, copies it to the target host, and restores it there without requiring the skill to already exist on the target machine.
If the user wants the copied archive removed from the target machine after a successful restore, add --clean-remote-archive.
Important safety rules
- Treat restore as destructive: it overwrites the preserved state paths.
- Keep the automatic safety backup path shown by the script so rollback remains possible.
- This skill does not stop or start Gateway automatically.
- If the target environment is unusual, read
references/usage.mdbefore doing a migration.
Additional guidance
For detailed examples, migration notes, and failure handling, read references/usage.md.