How I AI - Guillermo Rauch: Vercel CEO on how v0 hit 3,200 PRs merged per day (and lets anyone ship)

Episode Date: February 4, 2026

Guillermo Rauch, the CEO of Vercel, demonstrates how v0 has evolved from a simple prototyping tool to a complete development environment that supports the entire Git workflow. Guillermo shows how Vercel built skills.sh—a viral marketplace with over 34,000 community-submitted skills—using v0, and how the tool enables non-technical team members to contribute production-ready code changes. He walks through creating branches, implementing features, previewing changes, and submitting pull requests, all within v0.What you’ll learn:How v0’s new Git workflow integration enables anyone to contribute production-ready code changesWhy skills.sh became a viral hub for AI skills, with 500 new submissions per hourHow to implement features in v0 that consider production concerns like abuse prevention and rate limitingThe benefits of branch previews for testing changes in a production-like environment before mergingHow v0 eliminates development environment setup challenges for non-technical team membersWhy the “terminal core” design aesthetic became central to skills.sh’s interfaceHow Vercel uses v0 internally to democratize code contributions across teamsThe future of AI at Vercel, including upcoming tools for text-to-SVG and video generation—In this episode, we cover:(00:00) Introduction(01:22) Overview of skills.sh(04:40) Demonstration of v0’s GitHub integration and branch creation(06:40) Exploring the v0 development environment(09:05)  Building a rating system feature for skills.sh(11:18) Testing the new feature in the preview environment(13:20) Creating a pull request and deploying to a preview environment(15:25) How Vercel is using v0 internally for production work(17:48) Organizational adoption and cultural impact(22:04) Favorite non-coding AI use cases(25:17) AI-powered chess game built with v0(27:57) Teaching kids about coding with AI(31:44) Troubleshooting techniques when AI gets stuck(34:43) Final thoughts and audience Q&A—Tools referenced:• v0: https://v0.dev/• Skills by Vercel: https://skills.sh/vercel• Vercel: https://vercel.com/• GitHub: https://github.com/• Nano Banana: https://gemini.google/overview/image-generation/• Vestaboard: https://vestaboard.com/—Other references:• v0 Chess Match: https://v0-chess-match.app/• React Native: https://reactnative.dev/—Where to find Guillermo Rauch:LinkedIn: linkedin.com/in/rauchgX: https://twitter.com/rauchg—Where to find Claire Vo:ChatPRD: https://www.chatprd.ai/Website: https://clairevo.com/LinkedIn: https://www.linkedin.com/in/clairevo/X: https://x.com/clairevo—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [e-mail].

I'll say one thing about vibe coding. It's really easy to go from zero to one. I think we've all seen the demos of I promise something and it's cool. I think what's harder is to iterate on a project at scale and to deploy changes safely. Every marketer of Ressel wants to change this page at some point. And the old way was one of two ways. One is what I called, you had a petition to the government. You had to go to engineers and say, engineers, can you please add a logo over here or whatnot? or pray that the CMS was perfectly wired up for any ambition or dream or idea you had.

So now they can just open this page in V-Zero and prompt anything that they want. It reduces the friction of getting something live really, really low. The humiliation ritual of prioritization goes away. And you can actually focus your time on defending the merits of an idea on the actual idea as opposed to the hypothesis of the idea that then has to be implemented. And so I think it changes the speed of companies in a really significant way. So this is truly a first-time vibe podcast that we're doing together. And I wanted to introduce myself.

I'm Claire Vaux. I'm a product leader and obsessed with AI. And I have a podcast, Howie AI, where I teach people how to build better with all these new tools, including ones that we're going to see today. And I'm really excited to have you here, G, first. we're just going to get to the thing that everybody's wondering about. What is your most favorite feature that you released this week on V0? Well, I'll tell you, the hottest thing in AI today is skills.

And when it's excited about the fact that we can now augment agents and AI applications and agentic engineering with skills, like skills that the model doesn't yet have. And so we launched Skills. lot of S.H. And the beautiful thing about what we'll show you today is that VZero can seriously go from prototype all the way to production. So we're able to conceive changes to things like Skills. Slot S.H. I'm going to show you really quickly. Skills. Slot S.H is a new, you can think of it as like NPM. It's a hub, an open ecosystem of skills. And it's pretty dramatic what's happening to this site. So you can see that we now have 34,000 skills submitted by the

