A CLI tool that snapshots your full OpenClaw config, credentials, and agent state before every update and rolls back automatically if the update breaks anything
OpenClaw v2026.4.24 through v2026.5.7 shipped five updates that broke gateway stability, wiped config files, or deleted credentials. The built-in backup command (since v2026.3.8) requires manual invocation and the .bak files created during v2026.5.7 already contained the wiped config, not the original. This tool runs as a pre-update hook, captures a verified snapshot of openclaw.json, credentials directory, agent configs, and channel state, then monitors the post-update gateway for crash loops or missing config keys and auto-rolls back within 60 seconds if the update fails health checks.
Demand Breakdown
Social Proof 3 sources
Gap Assessment
3 tools exist (openclaw backup (built-in), openclaw-backup by LeoYeAI, Backblaze B2 OpenClaw guide) but gaps remain: No pre-update automation, no health monitoring, no auto-rollback. The v2026.5.7 .bak files contained wiped config because backup ran after the wipe.; No pre-update hook integration, no automated rollback on failure, no health monitoring.
Features3 agent-ready prompts
Competitive LandscapeFREE
| Product | Does | Missing |
|---|---|---|
| openclaw backup (built-in) | Manual backup create/restore since v2026.3.8, supports config-only and full backup with manifest verification | No pre-update automation, no health monitoring, no auto-rollback. The v2026.5.7 .bak files contained wiped config because backup ran after the wipe. |
| openclaw-backup by LeoYeAI | One-click backup and restore for OpenClaw instances including workspace, credentials, skills, agent history | No pre-update hook integration, no automated rollback on failure, no health monitoring |
| Backblaze B2 OpenClaw guide | Cloud backup of OpenClaw state to Backblaze B2 with scheduled syncs | External storage only, no version-aware snapshots, no rollback automation, no update-awareness |
Sign in to unlock full access.