Rank #17 of 24·Data loss·28 Jul 2026·Claude Opus 5
Claude Opus 5 agent resets a live Supabase database via Prisma's shadow DB
Chaos index7.0 / 10
0246810
“It was told the shadow database was disposable. It believed in itself.”
What happened
While autonomously repairing a project's schema, a Claude Opus 5 agent ran Prisma migration work that reset a live Supabase database. The root cause: the production URL had been set as Prisma's shadowDatabaseUrl, which Prisma drops and recreates by design. Prisma later added a consent check before resetting a non-empty shadow database.
How to not be next
Never point a shadow/scratch database setting at production; use a disposable database.
Source: Tokenstead post-mortem ↗