the community. And this website has gone viral all over the internet. It's hosted on B-Sel, but the most exciting part to me is that it was conceived in B-Zero. I have a quick question for the audience. How many of you have installed a skill in the last week? Oh, wow. Okay, a lot of people. Skill-pilled. How many of you have the top three installed? Actually, top five. It's very heavy at the top, right? It's like, these are ripping. Oh, no, I have top seven. Okay. Yeah. I have the top seven installed right now. This is a really great resource.

So for folks that are maybe watching this later or haven't been familiar with skills, Skills is now this standard that a lot of these agentic frameworks are using to help you repurpose and reuse best practices, step by step flows. And so, for example, I use this Remotion Best Practices one to let me import components and regularly create videos really, really quickly. And I would not have been able to do this without the expertise that's been packaged in these best practices that were installed with one line using skills.Sh. I think it's also worth noting maybe to peel the covers of how Versel builds products. Yep.

Skills.com. Sage was a thing that was just conceived at the moment of inspiration. We started promising, hey, wouldn't it be cool if this thing took shape? We discussed, for example, what it should look like. we've been calling this style terminal core because it looks a little bit like, this is my contribution to the project. I was like, hey, it wouldn't be cool if we make the top of the website look like a terminal. And so the process itself of building this was very much prompt-driven, L-Say,

like chatting in Slack and saying, hey, wouldn't be nice if we had a hub for this, which is very iterated, very collaborative between the team members at Versil. And what's really cool about this, again, is it's really fast. So it takes advantage of all of the Versailles infrastructure primitives, even though it has 35,000 of the skills, like if I start like heartacore scrolling this and then pick a random one, all right, Swift, Taylor Swift. You're going to see like the patient transitions are, it's probably Swift you. I, okay.

But all the patient decisions are instant production grade. You needed to scale. There were going to be a lot of eyes on this thing. Okay. So I think we want to get to our first workflow for how AI. And you just want to show us how you. either develop this or how you and the team improve this over time using the tool. I'll say one thing about VipeCoding.

It's really easy to go from zero to one. I think we've all seen the demos of I promise something and it's cool. And I think what's harder is to iterate on a project at scale and to deploy changes safely. In the case of how we work on Vosel products, we always work on branches and we take advantage of branch previews. And then we code review and then we merge. them. So we're basically going to be showing you today is how we brought those ideas of

hard core heavy duty production grade engineering to VZER itself. So I'm here and finding that same project that you just saw. Skills out of Sage, which is piped into is basically backed by Git.

The engineer who built this pushed some code three hours ago. And you have this new button within VZER, which is new branch. So what this is showing you is that V0 is making the Git flow of creating branches at first class citizen of the product. So I'm going to create a branch. And basically, this is going to give me the same sort of like chat experience you're used to. But notice here at the top, I got this beautiful new convention of project slash branch. Right. So I have the V0

slash Rouch G Branch. And here within the preview, you're going to notice that just like if you had cloned the project to your local device, we both have a full, full-scale BS code editor as well as the real project

running within B-Zero. One thing I want to pause and notice because I just have a laser eye for product is I love that you use the convention that all of us with engineering teams use on our Git branches, which is who's the contributor slash what's the future. And so what I think this is really interesting. You know, we're going to talk about how you actually use these tools to build. But I also think there's a flip side of how you design great AI products and agentic products.

And I still like the small design tweaks that make something like a V0 feel like a collaborative teammate on your pool. So for all the engineers out there, I noticed that little convention. So and what you're going to see in the design philosophy of the product is that we really want to embed those little details of what makes a real engineering workflow come to life. But in a really easy way, right? Like at the end of the day, I didn't have to go to a terminal or a boot up GitHub desktop and branch manually. Like it's the Stone Age. Just press the button and now I have a branch running. So the main idea here is that within this review, I have the full.

Skills.S.H project running. It downloaded dependencies. It installed the exact versions of Next.js and every dependency within the project. I have it all running here. I have it obviously within a staging or dev sort of environment. And now, you know, I could navigate it like I could navigate the production website. I could explore it. I could, you know, use all the capabilities that VZER brings to the table.

But I figured, let's actually build a feature that we could ship the product. Yeah, and one thing I want to pause on what you, I think, lost over a little bit, which is the fact that you had this VS code instance, the fact that you have all your dependencies installed, the fact that this is running both with code and a preview, for anybody who's less technical out there and maybe a lot of your users that are using V0.com are less technical. This, even like downloading VS code, getting your local environment set up, like I spent this morning with my designer installing homebrew, like it just wasn't on her laptop. It's nightmare feel. It's nightmare. And so if you're trying to step from this vibe coding prototype in web experience into feeling more like a software engineer without having to have Claire handholds you through like brew install, this gets you like halfway there. And so I think there's also this learning aspect of it. I want to make sure people don't miss.

