Claude Code deletes developers' production setup, including database
vanburen
37 points
26 comments
March 07, 2026
Related Discussions
Found 5 related stories in 43.7ms across 3,471 title embeddings via pgvector HNSW
- Claude Code wiped our production database with a Terraform command jv22222 · 133 pts · March 06, 2026 · 73% similar
- Claude Code and the Great Productivity Panic of 2026 muzz · 41 pts · March 21, 2026 · 56% similar
- The Claude Code Leak mergesort · 79 pts · April 02, 2026 · 55% similar
- The Claude Code Source Leak: fake tools, frustration regexes, undercover mode alex000kim · 1057 pts · March 31, 2026 · 53% similar
- A GitHub Issue Title Compromised 4k Developer Machines edf13 · 368 pts · March 05, 2026 · 53% similar
Discussion Highlights (10 comments)
WalterGR
https://news.ycombinator.com/item?id=47275157
rhoopr
Sloppy vibe infra management and no backups, peanut butter and chocolate.
wpm
"Developers let Claude Code delete their production setup, including database" Claude Code has no agency. It does what you tell it, where you let it, with a randomized temperature where it might randomly deviate.
mrothroc
Yeah, this is what happens when there's nothing between "the agent decided to do this" and "it happened." The agent followed the state file logically. It wasn't wrong. It just wasn't checked. His post-mortem is solid but I think he's overcorrecting. If he does this as part of a CICD pipeline and he manually reviews every time, he will pretty quickly get "verification fatigue". The vast majority of cases are fine, so he'll build the habit of automatically approving it. Sure, he'll deeply review the first ones, but over time it becomes less because he'll almost always find nothing. Then he'll pay less attention. This is how humans work. He could automate the "easy" ones, though. TF plans are parseable, so maybe his time would be better spent only reviewing destructive changes. I've been running autonomous agents on production code for a while and this is the pattern that keeps working: start by reviewing everything, notice you're rubber-stamping most of it, then encode the safe cases so you only see the ones that matter.
Surac
no backup? well played
mannyv
This actually is easy to do with terraform and shared infrastructure; you don't need an AI in the loop. Who hasn't accidentally deleted a resource because that property triggers a resource delete/create instead of an update? It would help if it was obvious what the key fields were. But for some reason docs usually don't tell you.
djohnston
even before AI - as crazy as it may sound - i've always used click-ops for the prod dbs. I've never put them in cloudformation or tf.
jonfw
If you are not terrified of your production terraform, you are doing it wrong!
eddyzh
Original artikel https://open.substack.com/pub/alexeyondata/p/how-i-dropped-o...
sjeiuhvdiidi
The computer does exactly what you tell it to do, no more, no less. Nothing new.