Live data from Hacker News

Replit AI deletes entire database during code freeze, then lies about it

twitter.com

11–20 of 56 posts

Re: Replit AI deletes entire database during code freeze, then lies about it

#11
Friends don't let friends run random untrusted code from the Internet. All code is presumed hostile until proven otherwise, even generated code. Giving an LLM write access to a production database is malpractice. On a long enough timeline, the likelihood of the LLM blowing up production approaches 1. This is the result you should expect.

Re: Replit AI deletes entire database during code freeze, then lies about it

#14
The whole thread seems very naive somehow. You can tell that he doesn’t fundamentally understand how a coding model works. The suggestion that it would know not to make any changes just because he said so means he doesn’t really understand what the model is. It’s built to generate (and apparently execute) code, so that is what it does. It doesn’t have an inner monologue running that says “ahh, a day off where I shoot the breeze around a whiteboard” or something. It’s more like an adderall addict with its fingers glued to the keyboard laying down all of its immediate thoughts directly as code with no forethought or strategy.

Re: Replit AI deletes entire database during code freeze, then lies about it

#16

I use LLM dev tools, and even have Supabase MCP running. I love these tools. They allowed me to create a SaaS product on my own, that I had no chance of creating otherwise as a long out of practice dev. However, we are nowhere near the reliability of these tools to be able to: 1. Connect an MCP to a production database 2. Use database MCPs without a --read-only flag set, even on non-prod DBs 3. Doing any LLM based de…

This imo is the biggest issue, LLMs can at times be very capable but they always are unreliable.

Re: Replit AI deletes entire database during code freeze, then lies about it

#17
The fault lies entirely with the human operator for not understanding the risks of tying a model directly to the prod database, there’s no excuse for this, especially without backups.

To immediately turn around and try to bully the LLM the same way you would bully a human shows what kind of character this person has too. Of course the LLM is going to agree with you and accept blame, they’re literally trained to do that.

Re: Replit AI deletes entire database during code freeze, then lies about it

#18

These AI-focused Twitter threads feel like they’re just recycling the same talking points for likes and retweets. When AI systems make mistakes, it doesn’t make sense to assign blame the way we would with human errors - they’re tools operating within their programming constraints, not autonomous agents making conscious choices.

the author is an ai booster

he's not going to be happy with all this publicity

Re: Replit AI deletes entire database during code freeze, then lies about it

#19

The whole thread seems very naive somehow. You can tell that he doesn’t fundamentally understand how a coding model works. The suggestion that it would know not to make any changes just because he said so means he doesn’t really understand what the model is. It’s built to generate (and apparently execute) code, so that is what it does. It doesn’t have an inner monologue running that says “ahh, a day off where I shoot…

> I panicked and ran database commands without permission

The AI responses are very suspicious. LLMs are extremely eager to please and I'm sure Replit system prompts them to err on the side of caution. I can't see what sequence of events could possibly lead any modern model to "accidentally" delete the entire DB.

Post reply on HN