But let's get into building something on this. So another part of our product development process is really listening to community and listening to customers. So people have been asking for a lot of different tools so that we could guide them towards knowing if a skill is high quality, vetted, verified, because there's so many skills. Last we checked, there were 500 skills being added every hour. And so one of the ideas that we came up with is like, could we add a rating system?

So let's add a five-star based rating system for the skill. put it on the sidebar. Be mindful. So I'll also give you a little bit of my real-time consciousness on. If I were talking to an engineer and say, like, what could go wrong if we accept ratings from the Internet? What are the things that can go wrong if you accept ratings from the Internet?

It's abuse. So let's say, let's still be zero. Be mindful that we should rate limit or prevent abuse on the scores that we receive. And again, for me, it's all about thinking from a lot. production readiness point of view when I think about the new V0 and make it make sense within the style of this skills website. What I love about what you're showing us is you have this very, very high sophistication

prompt here, which is make it make sense. So we have three incomplete sentences on a production app serving thousands, millions of people. That's right. So let's fire it off. And while you do this, one of the things, I want to just call out that I think, you know, why this feature is maybe important right now is I don't know if you've heard there's like this crustacean crawling all over everybody's MacBook minis. And skills can be a prompt injecting vector for things. And so as you're trying to make sure that this becomes the centralized hub for discovering skills, which I think it's starting to be, it is upon you to kind of make sure that the qualities there at least you have the right thing, right things in place to people to make good decisions.

And also maybe to follow with your analogy, this is a little bit like we're vibe. coding on top, GitHub.com or NPMJS.com. It's like a really, really big deal. All right. So I was going to walk you through what V-0 is doing, which, of course, if you've used V-ZO before, everyone does the whole, like, talk over to thinking trays because agents are not the fastest. But I do want to point out a few things that are really important. So V-Zero is all about leveraging the integration and marketplace capabilities of herself. So in this case, it knows what the data source is of this project, right? We're storing data in Redis by Appstash.

Obviously, it's going to go through the whole file system. It's going to try to interpret my requirements. This is already, like, really nice to see that it's not inventing a new way to store the data. Like, it's actually paying attention to the data that I use. And so we'll take a look at, again, here. Like, it actually gave me something that meets my requirements, right? Like, it fits within the design style. I can submit a rating.

It stores the rating. So I have now my five-star one rating. I guess I'm gonna- It's terminal core. It's quick core for real. Let's refresh the page to see that persistence actually works. Beautiful. There's a tiny bit of layout shift that triggers my neurosis.

So we'll tell it, hey, when we don't have data, make sure there's no layout shift. By the way, for those of you that are like less neurotic, I guess. So it bothered me that when we refreshed the page, when we didn't have data, like, jittered the sidebar a little bit. So we're just going to have these zero. So while we're jibber jabbering while it's thinking, which I have to get very good at as a podcast. So I will call out that I have observed a Versel internal hackathon. And I have seen this man screenshot like rounded corners that are not right and just put them in the chat with like a question mark.

And so I, it's, yeah, it speaks to my, my very attention to detail heart that you saw, you saw that. Let's see. Did it work? Yeah, no, I'm fairly satisfied. Like the, yeah. Yeah. The skeleton was stable. Yeah, yeah, yeah.

Zero layoff shift. So let's continue with the, we talked about this hardcore engineering workload. Like if, if we were making a change like this on skills out of age, again, receiving hundreds of skills per hour. with lots of visitors. We first want to make sure that things work, right? And right now, you can think of this as a very capable dev environment. We're booting up the NextJAS dev server in a virtual machine. It's basically very true to the actual end results.

In fact, thank you to the NextJS engineers who sweated all the details of mirroring to the best of their ability, the dev environment and the production environment. But there is another layer of assurance that we can get, right? which is, so if you're more familiar with the GitHub world, the GitHub side of things, you know that when you push a new PR to GitHub, this beautiful Versel bot comes to sort of save the day, right? You know that it builds what you're changing and then you previews it. Not only that, but notice that VZero really cool, because VZero is making me look so good here. Because I haven't written a PR description in like 25 years, 84 years.

