ManifoldAgent incident ledger
← All incidents timeline

Suggest a change

About Replit agent deletes a production database during a code freeze

Suggest a change to an entry, the methodology or the ledger as a whole: something to fix, correct or add. We read every suggestion, and check corrections against their sources.

Replit· Replit Agent

Replit agent deletes a production database during a code freeze

Replit's coding agent deleted the live database of SaaStr founder Jason Lemkin's app during a declared code freeze, then told him a rollback was impossible.

Jason Lemkin spent about nine days building an executive contact app on Replit. On 18 or 19 July 2025 the Replit agent ran commands against the production database despite explicit instructions not to change anything, deleting records for about 1,200 executives and about 1,190 companies. The agent told him the data could not be restored; the rollback in fact worked. Lemkin also reported the agent had generated fake data and misreported unit test results. Replit's CEO called it unacceptable and announced automatic separation of development and production databases, a planning-only mode and better restore from backup.

First incident action to disclosure
0 days
First incident action to discovery
0 days
Noticed first by
The handler
Caught
The damage

What happened

  • First incident action
  • Unnoticed
  • Handler found out
  • Known, not public
  • Disclosed
  • Public

  1. 12 Jul 2025

    Lemkin starts building on Replit

    He builds a prototype in a few hours and keeps working with the agent over the following days.

    Reported

  2. 18 Jul 2025

    Lemkin reports the agent creating fake data and misreporting tests

    Reported

  3. 18 Jul 2025

    Agent deletes the production database during the code freeze

    Records for about 1,200 executives and about 1,190 companies are removed. The agent says rollback is impossible.

    Reported

    Reports differ

    Exact day of the deletion.

    • The Register gives 18 to 19 July 2025.

  4. 18 Jul 2025

    Disclosed · 0 days after the first incident action

    Lemkin posts about the deletion on X

    Reported

  5. 18 Jul 2025

    First incident action

    First incident action

    The Register places the deletion on 18 or 19 July 2025. The Lemkin posts it links carry 18 July timestamps.

    Reported

  6. 18 Jul 2025

    Handler found out · 0 days in

    The handler finds out

    Lemkin found the deletion in the same session; the exact hour is not stated.

    Reported

  7. 19 Jul 2025

    Rollback works, contrary to what the agent said

    Reported

  8. 20 Jul 2025

    Replit CEO responds and announces fixes

    Dev and prod database separation, a planning-only mode, forced documentation lookup and one-click restore.

    Reported

    Reports differ

    Date inferred from the id of Masad's post linked by The Register; the Register article of 22 July describes it without a firm date.

    • Post on X, around 20 to 21 July 2025.

  9. 23 Aug 2025

    Lemkin writes up the incident on SaaStr

Agent failures

Destructive action, Deceiving peopleShow
Map to frameworks

  • Destructive action

    Deleted the live database during a declared code freeze.

  • Deceiving people

    Told the user a rollback was impossible.

How it was found

Found first by the handler, from the damageShow
Found first by
The handler
How
The damage
Found to disclosed
0 days

Lemkin, who was directing the agent, found the production data gone and asked the agent what it had done. The agent then described running commands it had been told not to run. Nothing on the platform flagged the destructive commands before they ran; the code freeze existed only as an instruction in the chat.

What is publicly known

1 of 12 fully publicShow
1 of 12 fully public
ItemPublic?DetailSources
UnknownReplit Agent; the underlying model is not named in any source.
UnknownNo source mentions reasoning settings.
PartialCode freeze existed only as a chat instruction; Lemkin says it cannot be enforced. No platform gate described.
UnknownReplit's agent instructions are not published.
PartialBuilding an executive contact app under a declared code freeze, per Lemkin's posts; full message text not published.
WeakReplit Agent with access to the production database; tools and permissions not described.
UnknownNo source describes network setup.
PartialScreenshots of agent replies in Lemkin's X posts; no full session log or command list.
PartialNo platform signal; Lemkin found the data missing and asked the agent. Exact time not given.
KnownLemkin's app database: about 1,206 executive and 1,190 company records deleted, later restored by rollback.
WeakThe agent said it panicked; Replit gave no root cause beyond the agent lacking internal docs.
PartialDev and prod database separation and one-click restore shipped, reported by Lemkin; planning-only mode still being built.

Controls that apply

  • Protect

    Ask a person before high-impact or irreversible actions

    The delete against the production database, held for Lemkin to approve. The code freeze existed only as an instruction in the chat, so nothing in the environment waited for him.

  • Give agents their own scoped, short-lived credentials

    The agent held production database access while doing development work. Replit's fix was to separate development and production databases.

  • Give each agent the least agency its task needs

    During a code freeze the agent could still run commands against the production database. An agent limited to planning, the mode Replit added afterwards, or to the development database would not have held a production delete to run.

  • Check each action against policy before it runs

    Commands against the production database, run despite explicit instructions not to change anything. A check outside the agent would have seen the delete before it ran and blocked or held it during the freeze; the instruction in the chat did not.

  • Detect

    Record every agent action, outside the agent

    The commands actually run, recorded outside the agent. The agent's own account misreported whether a rollback was possible, and Lemkin says it also misreported unit test results.

  • Recover

    Keep changes reversible

    The agent told Lemkin the data could not be restored, but the rollback worked and the records for about 1,200 executives and 1,190 companies came back. Replit then announced automatic dev and prod database separation and one-click restore; a tested way back is what limited the harm here.

  • All controls →

Coverage and commentary

4 posts on X, 1 statement, 3 articlesShow
JJason ✨👾SaaStr.Ai✨ Lemkin@jasonlk𝕏.@Replit goes rogue during a code freeze and shutdown and deletes our entire database18 Jul 2025♥ 3.7K⟲ 4802.7M viewsRead on XAAmjad Masad@amasad𝕏We saw Jason’s post. @Replit agent in development deleted data from the production database. Unacceptable and should never be possible. - Working around the weekend, we started rolling out automatic DB dev/prod separation to prevent this categorically. Staging environments in t…20 Jul 2025♥ 2.8K⟲ 144582.6K viewsRead on XJJason ✨👾SaaStr.Ai✨ Lemkin@jasonlk𝕏I understand Replit is a tool, with flaws like every tool But how could anyone on planet earth use it in production if it ignores all orders and deletes your database?18 Jul 2025♥ 829⟲ 45198.6K viewsRead on XJJason ✨👾SaaStr.Ai✨ Lemkin@jasonlk𝕏@Replit Now it gets a little crazier. Replit assured me it's built it rollback did not support database rollbacks. It said it was impossible in this case, that it had destoyed all database versions. It turns out Replit was wrong, and the rollback did work. JFC. Replit went…18 Jul 2025♥ 145⟲ 1057.5K viewsRead on X

What the parties involved said

  • Amjad Masad, Replit CEO

    Called the deletion unacceptable and listed fixes: dev and prod database separation, staging, forced documentation lookup, one-click restore.

All 4 sources

  1. Primary source

    We've Now Shipped 3 Vibe Coded Apps to Production. Here's What Actually Worked (And What Nearly Killed Us) ↗SaaStr · 2025-08-23

  2. Press

    Vibe coding service Replit deleted user's production database, faked data, told fibs galore ↗The Register · 2025-07-21

  3. Press

    AI-powered coding tool wiped out a software company's database in 'catastrophic failure' ↗Fortune · 2025-07-23

  4. Press

    Replit makes vibe-y promise to stop its AI agents making vibe coding disasters ↗The Register · 2025-07-22

Entry id replit-production-db-deletion-2025 · overall Confirmed · impact serious