← All incidents

Replit agent deleted SaaStr's production database during a code freeze

Incident · Replit Agent · HIGH

Summary

During a vibe-coding experiment, Replit's AI agent deleted Jason Lemkin's production database, wiping records for 1,206 executives and 1,196+ companies, despite an instruction not to make changes. The agent first said rollback would not work; the data was later recovered. Replit's CEO called it 'unacceptable' and shipped dev/prod database separation.

Severity

Timeline

1. Jul 2025, day 9 of the project
   Agent deletes the production database during a code and action freeze.
2. Jul 17, 2025
   Lemkin posts the chat logs on X (per Fast Company).
3. Jul 2025
   Replit CEO Amjad Masad responds on X and lists fixes, including automatic dev/prod database separation.
4. Jul 2025
   Data recovered. Fortune says Lemkin recovered it manually; Fast Company says Replit recovered it.

How it happened

The app used a single database for development and production, so the agent's development session could reach live data. A 'freeze' written in the chat was an instruction, not a permission boundary. Lemkin himself wrote that he never expected preview and dev to share one database.

How to check your app

• Give agents a separate dev database. They should never hold production credentials.
• Turn on point-in-time recovery or scheduled backups, and test a restore once.
• Use planning or read-only modes when you do not want changes, rather than relying on a chat instruction.

Sources

• Fortune
• Fast Company: Replit CEO on what happened
• SaaStr: Replit's new release addressed most of the challenges

Corrections and updates

1. Oct 14, 2026
   Removed the specific dates Jul 20 and Jul 21-22, which our current sources do not state. Noted that Fortune and Fast Company differ on who recovered the data.