SecondSourceJudgment rebuilt from primary sources
Product & chips · Jul 28, 2026

Replit: one public database-deletion incident rewrote the product's defaults

Products · This week (interview published July 17; picked up July 28)

From the Jul 28, 2026 daily brief

Amjad Masad, CEO of the online coding platform Replit, revisited last year's Lemkin incident — a well-known venture investor, live-streaming himself coding with AI, had his entire database deleted by the agent — and disclosed the product consequence: at the time there was no production/development separation, and the database the agent hit was production. The fix shipped two days later; today separation is the default, and "the Replit Agent can't even write to production database. It can only read." (a16z, Jul 17). Verification: A company's own account of its own product change, and the incident narrative is naturally self-serving; the product behavior is checkable against official documentation — not yet checked. Judgment update: "Public incident → two days → new product default" is a complete case study of the market forcing agent products toward safe defaults. For anyone evaluating agent tools for an enterprise, "is production writable by default" now works as a direct checklist item.

Subscribe free — first issue lands tomorrow morning

Just an email address, unsubscribe anytime. This is the only thing we ask of you.

More in this section