prisma-cli

Run prisma migrate dev --name your_migration_name during development to create and apply a migration. For production, commit the migration files and run prisma migrate deploy, which applies pending migrations without prompts or a shadow database.

prisma db push syncs the schema directly without creating migration files or tracking history, making it suited for prototyping and MongoDB. prisma migrate dev creates versioned migration files with drift detection, which is required for team collaboration and production deployments.

Use bunx --bun before Prisma commands, such as bunx --bun prisma init or bunx --bun prisma generate. 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, obtain consent immediately before running, and pass the exact consent text via PRISMA_USER_CONSENT_FOR_DANGEROUS_AI_ACTION.

No. In current Prisma versions you must run prisma generate explicitly after schema-changing commands to refresh client output, and run prisma db seed explicitly when you need seed data after migrate dev or migrate reset.

Avoid db push in production, in team environments needing trackable changes, and whenever rollback capability matters, since it creates no migration history. Use migrate dev and migrate deploy instead for those scenarios.