prisma-cli

Run prisma migrate dev with an optional --name flag to create and apply a migration from your schema changes. It uses a shadow database for drift detection, and you should run prisma generate explicitly afterward when you need refreshed client output.

db push syncs the schema directly without creating migration files or history, making it suited for prototyping and MongoDB. migrate dev creates tracked migration files with rollback capability and is the correct choice for team development and production-bound changes.

Use bunx --bun before the command, for example bunx --bun prisma generate. Without the --bun flag, the CLI falls back to Node.js because of its shebang, which can cause runtime mismatches in Bun projects.

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, obtain consent immediately before running, and pass the exact consent text via PRISMA_USER_CONSENT_FOR_DANGEROUS_AI_ACTION.

Use prisma migrate deploy, which applies pending migrations without prompts, drift detection, or a shadow database, making it safe for CI/CD pipelines. Run prisma migrate status first to verify pending migrations, and never use migrate dev in production.

No. In current Prisma versions you must run prisma generate and prisma db seed explicitly after migrate dev or migrate reset when you need refreshed client output or seed data. The seed script itself is configured in prisma.config.ts.