So VZero produced the PR, described it. And then the magic of herself is coming in, right? So it's giving me that preview. So I'm going to open it here. I'm going to say visit preview. I'm just, again, I'm going to be a software engineer for a second. Can we appreciate how quickly that preview branch deployed? Well, don't trigger me because it can be 10 times quicker.

But yeah, I'm proud of it. Question mark, explain. Now I have a production-like environment. So when you see this URL ending on dot-Vorcel.jsH, dot-viceh is our enterprise Vercell environment. That's why I had the 17 steps of logging in. But this is basically running on the production grade CDN, on the production-grade rendering infrastructure, hosting infrastructure, etc.

So now when I'm seeing that rating there, I have pretty good confidence. I was like, yeah, this is shipable. Okay. So I have to ask a couple questions about the, you know, know, inside the house view of this, is this how you all are shipping code? Or is this a big chunk of how you're shipping code to this? Is it 100%? How are you actually using this for production? So it's really interesting. When we cook on a project or a product internally, we hold ourselves to the same sort of high bar as if you had launched a product externally because you

want to make sure that people are actually adopting it, right? And so before we started chatting, and I'm going to give you a glimpse of, again, the behind the scenes of B. We've talked a lot publicly about our data analyst agent B0. Yes, we're very creative with names. We take the first initial and we add a zero. So this is our data AI powered assistant. And I was actually asking it. I said, V0.

This is me, by the way. Tell me about PR smirk with B0 in the recent weeks. Tell me about it's. growth. So again, PR submerged with DZero is a totally novel thing. And DZero cooked. Thank you, DZO. He said, PR's merged via DZO have seen explosive growth in the last week.

Wow, explosive growth. I have to appreciate whoever prompt managed this one because it did not put the explosion of OGE in there, which I think would also tricker G. We should. Yeah. Tree warning. Starting from near zero in early January, the feature hit 3,200. 100 PRs merge per day by January 28, 29, which is basically today, an extraordinary 100x.

The bots, the AIs do like to like, like, yeah, like sweet to talk us, but it's, it's pretty amazing. So this is in very, very, very early preview, right? Like we're just letting people in. But, I mean, this is just such a beautiful workflow. I mean, imagine triggering a task like this from your phone, from Slack, from B0, that app. Another convenience that we're adding is that you can take a GitHub repo like this and I can go to the homepage and then I can paste it. And so now I could import something that I

already have and create a chat from it. So anytime I have an idea for a real world project and product that Rasell has in production, I can now prompt. So I estimate that this is going to change fundamentally how we work, right? It's also very visual in nature. which is really cool. Obviously, there's a lot of ways of, like, getting preview, getting changes made by agents today out there in the world. Everyone's very excited about what AI can do. But this is actually showing me the actual results and, like, things that are going to happen. So I grade is really high for the kind of products that we build at Roussel,

and I expect this to continue to have a lot of traction. So I have to ask you sort of operationally, how do you imagine companies do this? And one of the things that I'm thinking is I was chatting with Caroline, who interrupted you all and said we're going to start the podcast. And she said last night, I was prepping for this demo and I V0 coded something. And somebody saw it and was like, well, that's a good idea. You should just merge it and ship it. Like, do you imagine or inside the company, who's shipping code?

How are you enabling that as a CEO? How does the culture support it? So how does it not? Until now, everyone could cook, right? everyone could create a prototype, a new design, a suggestion. In fact, a moment of vulnerability, because I haven't really even opened this in a while, but like, let's see if I have,

I probably created a bunch of things that I've been suggesting to the teams that we could look at, right? Ignored this one for a second, but... So any time I have an idea on how to improve the product, I nowadays create a V-0. Now, the difference is that until I had this mechanism to hand it off as a support, request to the engineering team, then I was kind of like playing in La La Land. I was like in out

there in this like prototype world. And now we have a common foundation and a common substrate so that if you have an idea whether you work in marketing, like marketers always want to change the website. Like imagine like go to Vurcel.com. I'll see a page that is actually quite fun at Vurzel. So our enterprise page. Every marketer of Vursell wants to change this page at some point, right? And the old way was one of two ways. One is what I called, you had a petition to the government. You had to go to engineers and say, engineers, please, can you please add a logo over here or whatnot? Or pray that the CMS was perfectly wired up for any ambition or dream or idea you had. So now they can just open this page in V0 and prompt

anything that they want, but it would be somewhat irresponsible to just ship it, right? So with the Git workflow and opening a PR and being able to preview it, we can all build confidence that it's going to be a good change, roll it back if needed. And again, this is a website that's pretty large. What I think is fun about this from an org perspective is it reduces the friction of getting something live really, really low, right? And like the humiliation ritual of prioritization goes away. And you can actually focus your time, on defending the merits of an idea on the actual idea as opposed to the hypothesis of the idea

