prisma-cli

Run prisma migrate dev --name your_migration_name to create and apply a migration during development. For production, commit the migration files and apply them with prisma migrate deploy, which never generates new migrations.

db push syncs the schema directly without creating migration files or tracking history, making it suited for prototyping and MongoDB. migrate dev creates versioned migration files with drift detection and rollback capability, suited for team development.

Yes, but you must run it with bunx --bun so Prisma uses the Bun runtime. Without the --bun flag, the CLI falls back to Node.js because of its shebang.

Prisma detects AI agent environments and blocks destructive commands like migrate reset and db push --force-reset until the user gives explicit consent. The agent must explain the data-loss impact and obtain consent immediately before running the command.

Configure a seed command in prisma.config.ts under migrations.seed, such as tsx prisma/seed.ts, then run prisma db seed explicitly. Current Prisma versions do not run seeds automatically after migrate dev or migrate reset.

Avoid db push in production, in team environments needing trackable changes, and when you need rollback capability. Use migrate dev and migrate deploy instead, since db push creates no migration history.