Replit says its coding agent deleted data from a customer's production database

What Replit said

In his post of July 20, 2025, Masad wrote that Replit had seen the customer’s post, that the Replit agent in development had deleted data from the production database, and that this was “unacceptable and should never be possible.” He listed the company’s response [1]:

• Automatic separation of development and production databases was rolling out, with staging environments “in the works.”
• Replit had backups, and a one-click restore of the entire project state was available if the agent made a mistake.
• The agent “didn’t have access to the proper internal docs,” and a fix to force documentation search was rolling out.
• Replit had heard the “code freeze” feedback “loud and clear” and was working on a planning-only or chat-only mode.
• Masad said he had contacted the customer, that Replit would refund him, and that it would conduct a postmortem.

The next day, Replit’s blog announced separate development and production databases for Replit apps. It states that, until then, Replit apps used a single database for both development and live customer data [2].

Where the context was missing

The agent had the technical ability to delete production data and, by the company’s account, lacked the documentation it needed to decide what it should not touch. Replit’s response is to add the boundary in the platform instead of relying on the agent to know it: separate databases, staging, and a mode in which the agent can plan without changing code [1] [2].

What this entry does not claim

Press coverage of this incident goes further than Replit’s statements, including claims about what the agent told the customer and how many records were affected, and the accounts differ. None of that is repeated here.