that then has to be implemented. And so I think it changes the speed of companies in a really significant way. And you worked, I mean, to say it at least, at launch darkly. Yeah. And you know that a true production grade release process involves things like feature flags and experiments

and things need to be measured. And there is events that are critical to report from these product surfaces. And so this is also where I see the skills that we can add to V0 and that you can contribute yourself to play a very important role. Because sometimes, you know, like we're all operating on this like websites and pixels and whatnot. And we say like, it seems easy. How risky could it be to move this button 20 pixels to the right?

And so I think we can make vibe coding scale to that kind of rigor that exists within enterprises and companies at scale. Well, and if we're being honest, on that enterprise, it's not. going to be moving a button two pixels. It's going to be switching the emphasis. I know this, because I spent my life in enterprise, switching the emphasis between contact sales and view the product. There's going to be a perpetual debate, which one's the primary call to action, which is the secondary. Okay, I, so we've shown a new V0, import GitHub, which I think is really great. Do a poll request, copy and paste your GitHub URL in to import it, actually push to

production, make friends with your engineers, three sentence prompting, no more than that. I want to go to quick, because we want to keep this tight. I want to go to a quick lightning round with you and ask you a couple different AI questions. So what is your favorite non? I mean, everything's a coding use case, I'm sure with you. But what is your favorite non coding use case of AI? Well, I'm conflicted. My mind immediately went to image generation because I use.

So we built up Bangor Playgrounds. I don't want to share a screen again. I want to take it from you. This is, oh, no, I was just going to say image generation is how I got this pretty, pretty background. B0-Nanobanana Pro. Nrsella app. Nano banana. So what's really cool that's happening at Rissell today is that we're building so many of our own internal tools and agents.

And so we're building our own design tools. Like, for example, to create new images, we created a playground for nanobanana. And I use that a lot. So I use it to make memes. Guilty is charged. But I also use it when I want a percent in for. information in really cool ways when I tweet, when I sometimes have to make a present my vision in a way that's more like on the image side of things. I combine it a lot with V0 because

nano banana is really good at like, again, letting me fire off 20 generations in parallel and then pick the one that I actually like and then I toss it into V0 and then I actually get more fidelity of what I want to implement. So image generation is a big one. But also I'm very excited of video generation. We're going to be dropping something I don't want to say. Spoil it too much. We're going to be dropping something on the video side as well. But yeah, all AI is, I also kick off a lot of research tasks, like long Verizon research tasks. Yeah.

So one of the things I want to call out from a nanobanana perspective of our podcast is I've used nanobanana to turn every conversation. I think we're now at 118 workflows. Every AI workflow that we talk about on the podcast gets its own pretty consistent nanobanana infographic. And so I just think there's just such undervalued use cases in both image and video gen.

And I'm about to take this and turn them all into little mini videos. We also created a really awesome. I don't know if we've written about it yet. We're published on the blog post. We have an OG image, like an open graph card, Twitter card generator that we use internally.

That combines more traditional rendering techniques, but also image generation. So a bottleneck in our team was sometimes literally like, can we get that social card to get the announcement through the door. And so now we've also sort of automated and agentified that. Every day we're basically asking ourselves, how can we build an agent that takes over a task

that we were previously given to a person? And typically the person that was working on that task is that the one creating the agent. So something we said at the beginning is, we won't be zero to be really awesome for you all to create agents, not just traditional web applications. So that's basically the run up with the product. So I have to say my favorite, so that's your favorite use case.

My favorite use case of your use of V0, which I don't know if you're prepared for me to have this much knowledge about what you vibe code, is your agent to agent chess game. My kids are obsessed with this. They think it's because they got the AI chess board. Yeah, yeah. And now they're like playing chess at various levels. By the way, I learn a lot. So it was really cool. like during the holidays, I'm kind of a visual person.

So the chess, I think, has been done before, but I imagined this sort of, imagine like ESPN is broadcasting a final of a chess match, and they're going over the shoulder of each player and showing the chessboard, obviously, in 3D. And so I figured it could be zero generate 3D code, right? Could it render with 3JS and things like that a live chess match? and could I have two AIs battle it out? And so you could open it.

