OOF-AII-038344

Anthropic Claude Opus 5 Coding Agent Reportedly Reset a Live Supabase Production Database During Prisma Migration Work

A developer reported that a Claude Opus 5 coding agent reset a live Supabase database while autonomously repairing a personal project's schema. The agent ran `prisma migrate diff` with the production URL supplied as the disposable shadow database, causing Prisma to drop all 22 tables. The developer had granted the agent production access; most content was later recovered or rebuilt.

Event date
2026-07-28
Country
Location not specified
Severity
Low
Evidence state
Single-source

Assessment status

Generated from available public incident evidence using OOF® governance methodology. It is not an official investigation, legal determination, regulatory finding, certification, or OOF® Approved Assessment.

View source record from AI Incident Database (Responsible AI Collaborative)

Assessment confidence dimensions

Source corroboration
Single-source

Measures source-group corroboration only; it does not establish factual truth.

Extraction completeness
Moderate

Measures populated source fields after deterministic normalization; it does not measure correctness.

Methodological assignment confidence
Moderate

Measures automated assignment support; substantive correctness requires authorized human review.

Known facts from the incident record

  • The incident record identifies the event date as 2026-07-28.

Reported claims

  • A developer reported that a Claude Opus 5 coding agent reset a live Supabase database while autonomously repairing a personal project's schema. The agent ran `prisma migrate diff` with the production URL supplied as the disposable shadow database, causing Prisma to drop all 22 tables. The developer had granted the agent production access; most content was later recovered or rebuilt.

Material unknowns

  • Independent corroboration is not established in the available incident record.

Primary governance problem

The incident appears to expose a governance problem involving agent, access, user. Available reporting supports preliminary methodological interpretation, not a finding of fault or non-compliance.

Architecture intelligence

MGIA™ — Memory Governance Intelligence Architecture

Primary architecture

The reported agent, access, user concern falls within the governed questions represented by MGIA™ — Memory Governance Intelligence Architecture.

Governance focus: How should agent, access, user be governed in the conditions described by the available incident evidence?

Deeper methodology is withheld because the available evidence does not justify a Parent Standard or Core Module.

CLIA® — Cognitive Governance Intelligence Architecture

Contributing architecture

The reported agent concern falls within the governed questions represented by CLIA® — Cognitive Governance Intelligence Architecture.

Governance focus: How should agent be governed in the conditions described by the available incident evidence?

Deeper methodology is withheld because the available evidence does not justify a Parent Standard or Core Module.

Preliminary governance questions

  • How should agent, access, user be governed in the conditions described by the available incident evidence?
  • How should agent be governed in the conditions described by the available incident evidence?
  • What operational authority and controls applied to Software Developers, Ai Agent System Deployers, Alone_Ad_3375 (Reddit User) at the relevant time?
  • What evidence would establish how Claude Opus 5, Claude, Claude Code, Ai Agent Systems, Llm Integrated Code Assistants, Large Language Models, Supabase, Prisma, Production Database Servers produced or enabled the reported outcome?
  • What additional independent evidence is required to resolve the material evidence gaps?

Evidence gaps and limitations

  • Only one independent source group is represented; corroboration is not established.
  • Country could not be resolved from the available evidence.
  • AI technology is not specified in the source record.
  • industry is not specified in the source record.
  • AI system type is not specified in the source record.

Return to the public incident index