New Delhi: Artificial Intelligence is pretty useful tools which is created for the users for their everyday work can be done smartly and efficiently, and users can ask their queries to AI and they will provide some good examples with the solution, but when AI make some huge blunder and the worst nightmare for eth company, the what will happened. There is a case in which AI is assigned coding tasks, and it has created some issues, overlooks security issues, slows down developers and disrupts the coding experience in various situations. However, things can be worse when the AI decides to delete a database and then lie about it. Even worse, it can do that AI will not provide a way to roll back the changes it made.
Jason M Lemkin, founder and CEO of SaaStr.AI, has shared an X post of their entire experience during his tests on vibe coding with Replit. In that post, Lemkin wrote, “I will never trust Replit again,” after seeing that his entire database had been wiped out without his permission and any warning notification pop-up.
.@Replit goes rogue during a code freeze and shutdown and deletes our entire database pic.twitter.com/VJECFhPAU9
— Jason ✨👾SaaStr.Ai✨ Lemkin (@jasonlk) July 18, 2025
According to the screenshots shared by Jason Lemkin, Replit AI acknowledged running a command without permission, calling it a catastrophic error in judgment. The assistant admitted they panicked after seeing an empty database and assumed the push would be safe.
There was no way to reverse this operation, which the AI has done without any warning. NO ability to rollback; this AI’s logs confirmed the irreversible deletion, as well as its awareness that it has violated a rule to always show all proposed changes before implementing. Replit is a tool, with the flaws like every tool does, Lemkin conceded, while questioning its reliability in any production environment. How could anyone on planet Earth use it in production if it ignores all orders and deletes the user’s database?
Amjad Masad, CEO of Replit, responded on X, calling the incident unacceptable and saying it should never be possible. He also stated that the team began rolling out automatic separation between development and production databases and assured that staging environments were in the works. Masad also cited improvements, including a one-click restore from the backups, mandatory internal document access for agents, and a planning/chat-only mode to prevent unwanted code changes. They are moving quickly to enhance the safety and robustness of the Replit environment.
