AI agent reset your database? Restore it and stop it next time

To fix drift, Prisma can offer the big hammer. Its docs say prisma migrate reset “Drops the database/schema if possible” and then rebuilds it empty. The docs mark it “For use in development environments only”.

prisma db push has a safety too. When a change could lose data, it needs --accept-data-loss. Prisma: “This option is required if as a result of making the schema changes, data may be lost.” An agent that adds that flag, or answers yes, has said yes for you.

Prisma now stops agents, until someone types consent

Prisma’s docs say the CLI “can detect when it is being invoked by popular AI coding agents such as Claude Code, Gemini CLI, Qwen Code, Cursor, Aider, and Replit.” When one of them tries something like prisma migrate reset --force, “Prisma ORM blocks execution”.

It unblocks only when PRISMA_USER_CONSENT_FOR_DANGEROUS_AI_ACTION is set to “the exact text of the user’s message in which they consented”. That consent has to be yours, typed by you, after you checked which database it is.

Why rewind can’t undo it

Claude Code has /rewind (or press Esc twice). It’s great for code. Its docs: “Claude Code tracks all changes made by its file editing tools.” And: “A file that only Bash commands changed isn’t tracked and stays as it is.”

Your database isn’t a file Claude edited. It lives on a server. Rewind brings the code back, not the rows. The docs also say checkpoints are “Not a replacement for version control”. They aren’t a backup either.

If your free project was already wiped, there is no Supabase backup to restore. Look for any copy you have: a local database, a test project, an old export. Then start backing up today, so this never costs you twice.

# Your connection string: Supabase dashboard → Connect (Session pooler).
# Keep these files OUTSIDE your repo: they hold your users' data.
mkdir -p ~/db-backups/$(date +%F) && cd ~/db-backups/$(date +%F)

supabase db dump --db-url "$PROD_DB_URL" -f roles.sql --role-only
supabase db dump --db-url "$PROD_DB_URL" -f schema.sql
supabase db dump --db-url "$PROD_DB_URL" -f data.sql --use-copy --data-only

# Plain Postgres (any host) works too:
pg_dump "$PROD_DB_URL" -Fc -f ~/db-backups/$(date +%F).dump

Make it a habit

• Run it every week, and before every big change your agent makes to the database.
• Keep the files outside your project folder and never commit them. They hold your users’ data.
• Keep a copy off your laptop too: Supabase says “maintain off-site backups”.

{
  "permissions": {
    "deny": [
      "Bash(prisma migrate reset *)",
      "Bash(prisma db push *)",
      "Bash(supabase db reset *)",
      "Bash(npx prisma migrate reset *)",
      "Bash(npx prisma db push *)",
      "Bash(npx supabase db reset *)"
    ]
  }
}

Using Drizzle? Add "Bash(drizzle-kit push *)" and "Bash(npx drizzle-kit push *)" too.

What bumpers can’t stop

Claude Code’s docs are honest about this. A deny rule “covers the invocation Claude usually produces and isn’t a security boundary around the program.” The same command written another way, like bash -c '…' or a full path, isn’t matched.

So the bumpers stop the usual roll, not every trick shot. That’s why the practice lane comes first. For a harder wall, the same docs point to sandboxing and a PreToolUse hook that checks the full command.

Never let it answer for you

Add one line to your project instructions (CLAUDE.md) and say it in the chat: never answer yes to a reset, drop or “data will be lost” prompt. Stop and ask me. And never set PRISMA_USER_CONSENT_FOR_DANGEROUS_AI_ACTION: that consent is yours to type.