So the zero dash chess dash match that Rosela at app. And the other thing, the other thing, I wonder if I am SEOed or not. You were number one. Good job. Yes. A little terminal core over here. So terminal core, of course. But so what I did is I started streaming the thinking tokens of the models.

apologies to Google in advance. We're using a very old model of theirs that is really cheap, but they're losing $2,2005. At least they got five in. So you can see the thinking tokens of the models. This is combining all of the Vercel AI infrastructure. It's using a workflow so the game could run forever. The game could literally run forever or until I run under tokens.

AI Gateway. AI Gateway, of course, because we can change models. It's like we could see like Brock versus, you know, whatever, what dropped this week, when three max thinking. But also, I learned chess incidentally because not from this guy. This guys are kind of dumb. But you can see how it thinks through what piece to move. And it says, oh, no, because if I move it there, I'm going to get F.

So I need to do this. So this is a fun to be zero created during the holidays. Yeah, so I need a kid core version of this. I also want to see how much these models are. spending to beat and lose. Well, that's a beautiful thing about the AI gateway is that we kind of report, you know, for this prompt, how much it costs you with this model, et cetera. But see, so this is GPD open source, which is actually pretty decent and pretty cheap.

So great. And then so on this talk, so that's my kids favorite, your V0. I don't know if they have a favorite. It's popular with kids. I also got another parent, reshaping me and say, like, oh, this really inspired us and we're going to use V0 together to create. create more things. My kids, a DAU on V0, don't worry about it. So this is my second question, which is, what is the last thing you built with your kids? That was really fun. So the other

day, I brought them all to the office. And what we started vibe coding is, so now we want to do things that are more like physical AI. Like bring AI to the real world. I think it's the next frontier. And so at the office, we have a thing called Vesta board, which is a board where you can basically render things in the real world. And I think I really broke. their brains that day. Not all of them because I brought four of them and one was on his iPad, not paying attention. It was almost like bringing them

to Sunday school for what it's worth. But two of them were like, holy crap, you can type in code and then you can change the real world. So I kind of taught them the concept of an API. And yeah, all vibe coded and I took one of the nannies too and she was mind-blown. I didn't have to teach everyone

how to vibe code. That is, you and I are like twin stars here because, well, You have the Vesta board, which is pretty big. I have this tiny, like, 32 by 32 pixel fake little mini computer that my kids and I are, like, vibe coding of little screens on and little games on. So I completely agree. Take it off the screen for many reasons if you have kids. Yeah. Put it in the real world.

Yeah, yeah. And you can do some fun stuff and blow their mind. They deal like sending a packet and responding to it. And the beautiful thing about VZero and things like this is like you're literally speaking English to the computer. So I think if you can teach them that they can explain. express their thoughts and desires, then they can make anything happen. Okay, important question. Are you teaching your kids to type? That's a tough one because I was, when I grew up in Argentina, my dad got me this soccer

game. He tricked me. I thought, oh, he's getting me FIFA or something cool. No, he got me a soccer typing game. So to score, I had to type really fast. And that's how I learned to type really fast. But nowadays, like, they're kind of getting really into the speech to text thing. I need to find that hack. We're like, oh, I got you, Roblox. And it's not. It's just a type of game. So I, I'm tricking my youngest right now. We have a switch. And I really don't play Ocarina of Time for people that were born when that game came out a million years ago. And the only reason I let him play it is it's like 99% just reading. Nice. And so I'm like, you can play this very slow pace game. It's a game. It's really just going NPC to NPC and reading.

I really like that. So we played a game like this when my kids during the holiday break. It was basically like a puzzle math game that looked like a game. And that inspired so, okay, good and bad. The good was, the game was like really educational. The bad was like it was like ad-ridden brain rot slop. And so it was like, okay, huge opportunity

for someone to create a game platform. You can combine all of this models, you can do image generation for the assets. We're about to drop something insanely cool. Text to SVG. There's models that now produce really, really high quality. We're going to

share recraft models through the Versailles AI Gateway. So you can create assets that are beautiful, game ready, scalable in high DPI screens, whatever, iPad. And so I really, I see the future of really high quality content at our fingertips and getting to hold this slop. Yeah, well, you know, my, my feature roadmap releases are not as confidential as yours. And so I am in the back of my mind working on like Ma'Claire's do. for crack little hackers. Nice. So maybe someday and deployed on, obviously, Versal.

Okay, last question. Do you, when you're frustrated, prompt AI, the same way I have seen you prompt in Zoom chat, which is explain. How do you, how do you, how do you, yeah, question mark? Like, what do you do when it's not giving you what you want? So I do think that what we're dropping now is going to help you so much for the moments where, I mean, let's be real. You can get stuck.

