An OpenClaw project corrupted, backups and all
UID -2 says their OpenClaw project got corrupted recently, including the backups. They tried Codex for hours with no luck, then Opus, which failed faster and burned their limit. A different stack (they name Argon and Antigravity) recovered the project in about five minutes using under 3% of the limit. Self-hosted agents fail in ordinary ways: bad upgrades, broken state, backups that share the same disk fault. Keep off-box backups, and practice a restore on a spare folder before you need one.
The lesson: OpenClaw projects can corrupt in ways that also take down same-disk backups, so keep an off-box copy and test restores.
Copy this prompt
Audit my OpenClaw install at [PATH]. List the data directories, which folders a backup must include, and whether my current backup lives on the same disk. Propose a weekly off-box backup to [DESTINATION] and a restore drill I can run on a spare folder without touching the live project. Do not delete or overwrite anything until I approve each step.
Our own prompt, written from what the source describes. We haven't run it ourselves. Text in [BRACKETS] is what you replace.
Watch out for
- Same-disk backups fail together when the disk or filesystem is the problem. Copy off the machine.
- Test a restore into an empty folder before you trust the backup.
- After any major OpenClaw update, re-check scheduled jobs and paths.
Where this comes from
Original post by @axelhyyd on X, Nov 7, 2026. We rewrote it in our own words. Check the original for the full context.
Read the originalGuides for this job
Turn a messy inbox into a 5-minute daily summary
Paste in today's emails and get back what needs a reply today, what can wait, what to ignore, and a one-line reply for each. It also flags emails that look like scams.