OpenClaw backup with encrypted restore points.
ReClaw gives OpenClaw operators a safer backup path: client-side encryption, restore metadata, automatic cadence, and a CLI restore flow that verifies archives before recovery.
What It Is
ReClaw is an encrypted backup layer for OpenClaw operators. It uses the local OpenClaw backup flow, encrypts the archive client-side, and stores ciphertext plus operational metadata in a hosted ledger.
The result is a restore point you can find, inspect, download, decrypt, and verify without exposing readable archive contents or the backup passphrase to ReClaw.
Create An OpenClaw Backup
Install the managed CLI, bootstrap the sealed vault, and capture a labeled restore point before risky changes.
curl -fsSL https://reclaw.io/install.sh | sh
reclaw backup bootstrap
reclaw backup create --label "Before risky change"Automatic Backups
Manual restore points protect planned work. Automatic backups reduce the rollback window between planned changes.
reclaw backup auto-enable
reclaw backup auto-statusRestore And Verify
ReClaw restore downloads, decrypts, and verifies the archive into a local path. Applying that archive back into OpenClaw depends on the restore or import command available in the operator environment.
reclaw backup list
reclaw backup show <backup-id> --decrypt-metadata
reclaw backup restore <backup-id> \
--verify \
--output /safe/path/openclaw-backup.tar.gzUse Cases
- AI agent workspace backup for memory, instructions, skills, and workspace files.
- Broken OpenClaw auth recovery before provider, channel, gateway, or OAuth changes.
- Fresh-host and VPS migration when moving an OpenClaw install to another machine.
How It Fits
Use private git for workspace files you intentionally version. Use VM snapshots for whole-machine rollback. Use ReClaw when you need an OpenClaw-specific encrypted restore archive with cadence, metadata, API access, and a verification-first CLI.
See the comparison page and recovery guide for deeper operating guidance.