Recover from broken OpenClaw auth changes.

OpenClaw operators often change provider auth, channel credentials, gateway settings, or agent configuration while the system is already in use. If that change breaks access, the same agent that could help repair the issue may be unreachable.

ReClaw is built for the moment before that change. Capture a labeled restore point while the environment is still healthy.

• Before OAuth, API-key, channel, or gateway auth changes.
• Before updating OpenClaw or adding a new skill that touches credentials.
• Before moving from localhost access to remote access, tunnels, or a proxy.

Use a label that names the risk, not just the date. That makes recovery faster when a future operator scans the ledger.

reclaw backup create --label "Before provider auth rollout"
reclaw backup show <backup-id> --decrypt-metadata

When access breaks, use ReClaw to download, decrypt, and verify the archive into a safe local path. Applying the archive back into OpenClaw depends on the restore or import command available in that OpenClaw environment.

reclaw backup restore <backup-id> \
  --verify \
  --output /safe/path/openclaw-backup.tar.gz

Manual restore points are best before known risky changes. Automatic backups cover unexpected damage between planned maintenance windows.

reclaw backup auto-enable
reclaw backup auto-status