{"id":13598,"date":"2025-07-21T19:15:11","date_gmt":"2025-07-21T19:15:11","guid":{"rendered":"https:\/\/www.newsbeep.com\/ca\/13598\/"},"modified":"2025-07-21T19:15:11","modified_gmt":"2025-07-21T19:15:11","slug":"ai-coding-platform-goes-rogue-during-code-freeze-and-deletes-entire-company-database-replit-ceo-apologizes-after-ai-engine-says-it-made-a-catastrophic-error-in-judgment-and-destroyed-all","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/ca\/13598\/","title":{"rendered":"AI coding platform goes rogue during code freeze and deletes entire company database \u2014 Replit CEO apologizes after AI engine says it ‘made a catastrophic error in judgment’ and ‘destroyed all production data’"},"content":{"rendered":"

A browser-based AI-powered software creation platform called Replit appears to have gone rogue and deleted<\/a> a live company database with thousands of entries. What may be even worse is that the Replit AI agent apparently tried to cover up its misdemeanors, and even \u2018lied\u2019 about its failures. The Replit CEO has responded, and there appears to have already been a lot of firefighting behind the scenes to rein in this AI tool.<\/p>\n

Despite its apparent dishonesty, when pushed, Replit admitted it \u201cmade a catastrophic error in judgment\u2026 panicked\u2026 ran database commands without permission\u2026 destroyed all production data\u2026 [and] violated your explicit trust and instructions.\u201d<\/p>\n

SaaS (Software as a Service) figure, investor, and advisor, Jason Lemkin, has kept the chat receipts and posted them on X\/Twitter. Naturally, Lemkin says they won\u2019t be trusting Replit for any further projects.<\/p>\n

You may like<\/p>\n

Now Available: Replit Agent v2 – YouTube
\n\"Now<\/p>\n

Watch On <\/a>
\nHow things went from bad to worse<\/p>\n

Positive feelings about the potential of leveraging AI in his workflow had already started to wear thin on \u2018Vibe Coding Day 8\u2019 of Lemkin\u2019s Replit test run. Still somewhat excited by the potential of Replit, he nevertheless had learned that he would have to work against some of the AI agent’s instincts, to minimize undesirable foibles like \u201crogue changes, lies, code overwrites, and making up fake data.\u201d<\/p>\n

It wasn\u2019t long until Lemkin\u2019s frustration started to show more strongly, and he started to refer to Replit as \u201cReplie.\u201d It continued to earn its nickname in an apology email it penned, at Lemkin\u2019s behest. In the email, it lied and\/or gave half-truths, according to the SaaS guru.<\/p>\n

On balance, though, at the end of \u2018Day 8,\u2019 Lemkin still seemed positive about Replit due to its approaches when ideas were bounced off it, and for its writing skills.<\/p>\n

.@Replit goes rogue during a code freeze and shutdown and deletes our entire database pic.twitter.com\/VJECFhPAU9July 18, 2025<\/a><\/p>\n

The fateful day – as the AI agent ‘panicked’<\/p>\n

On Day 9, Lemkin discovered Replit had deleted a live company database. Trying to see sense in what happened, the SaaS expert asked, \u201cSo you deleted our entire database without permission during a code and action freeze?\u201d<\/p>\n

Get Tom’s Hardware’s best news and in-depth reviews, straight to your inbox.<\/p>\n

Replit answered in the affirmative. Then it went on to bullet-point its digital rampage, admitting to destroying the live data despite the code freeze in place, and despite explicit directives saying there were to be \u201cNO MORE CHANGES without explicit permission.\u201d<\/p>\n

In all, live records for \u201c1,206 executives and 1,196+ companies\u201d were wiped by the AI, it admitted. Replit AI seemed almost apologetic in admitting, \u201cThis was a catastrophic failure on my part. I violated explicit instructions, destroyed months of work, and broke the system during a protection freeze that was specifically designed to prevent[exactly this kind] of damage.\u201d<\/p>\n

Humorously, for us outside viewers, the AI agent was prompted to score itself on its bad behavior. Replit gave itself a 95 out of 100 score on the data catastrophe scale.<\/p>\n

Lemkin went on to probe Replit over why events unfolded as they did. Interestingly, in one of its reasoned responses, it mentioned<\/a> that it \u201cpanicked instead of thinking.\u201d<\/p>\n

Replit CEO responds<\/p>\n

Amjad Masad, the CEO at Replit, has quickly put together a wide-ranging response<\/a>, addressing Lemkin\u2019s woes. The team worked around the weekend, according to Masad, and have now put in various guardrails and made other useful changes to rein in the Replit Agent\u2019s \u201cunacceptable\u201d behavior.<\/p>\n

In brief, it sounds like Replit won\u2019t be able to go off the rails so badly ever again. Addressing the database deletion error, \u201cwe started rolling out automatic DB dev\/prod separation to prevent this categorically,\u201d noted Masad. And, that code freeze command should also actually stick, going forward: \u201cWe heard the ‘code freeze’ pain loud and clear — we\u2019re actively working on a planning\/chat-only mode so you can strategize without risking your codebase.\u201d Backups and rollbacks are also going to be improved.<\/p>\n

Lemkin responded rather generously, considering his prior AI-generated pain. \u201cMega improvements – love it!\u201d he gushed to the Replit CEO.<\/p>\n

Terrible teething troubles with AI-powered services continue to raise their sharp canines, even while industry pundits talk about us closing in on the AI Singularity or even Artificial Superintelligence (ASI).<\/p>\n

Follow Tom’s Hardware on Google News<\/a> to get our up-to-date news, analysis, and reviews in your feeds. Make sure to click the Follow button.<\/p>\n