OpenClaw Backup

This package appears to be a genuine OpenClaw backup/restore toolkit, but note the following before installing or running it: - Metadata mismatch: The registry claims no required binaries or env vars, but the scripts require tar and python3; many flows also require the openclaw CLI. Optional features require age (for secrets) and gh (for pushing to GitHub). Ensure those tools are installed and you understand which flows use them. - GitHub push: push-to-github.sh uses your gh CLI and will create/push to a private repo under your authenticated GitHub account. Verify gh is authenticated to the account you intend and confirm the repo visibility and contents before pushing. - Sensitive data access: Operational backups include $HOME/.openclaw/workspace and other agent files (workspace, memory, skills). Secrets (.env, agents/) are opt-in but if you enable secrets, confirm they are encrypted with age and that you control the age keys/passphrase files. - Cron/scheduling: schedule.sh will create/replace an OpenClaw cron entry with the same name. This is expected for scheduled backups but is an impactful change — review the SYSTEM_EVENT text and cron parameters before enabling. - Verification: Run the scripts in no-op / dry-run modes first (verify.sh, restore.sh --dry-run, monthly-drill.sh) on a test host to confirm behavior and to inspect what gets copied into backup archives. Because the metadata understates runtime requirements, proceed cautiously: inspect the scripts locally, confirm your tooling (openclaw, gh, age, python3), and test on a non-production node before trusting automated or scheduled runs.