prisma-cli

Run prisma migrate dev --name your_migration_name to create and apply a migration from 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 tracking history, making it faster for prototyping. migrate dev creates versioned migration files with rollback capability and drift detection, making it the right choice for team development and production paths.

Yes, but you must add the --bun flag so Prisma runs with the Bun runtime instead of falling back to Node.js due to the CLI shebang. Use bunx --bun prisma init and bunx --bun prisma generate.

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 or shadow databases, making it safe for CI/CD pipelines. Check prisma migrate status first, and never use migrate dev in production.

Avoid db push in production, in team collaboration requiring trackable changes, and when you need rollback capability, since it creates no migration history. Use migrate dev and migrate deploy instead for those scenarios.