with AI, right? But now that you can essentially have this full, like, let's call it Escape Hatch, right? Like, you can, if you want, you can clone the repo and keep cooking on your local machine or if you need someone else to help you. This is fundamentally a collaborative medium. That's the thing that GitHub unlocked for the world, collaboration between engineers, designers, marketers. And so I foresee that a lot less people are going to get stuck, frankly. The models also keep getting smarter. Skills is going to help you a lot as well. So I'll give you an example. We are always adding new frameworks and new capabilities and X-ChS is getting more powerful than the AISDK. Now that we have skills for those that we're going to preload into V0,

the model itself is not going to get it stuck as easily because now it has more resources to figure out how to solve that problem. Another thing that I've done, it actually used it for this project. So there's a lot of subtleties about this 3D thing that I didn't know anything about 3D. So whenever I would get stuck, I would ask other models. I think it was something about the way that, and kudos to the awesome soul, the gentleman that open source the 3D. So I got it from a sketch fab. And he didn't design this for creating a game or anything like that.

So all of the pieces were stuck together. It was almost like you had 3D printed it and the pieces were stuck together with the board. And so obviously I want that sweet animation that when the model decides it moves the piece, right? And so I had to ask a lot of questions to other models about, hey, teach me what's going on with this 3D thing. How do I reason about it? And then I would copy what another model tells me and I would toss it into V-Zero. So another thing that you can do when you get stuck is she can't see it here because it's only for me. But there's a debug button.

And what the debug button says, I asked B0, hey, give me debugging tools so that I can visualize the mesh of the 3D model. I can visualize, I can turn the textures on and off. And so the AI itself can help itself and can give you tools to debug problems, which is kind of meta. But try it, try it and it's going to work well for you. Okay. So you ask an expert, which is another model. Let me find out the right question to ask. Well, this has been very fun.

Thank you for showing us a little bit behind the curtain of how you use V0, all the new stuff, some of the ways you use in your personal life and fun projects. We love to see it. So you have this new VZero. You have this room full of people. What do you want from them? What can they do for you? I mean, get busy shipping.

So try it out. Give us feedback. We will fix it as very, very fast because we're going to be eating our own dog food. And yeah, share the things that you built. with V-Zero. Oh, we have a question back here. Oh, I love it. So I had a question.

Thank you for sharing, like, the feedback process, how you loop in terms of, like, from ideation to, like, production. Like, during that process, do you do any, like, product market fit? How do you validate that what you're trying to build is actually, like, useful or impactful for, like, your ecosystem? Yeah. Super hot off the presses, new sort of mental model that we've been using internally. There's a customer zero and a customer one.

Customer Zero, we like to be ourselves. It's like the Rick Rubin, the confidence in our ability to know what's good, whatever. Like, we like our taste. We've been around the block for a while. We have ideas of products that we would like to see out there in the universe. But customer one is also really important. Like a closed design partner, Claire V-Zero. Oh.

Claire V-Zero. And Claire and our CPO are constantly texting. We're on a text chain. She texts bug reports. She texts things she needs. So having that group of design partners, enterprise companies, individuals, community members, people that slide into my XDMs. So you always wanted that pressure test of the world.

And for skills, it was that, you know, people telling us, hey, like, why does Opus 4.5 kind of know the latest next year is, but not really? And how can we embed your best practices? So that was kind of like in our backlog. We were thinking about that problem for a while. But then it also became really concrete. We were like, okay, how would we go about distributing and discovering these skills? And so sort of the idea became very complete. And that's where a tool like V0 really helps you.

Because when you want to extract out of your mind, you can just V0 it. And so pretty much what you see today, it started with like four or five V0 prompts in a conversation with our VP of Design who then took it way further and made it actually good. and our CTO and our product leader. So you mentioned about VMs, is there a possibility of having React Native in VZero? So what you saw today is if you feel the covers of how VZO is built,

it's built on a bunch of VARCEL infrastructure that you all have access to. The virtual machine that we use to run that NextJAS preview is called sandbox. So the VARCEL sandbox. It is a very powerful computer. In fact, what's actually making agents really capable is not that they're perfect, is that they have a computer at their disposal in order to solve any problem.

So the reason we show you a glimpse of how we work internally with D0, the reason DZO is so good at data analysis is that it has a computer where it can do research, it can write Python code, it can run it, it can make a look up to Snowflake, it can search the web, it can come back, it can fit it. It's like a four or five minute process, right? And so these computers are very powerful general purpose computers. You could imagine them running React Native. You could imagine them writing other programming languages.

