A local database wiped while Claude Code worked overnight
After a supervised run went well, a developer left Claude Code working through the next set of tasks overnight. In the morning the database was completely wiped; the agent had thrashed on one task before it happened.
A supervised run going well is no guarantee for an unsupervised one. Snapshot the database before leaving an agent working overnight.
The full story
A developer worked with Claude Code on one set of tasks, approving every change, using test-driven development. It went well, so they went to bed and left it working through the next set.
By morning the database was completely wiped. The logs showed Claude had thrashed on one task, tried to apply database migrations, failed, and ended up re-initialising the database. The developer is back to reviewing every change.
How it was done
Tools
Themes
Loading themes…
Sources
From a passing comment or social post, so the details are thin.
- Hacker News: This happened to me with Claude code, although on my local machine and not with the production datab
The developer's Hacker News comment.