James McKernan

seeing several posts suggesting @prisma had layoffs or mass departures in the last 2-3 days but not seeing any blog posts. i run prod systems on prisma products, so i'd appreciate transparency from @sorenbs on the company's state. time to migrate to @PlanetScale + @drizzleorm?

@velvet_shark @openclaw thanks for a very informative video! question: for track-a, does this recommended config line require some 3rd party install? "modelPath": "hf: ggm1-org/embeddinggemma-300m-qat-q8_0-GGUF/embeddinggemma-300m-qat-08_0. gguf"

Your @openclaw agent works perfectly for 20 minutes. Then it silently forgets your instructions and goes rogue. The fix isn't better prompts. It's understanding how memory actually works. I'm an OpenClaw maintainer. After 2+ months of daily use, I ended up with a memory system where my agent remembers decisions from weeks ago, checks its notes before acting, and picks up exactly where it left off after every restart: 0:00 The real reason your agent forgets 1:59 Quick start: 3 things that matter most 3:01 The 4 "memories" people confuse 4:52 3 failure modes: why your agent forgets 6:42 Compaction vs pruning 8:05 Prove what's loaded: /context list 10:06 What compaction actually does 13:42 Layer 1: pre-compaction memory flush 16:27 Layer 2: manual saves + /compact trick 19:12 Layer 3: the file architecture 23:22 The memory protocol for AGENTS.md 26:06 Retrieval: Track A, A+, and QMD by @tobi 31:59 Cost and cache 33:33 The complete config (copy and go) 36:35 5 things to remember

@sorenbs @DrizzleORM just so you have an example, this is what non-dodgy behavior towards user questions looks like x.com/bcherny/status…

@jamckernan @DrizzleORM Who are you with these demands and insults? 🤣

The response to our Prisma Next announcement has been phenomenal. One thing that I think is really going to be super important is the support for multiple query interfaces to coexist. And the ability for the community to experiment with new interfaces with a relatively simple extension mechanism.

@MartinJans60085 @andrii_sherman @stefanmaric_ @prisma @DrizzleORM reply to me and then block me. nice one martin. real mature. what’s wrong with all you prisma folks today? used to be so cool to engage, now its just cringe. 😬 how the mighty have fallen.

@MartinJans60085 @andrii_sherman @stefanmaric_ @prisma @DrizzleORM you come across like a sore loser

Today, we’re sharing our vision for a new foundation for Prisma ORM. It keeps the experience you love and sets the direction for a more composable, extensible, agent-ready future! We'll let the code speak for itself ✨

@sorenbs @DrizzleORM asking the @prisma ceo a question about his own product building practices is deemed an insult. this i did not expect.

@sorenbs @DrizzleORM i'm a long standing prisma user evaluating whether to trust my production systems to your next version, that's who. and it's a straightforward question you still haven't answered. if the answer were reassuring, you'd have given it 5 replies ago. your non-answer speaks volumes.

@sorenbs @DrizzleORM ok, i'll accept your terminology distinction: agentic engineering, not vibe coding, fine. now pls answer the question: what % of the prisma next was generated by agents vs written by humans? you've spent 4 replies reframing definitions instead of giving a number. worrysome.

I continue to think we have different definitions of vibe coding. I have personally adopted Simon Willisons definition (simonwillison.net/2026/Feb/23/ag…), which I feel is a very faithful interpretation of Karpathys tweet from last year: "coding where you pay no attention to the code at all". That's what non-developers are doing on platforms like Replit and Lovable. That's a very cool thing to be able to do, but it is not how we are developing Prisma. What we are doing is very aligned with what Simon describes as Agentic Engineering, hence my use of that term. This is obviously a rapidly evolving field, and we are learning along the way. We are going to write about our experience for anybody who is interested.

@sorenbs @DrizzleORM hmm, if you don't know what vibe coded means, should i be trusting my production systems to you?? vide coded = "prompted into existence" vs someone actually writing coded by hand. can't believe i had to write that out to you.

@jamckernan @DrizzleORM I don’t know what you mean by vibe coded, so I tried to answer as best as I can. We will write up our process when we get a moment. I believe it will be interesting for many.

@sorenbs @DrizzleORM i care deeply about protecting my production systems. it is my job. i asked a simple clarification question and you went all pete hegseth on me. so, i'll ask again: even with your sophisticated process, what % is vibe coded?

That’s a very dismissive attitude, and I’ll invite you to follow the development in the repo to see for yourself. We should probably write about this. All code is reviewed manually and tested thoroughly. We have structured the entire repository such that agents can work on small self-contained pieces that can be tested in isolation. It is our belief that most software will be written this way in the near future.

@sorenbs @DrizzleORM i am eager to see where this goes!

@jamckernan @DrizzleORM We are keenly aware of community feedback. That’s why we are making Prisma Next :-) Do you have any specific feedback?

@sorenbs @DrizzleORM "principled Agentic Engineering process"... fancy way of saying it is vibe coded... 🙁 feedback: i will not run my production stuff on vibe coded stuff. too risky. some stuff there and here is ok, but if the whole thing is vibe coded, then nope. what % is hand coded vs vibe?

@jamckernan @DrizzleORM Prisma Next is developed under a principled Agentic Engineering process. We have learned a lot along the way and the text artifacts in the repository should be interesting to study.

someone please explain what @davemorin has done to be associated with @openclaw?? seriously, this guy will leech on to anything to get visibility.

@lassvestergaard @prisma @DrizzleORM @PlanetScale not saying they are not awesome, they are. but they need to wake up.

@jamckernan @prisma @DrizzleORM @PlanetScale Prisma is not cooked bro, both drizzle and Prisma is awesome 😭 I use both every day

The whole @DrizzleORM core team is joining @PlanetScale. Regardless of the discourse, this is a big win for any startup.💚

@prisma u realize u're making your big announcement the same say as apple is making theirs??? whoever is running launch planning for y'all needs to get demoted.

soon 🤫

@DrizzleORM don't disagree. but then how do you track market growth. if the metric is inflated, it is inflated for all. that still makes it a decent rubric, no?

npm downloads is both unstable and now extremely inflated metric, we no longer pay attention to it

@prisma orm or other products? "prisma" is a placeholder at this point of everything that you do, or are you saying the whole thing is going to change?

Prisma is about to change drastically in 2026 Any guesses what’s coming? 👀

@nikolasburk @schickling that's cool. which voice input tool are you using?

I've been using voice input consistently for chatting with my agents over the past weeks (thanks @schickling for nudging me), and can't imagine going back. Surprised that 65% of respondents so far to my "State of Agentic Coders" survey say they never use it...