They can obviously already write Python and run it. And so the sky is the limit from that perspective. I have a question on that topic. Is there going to be a point at which V0 is going to help you build those agents? Oh, absolutely. So the main idea of this chess thing, it's cute, but I mentioned the word workflow. So it's actually freaky for me to say this program is going to run forever in the presence of network or compute failures. So in fact, like, you know, we're doing this live and just randomly came up with the idea.

The reason I had confidence that demo was going to work is that if an LLN provider is down or a function called dies or times out or whatever, the workflow engine of our cell would say, we're doing life. We're going to try it again and we're going to try it again and we're going to try it again. What we're going to help you do is create those kind of workflows from within V0. A lot of agents need that kind of reliability. For example, you send the message from Slack and you say at player GPT, go and speck out this PRD for me. Yeah, it's called at chat purity. It is running on workflows. We didn't rehearse this.

Yeah. So we do have, we do have, I feel the pain on on agents where. workflows are really helpful because they gave you durable overtime execution. You can retry things. Things can fail. You can do them sequentially. You can do all sorts of things. And so I do think the ability for you to build that on the backend is very helpful.

Even for applications that don't have the same kind of UI that you would have it. Because some are very visual. And some are going to be more headless. Like some are going to be background agents that are doing work for you. In fact, the world is excited about the artist formerly known as Claudebot. mold bot. I don't know what mold bot means, by the way. Well, crustaceans, this is how you know you have kids in like elementary schools.

Crestations like lose their shell. And they mold. Yeah. It's like a snake. Yeah. Got it. And then emerge to steal your bank account. But so that's a beautiful example of the background thing, right?

Because you text it and it does a bunch of stuff for you and then a response. So that that's the kind of thing that we wanted to be able to build with VZ. where it's going to use workflows, it might use sandbox, and it might be more, I think MoldBot is like super general. It can do anything and even hack your computer. But I expect a lot of really cool agents to work that way. Like you just WhatsApp them. Yeah, and we'll help you build those with VZero.

And the last thing I actually deployed on VSEL was my live MoldBot conversations. Oh, nice. It is TerminalCorp. Oh, you have a MoldBot. I, well, I shut the computer and walked down. way. I did not enjoy my. It was an interesting experience. You can smash that subscribe button if you want to watch it. But I did, I did deploy to Versailles a terminal view of my conversation with moldbot so you can go. It's like, it's called.

Yeah. Oh, that's exactly what it is. Yeah, it's real scary. That app. Great. Maybe one more question. Oh, wow. What an honor. First of all, thank you so much for hosting the event. Thank you so much for the new V0. I ship a lot with VZero. My co-founder is using cursor and now we have like a mutual compatibility. We're so back. Love it. There you go. And so I wanted to, again, I'm also a V-Zero ambassador.

There we go. Let's go. I wanted to ask two questions. Number one, a little bit different, but when do you think, so V-Zero has really democratized the ability to go from prom to UI, UI that works, and UI that satisfies the prompt that the user created? When do you think that paradigm is going to happen within consumer in January? I see that your team has been playing with a bunch of different libraries,

different ways to create that. When do you think that switch is happening? And then the second question, when can I write a prompt and then deploy to the app store? Yeah. So on the first question, sometimes you're going to want like a flash V-0. So we're playing with ideas around generative UI

where an agent might decide to render something and think of it as like spontaneously creating the UI code. and then rendering it right away. You're not actually creating a code and an application and deploying it. You just want to make it happen. So we're doing a lot of research on like, what would that look like?

So it's another tool that we can give agents. On the app or question, you've seen some of the stuff that we've been doing with V0 iOS app, React Native Skills. A long health dream of ours has been to really democratize pushing to the apps like you would push to the web. And everything here is like sort of using those same,

ingredients, React-based deployment platform, just deploy with one press of a button and whatnot. So, yeah, don't want to promise any timelines, but definitely something we want to do. Thank you. Thanks, everybody. Thanks so much for watching. If you enjoyed this show, please like and subscribe here on YouTube or even better, leave us a comment with your thoughts. You can also find this podcast on Apple Podcasts, Spotify, or your favorite podcast app. please consider leaving us a rating and review, which will help others find the show.

You can see all our episodes and learn more about the show at how-I-A-I-I-I-I-I-Pod.com. See you next time.