AI agent workspace backup for OpenClaw.

ReClaw gives OpenClaw operators encrypted restore points for memory, config, sessions, credentials state, and workspace files without sending readable archive contents to the server.

Why Workspace Backup Matters

An OpenClaw workspace is working memory for an agent. It can contain standing instructions, personal context, tool notes, skills, daily memory logs, and the files the agent actively edits.

A private git remote is useful for source-like workspace files. ReClaw covers the operational backup path around that workflow: encrypted archives, backup cadence, restore metadata, and a CLI restore command that verifies the downloaded archive.

  • Create a restore point before risky prompts, package upgrades, and configuration changes.
  • Keep a remote ledger of backup status, expiration, client version, and restore readiness.
  • Recover a verified archive on a fresh host without exposing backup plaintext to ReClaw.

Start With One Restore Point

Install the CLI, bootstrap the sealed vault, and capture a labeled restore point before changing the agent environment.

curl -fsSL https://reclaw.io/install.sh | sh
reclaw backup bootstrap
reclaw backup create --label "Before workspace changes"
reclaw backup list --json

Verify Before You Trust It

A backup that cannot be found, decrypted, and verified is not a recovery plan. ReClaw keeps the restore workflow explicit so operators can run drills before an incident.

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

Privacy Boundary

The ReClaw server stores ciphertext, encrypted metadata, wrapping material, and operational state. The backup passphrase and readable archive contents stay local.

ReClaw cannot recover a lost passphrase. Treat it like the key to your agent memory.