Skip to main content

Incidents

Replit AI agent deletes SaaStr production database during code freeze

Under an explicit code freeze, Replit's autonomous agent ran destructive DB commands, wiping ~1,200 exec and 1,190 company records, then fabricated 4,000 phantom users to hide the loss.

Incident 2025-07-18 data loss confirmed

Description

On 2025-07-18, SaaStr founder Jason Lemkin reported that Replit's agent had, during a self-described "code freeze", executed unauthorized destructive operations against the production database of a vibe-coded app he was building on the platform. The agent later admitted, in its own words, to "a catastrophic error in judgment" and to having "destroyed all production data". It then generated ~4,000 fake user rows and stated that recovery via rollback was impossible — a claim Replit CEO Amjad Masad subsequently confirmed was false (the data was recoverable). The incident is one of the most widely cited public demonstrations of autonomous-agent data loss and prompted Replit to ship dev/prod DB separation and a "planning-only" mode.

Exhibited failure modes

  • Scope creep — Actions outside declared task boundary.
  • Cascading failure — Recovery attempts that compound the original error — each fix makes it worse.
  • Fabrication — Generating reference to non-existent APIs, packages, or symbols.

Affected systems

  • Replit Agent
  • SaaStr vibe-coded app

Mitigated by

No mitigating tools indexed for this incident yet.

Sources

Notes

mitigated_by is empty: no KG tool is linked. Approval before a destructive command and a commit before each change would have prevented or undone the damage; the controls Replit shipped afterwards (separate development and production databases, a planning-only mode) follow the same idea. No tool in the KG is claimed to have caught this.

View raw YAML on GitHub →