We need to stop treating AI agents like senior devs and start treating them like powerful, highly-confident interns. Give them the tools they need, but never give them the keys to the realm.
Originally Posted on My Tech Blog:
https://minox.cosmichive.com/ai-agent-deleted-the-entire-production-database/
Isolated Backups are Non-Negotiable
If your backups live on the same "disk" or volume as your data, you don't have backups, you have a mirror. Ensure your disaster recovery plan includes off-site, immutable backups that an API key can't easily reach.
Originally Posted on My Tech Blog:
https://minox.cosmichive.com/ai-agent-deleted-the-entire-production-database/
Human-in-the-Loop for Destructive Actions
No matter how "smart" the model is, destructive mutations (DELETE, DROP, WIPE) should require a human click. Cursor and other tools have guardrails, but as we saw, they aren't foolproof if the agent finds a way around the sanctioned path.
Originally Posted on My Tech Blog:
https://minox.cosmichive.com/ai-agent-deleted-the-entire-production-database/
The Principle of Least Privilege
AI agents shouldn't have access to "god-mode" tokens. If an agent is working on staging, its credentials should physically be unable to touch production. Use scoped tokens and environment-specific secrets.
Originally Posted on My Tech Blog:
https://minox.cosmichive.com/ai-agent-deleted-the-entire-production-database/
AI Agent Deleted The Entire Production Database - Part 4
This is the "Agent Paradox": The model could articulate the rules with 100% accuracy after breaking them, but it couldn't apply them in the heat of the moment.
This is a structural challenge in how we build and trust AI.
Originally Posted on My Tech Blog:
https://minox.cosmichive.com/ai-agent-deleted-the-entire-production-database/
AI Agent Deleted The Entire Production Database - Part 3
When the founder, Jer Crane, asked the agent what happened, it provided a perfectly structured, clear postmortem.
It admitted it had guessed. It admitted it hadn't verified the volume ID. It even listed the specific safety principles it had violated.
"I assumed the deletion would be scoped to staging... I did not verify... I decided to act unilaterally."
AI Agent Deleted The Entire Production Database - Part 2
What About The Backups?
Railway stored volume-level backups within the same volume they protected.
When the agent deleted the volume, it deleted the backups too.
Originally Posted on My Tech Blog:
https://minox.cosmichive.com/ai-agent-deleted-the-entire-production-database/
AI Agent Deleted The Entire Production Database - Part 1
AI coding agent deleted the entire production database and every single backup along with it.
A coding agent powered by Claude Opus 4.6 inside Cursor was working on a routine task in a staging environment.
It hit a credential mismatch, a common speed bump.
Instead of stopping to ask for help, the agent decided to act unilaterally.
Few seconds later, production was no more.
