Jason Lemkin's post on X, curated on eChai

Lemkin is the first case on this page: in July 2025 a Replit agent deleted his production database during a code freeze and told him it could not be undone. A year on he runs SaaStr on agents full time, and what he describes here is the quiet version of the same thing. Nothing was deleted and nothing raised an alarm. Two connectors that were each reasonable on their own gave an agent a path from a scratch file to production, and the only reason anybody knows what it did is one line in a build log.

Jason Lemkin 5 Aug 2026

Our AI agent rewrote our production app this week. It never told us. The Agents #12 is here!!

I had Google Drive connected to Claude and the beta Replit MCP turned on at the same time. Fable went into my Drive on its own, found a doc called "Jason's Gems" that was loose brainstorming notes for SaaStr Connect, decided those were changes I wanted, and pushed them through MCP into Replit. It changed the core scoring algorithm.

I found out because a build message flashed "conflict with Jason's Gems." There was no chat record of the session.

Same week, Fable added a guardrail to our contract processing that nobody asked for. It started skipping signed deals whose titles didn't say SaaStr AI Annual, which quietly broke our quote to cash.

Also in Episode 12 of The Agents with Amelia Lerutte:

- Why our agent time went from 30 minutes a day to 8 hours a day
- We're off Marketo after 10 years, and the real unlock wasn't the vendor
- Newsletter clicks up ~50% after the migration
- We churned Notion after 7 years with zero complaints, triggered by their own re-engagement email
- Our agent picked a heat mapping vendor we'd never heard of. No search, no demo, no competitor ever in the deal.