# Why the Prisma CLI Asks for Your Feedback

URL: https://www.prisma.io/blog/why-the-prisma-cli-asks-for-your-feedback
Published: 2025-05-15
Authors: Will Madden
Tags: orm
Description: To capture the voice of our community we’ve started prompting for feedback directly in the CLI—an unconventional choice that deserves a short explanation.

In the [Prisma ORM Manifesto](https://www.prisma.io/blog/prisma-orm-manifesto) we committed to building Prisma “in conversation with our community.” To capture the voice of our community we’ve started prompting for feedback directly in the CLI—an unconventional choice that deserves a short explanation.

## Meeting you where you work [#meeting-you-where-you-work]

Most development tasks already flow through the CLI. By surfacing the survey there, we reach you at the precise moment you experience Prisma—no emails, browser pop‑ups, or tracking pixels. The question is simply:

> How likely would you be to recommend Prisma? (0 = not at all likely, 10 = extremely likely)

One input records your rating. If you would rather not take part, press **Enter** without typing a number; the prompt will not re‑appear on that machine for at least three months. We also suppress the survey automatically in CI environments and whenever you pass the `--no-hints` flag.

## What happens to your answer [#what-happens-to-your-answer]

Every response is reviewed by engineering and product. The overall NPS trend tells us whether recent releases are moving the project in the right direction, while the optional free‑text comments highlight specific annoyances or ideas.

For example:

> “Add better SQLite support, like enums or smt”

**Result:** enum support for SQLite shipped in 6.2.0

> “Absolutely insane that you run this type of thing from CLI… I’m stunned”We will need to convert that into a docs page

**Result:** we have been polishing the rough edges of the survey prompt

## What we record—and what we do *not* [#what-we-recordand-what-we-donot]

We store the score, any comment you provide, and a random uuid. We do **not** collect your schema, queries, environment variables, or any other project data. All information is processed under the same security measures that protect our crash telemetry.

## But I don’t like it [#but-i-dont-like-it]

Participation is entirely optional. If you’d like to opt out, choose whichever method suits you best:

* When prompted, leave the input blank and press **Enter**—you will not be asked again
* Run commands with [`--no-hints`](https://www.prisma.io/docs/orm/v7/reference/prisma-cli-reference#options-1) to avoid survey prompts and other tips
* Set the [`CI` environment variable](https://github.com/watson/ci-info/blob/master/index.js#L36) to any truthy value in order to silence prompts in automated pipelines

## Closing the loop [#closing-the-loop]

Our [Manifesto](https://www.prisma.io/blog/prisma-orm-manifesto) concludes: *“If we ever fall short, call us out.”* 

The CLI survey is the shortest route from your keyboard to our roadmap. Whether you leave a triumphant “10,” a frustrated “2,” or a paragraph of suggestions, it genuinely influences what we build next.

If you have ideas for improving the CLI or the survey experience, leave a comment below, ping us on X, or join the conversation on Discord.

**Thank you for helping shape Prisma.**