Prisma ORM 8 is here.Read the docs

Environment variables

The environment variables the Prisma CLI reads, what each one does, and the release that added it.

The prisma command reads these environment variables. Set them in your shell profile or in your CI configuration. For one command, put the variable in front of it, as in this contract emit run:

Terminal
PRISMA_DISABLE_TELEMETRY=1 npx prisma contract emit

In PowerShell, set it for the session:

PowerShell
$env:PRISMA_DISABLE_TELEMETRY = "1"
npx prisma contract emit

The CLI does not read .env files or DATABASE_URL itself. Your prisma.config.ts does that, and the one orm init writes already loads .env; see Configuration.

"Since" is the first prisma release that reads the variable.

VariableWhat it doesSince
PRISMA_DISABLE_TELEMETRYSet to 1 to turn off anonymous CLI telemetry. Empty, 0, and false leave it on.8.0.0-rc.1
DO_NOT_TRACKSet to 1 to turn off telemetry. Other values do nothing.8.0.0-rc.1
PRISMA_DEBUGSet to 1 to print the CLI's debug output to stderr.8.0.0-rc.1
PRISMA_SKILLS_CHECKSet to 0 to silence the notice that your project's agent skills are out of date.8.0.0-rc.9
PRISMA_SERVICE_TOKENA service token for a Prisma Platform workspace, created in the Prisma Console. Only the Platform commands such as auth, project, and deploy use it, in place of a browser login, even if you are also logged in.8.0.0-rc.1
PRISMA_WORKSPACE_IDThe ID of the workspace the service token belongs to, from the workspace's settings in the Prisma Console. Set it alongside the token.8.0.0-rc.1
NO_COLORSet to any value to turn off colored output. The --color and --no-color flags override it.8.0.0-rc.1
CISet to any value except false to mark the run as CI: no telemetry, no skills notice, and no interactive prompts. CI=false forces the non-CI behavior even when a CI system set it.8.0.0-rc.1

Agent skills are files in your project, in .claude/skills and similar folders, that teach AI coding agents about Prisma. Silencing the notice does not update them; prisma skills sync does.

You rarely need to set CI yourself: the CLI also detects the variables that CI providers such as GitHub Actions and GitLab CI set.