Why the Prisma CLI Asks for Your Feedback

In the 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
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
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
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
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-hintsto avoid survey prompts and other tips - Set the
CIenvironment variable to any truthy value in order to silence prompts in automated pipelines
Closing the loop
Our 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.
About the author

Will leads the engineering team behind Prisma's open source ORM and guides its technical direction, with more than 15 years in software and an open source trail stretching back to 2008. He has appeared on podcasts including PodRocket to discuss ORM architecture and direction, and writes about ORM design, engineering leadership, and shipping software other engineers depend on.
Keep reading
See Your Migration History in Prisma Studio
The Prisma Studio Migrations view shows every applied Prisma Next migration as a timeline with a visual diff, the executed SQL, and a schema diff.
How One Founder Builds a Live Sports Platform Without a Database Team
How Xeito uses Prisma ORM and Prisma Postgres to ship live scoring, leagues, payments, and player workflows without a database team.
Build your next app with Prisma
Start free. Scale when you’re ready.


