Zero to Deployed: Build a Real Laravel App with Claude Code - No Terminal, No IDE, No Setup Required

should be live. No, I think them being tangled is like perfect. It's true to my true to form, you know? It's an accurate representation of my mind. Yeah. No, literally, I checked Twitter earlier today and I already forgot it was April Fool's Day, which this is a very serious stream for everyone who's starting to trickle in, but it is April Fool's Day. And I checked Twitter and I saw this like random stuff and I'm like, "Wait, what's going on? What's this? What's this?" And I'm like, "Oh my god, April Fool's got you in the You know, because by the time the day goes on, everyone's on guard. It's like I think two years ago or something, Duolingo did one that was like Duo on Ice. I'm so mad it was April Fools because I would pay to go see Duo the owl for Duolingo on Ice. I love that. I'm trying to think of like good April Fools ones I've seen, but typically Hi, Florian. Hi, Florian. No pressure with you watching. Don't have to be nervous. He's hyped for us. This will be good. We're We're going to the moon today, Hannah, too. I don't know if you saw that. This will be good. Hi, Najib. Welcome in. Hi, Mike from France. Um, Hannah and I are both in Colorado. So, very far, very different time zone. What time is it for you in France? I think like 6 or 700 p.m., right? I know UTC it's what like 5:00 PM right now I think I don't know math math is beyond times are so hard world time buddy for anyone that needs to schedule across time zones is my personal tip 7 p.m. Hi Ben welcome in cloud code on the moon yeah Hannah and I are taking cloud code to the moon or it might be taking us to the moon or stranding us in between we might be we might be crashing back down. We'll see. We'll see how it goes. Our practice rounds were a little bumpy. It's like I don't know if anyone's seen the Twitter stuff about Claude Code, the usage tokens and stuff. Um, but that definitely got us in prepping this stream. It didn't get me. It got Hannah, which is really weird. It wasn't like it knew all accounts. No tokens for you. You're done. I kept getting locked out right as me and I would make progress. So, we'll see. We might be switching screens today and see what we can do. Hi Tis, welcome in. Hi Greor. 7 p.m. in Europe. Okay, we were around it. You guys are up late. It's 19 hours in France. So seven. Sometimes my brain can do the like the military 12 really fast and sometimes one time India. Wow. Yeah. Hi from India. Welcome in. We'll get started in one second, but um when I was in college, I worked as a cashier at a grocery store and our registers were in military time, so like four hours. And I usually did the calculations correct because I guess for context, I was a math major for anyone watching. So, I majored in math. I'm supposed to be good at math and I generally am, but I messed up my calculation one day and I was like, "Oh, I get to clock out now. I get to clock out now." I was off by an hour and then I was so mad that whole last hour. I just wanted to cry because I thought I was off and I did the math wrong for the time. Oh my god. I call it military time. It's really like time for everyone. That's what I That's like a very American thing I feel like to say, but that's how I think of it, too. What What's the alternative phrase? I don't know. Yeah. Do you guys just say time? Is it ant time? I don't know. Default time. Um, you know, time with us. We call it time. All right. Confirmed. All right. Cool. Shows up and we just instantly disappoint him with the military time. Two Americans in Colorado. Just there's a lot of military bases around here. Okay. That's what that's what's going on. So, hi Emanuel. Welcome in. Hi Kristoff. Kristoff said respect for Hannah. Yeah. Don't give me my flowers too soon. You gotta You gotta wait and see how this goes. I don't think I've been this nervous since my wedding. A lot of people. So, we'll see. We'll see. Oh, man. That was good. Yeah. Floren said only upwards from here. So, this is a great point to start from. We disappointed everyone with the military time thing, all the non-Americans. So, now we can actually start. But yeah, hi everyone. Um, so today Hannah and I will be showing how to create a Laraveville app from scratch for non-traditional um, people who aren't traditionally a developer. So for non-developers. So we're going to be using Agentic coding using no terminal, no IDE, um, not even like running it locally for this. Instead, we'll be using cloud code, more specifically a cloud environment within cloud code to prompt it and create all of this. And then we're hooking it up with um a GitHub repository. So, we'll be using GitHub and then we'll be deploying the application on Laravel Cloud to actually see the real-time updates instead of uh running it locally or anything. So, that's what we're doing today. But my name uh is Leah Thompson. I am a dev engineer here at Laravel. I work closely with our online community and do live streams like this one today. And today I'm here with Hannah who also works at Laravel. Hannah, would you like to do a quick little intro? Sure, I would love to. Um, my name is Hannah. I'm an account executive here at Laraveville. So, I work with our customers that are looking to migrate to cloud primarily. Um, that's kind of our sweet spot of where we interact with customers. Um, I I guess I do have to have some disclosures around my background. I used to be a front-end engineer, but I've been in the sales game for about five or six years now. So, um, there's a little bit of familiarity with what we're doing, but it's been a long time and things have really changed. So, I think when Lee and I were talking about this live stream, our goal was really to think about how can we make it easier for anyone, whether you're on a marketing team, an ops team, finance, whatever your role is, um, to use Laravel to actually build an application that you can use. And so, we have a lot of use cases internally. Um, and we want you all to be able to go and help kind of your co-workers use Laravel as well um, in new and interesting ways that make your jobs easier. So um that was kind of the the origin story if you will for for today. So we'll see how we do. Yeah. No, exactly. And also because uh like you said a lot of people internally at Laravel have started shipping um applications using Laravel and hosting them on Laravel cloud and sharing them internally like um Sam Sappenfield posted on her LinkedIn that she built a tool that we're going to use for Laracon that helps um schedule out where everyone needs to be for the different boosts and stuff. Um people on the sales team. So Hannah's boss has created kind of what what is Drew? Drew is a it's a sales coaching and intelligent app. Uh so it basically helps us pull customer conversations and understand where our gaps are in technical understanding, migration plans, all that kind of stuff. I think I think we have lost our VP of sales to the engineering team. I think he you know he's been vibe coding on the weekends. He is fully on board. He's in it. Um, and so yeah, we might he might be needing a switch of titles uh before this is all over with with the the pace that he's going at, which is great to see everyone jumping in. I know a lot of people too have been using kind of like the terminal um to connect to cloud code, but there's like when they're then trying to get their friends doing the same things, like if they tell their friends like, "Hey, I built this app and then they also want to do it." It's a little hard for people to um kind of figure out how to get started, right? How to do the dev setup? Do they need to bring in Larurd? uh what do they need to install with PHP and everything. So Hannah and I thought we would show doing it this way without needing the terminal, a dev setup or IDE, anything like that because I feel like it's a really easy entry way to get started and get something shipped on cloud. So I guess let's jump into it. Yeah, let's do it. All right. Um, so to start us off and kind of give a little bit of um, context on what we're looking at here and what we already have pulled up, I guess we have my calendar that's not going to be as relevant today. Um, but we've got um, a new GitHub account that we created. Um, so I just went through the normal login flow for that just to, you know, save us some time and um, not have you all know my password as I'm going through the login flow for that. Um, we also are going to have um, a cloud setup. So, we've got my own Laraveell cloud account. So, we already have that logged in just so that we're not you know spending time with um you know all the wiring and all the connections there. And then we've got um cloud code set up and it is already connected and enabled with my GitHub account. But that is just a matter of a couple of clicks. Um so nothing too crazy going on there. So just to kind of orient everyone to what we are going to be working in today. Also, did you already create the new GitHub repository that we're going to use? Yes. You want to show really quick where you go into the UI to do that? Yes. So, if you hop into your homepage on your GitHub account, you'll see this new button. It's pretty obvious here. You can click new. Just do your name of your repository. And then you don't need to do any of these kind of configuration steps here. Um, so unless you want it to be private, so people can't see your code, then you would change the visibility. Otherwise, if you're fine with it being public, which means people can go to your account and potentially like look at all of the code that you've generated, then um, leave it public. If you don't want that, just change it to private. It's a good point. I know you're all going to be forking the repository that we build today because it's gonna be it's gonna be beautiful. Yeah. So, pretty easy step there. And then of course cloud you can go and sign up and get um a free trial credit. Um so you don't have to input a credit card which is actually just what I did for my own cloud account. So you can see here that I'm drawing down on my $5 of credits for this as well. So everything here I guess with the exception of cloud code um is free. So and if you sign up for a new cloud account like Hannah just said you will automatically see the $5 credit applied to your account. So then when you host your application on Laravel Cloud, you're not having to like pay for it yourself. Like it would be covered under the $5 credit. And I did link the or I did share the links just for github.com and Laravel Cloud that we just talked about. Now we can proceed. Sorry about that. All right. Hannah's like trying to teach and I'm like, "Okay, side note. Can we actually show this?" I'm like a little nervous. Um, okay. So, Leah, will you kind of walk me through all the different setups here with the configuration in a Cloud Code session? Yes. Um, so we went well, first off, we went to Cloud Code. So, we went to what? Claude.ai. Cloud.ai, which is their website. And then from there once you're signed in so for this we you do need a Claude account which we're using the one through Laravel today. I also tested this on just my own personal Claude Code Pro subscription which is $20 a month and that's worked fine with that as well. And then from there we hit the code tab to get to Cloud Code. And we're doing this all through the browser. So this is Cloud Code in the browser. You're seeing the little chat box now. So, where it says find a small to-do, you would put in your prompt and that's where we're going to like write our prompts later on. Um, when you hit the plus sign down at the bottom. Yeah, that's if you need to import an issue from GitHub or add an image or anything. You could also drag and drop or copy and paste images into this box as well. uh plan mode which is what I think we want to use for our prompts just so it will actually create a plan and then ask us to approve it before implementing it otherwise it will just automatically start working on um the prompt that you give it where you see opus 4.6 six um and the 1M for the context. This is where you can change the model that you're using and different models are capable for different things. They also have different uh what token usage limits. So different models will use the tokens faster than other ones. At the bottom where you see the live stream with Leah, this is where you would change what repository that you are connecting this Cloud Code cloud environment to. So Hannah's already selected the repository that we want to use for this, which is an empty GitHub repository, nothing in it. And then where you see live one, sorry. Um, where you see live one, live one is the cloud environment that we're using for this cloud code session. So you can run it locally, which I feel like is what most people do when they do cloud code. But for this, we're using a cloud environment. cloud environments. You connect to a GitHub repository and then it will just automatically push up the code it creates to that GitHub repository which is what allows us to have no terminal uh no IDE and just uh create this through the browser basically. Leah does this manage the git part of it as well like committing to code and stuff or you know Okay. All right. I'm going to create a new environment for us to make sure you select it. Yeah. Okay. All right. Okay. That was all the setup so far. So, that was set up and now we can start with the actual prompts. Um, also let me know in chat while we're continuing to do the prompts if you have any questions about the setup step and I'll try to answer them as we're waiting for Claude to cook um, so to speak. So, yeah. All right. I want to create a new Laraveville application using no starter kit. If you want to explain that particular decision. Um yeah. So when you start with Laravel we offer different starter kits. Um we have no starter kit. We have one with livewire react view spelt and I might be missing one. Um, but we offer different starter kits. The reason we decided to go with no starter kit for this specific one is because um, for what I want to build, we don't want to do authentication. So, we don't need O built-in. And I also felt like if I build it using the React Inertia starter kit or one of the other ones, we would just have to rip out some stuff because it brings in authentication. Um, it brings in like the sidebar and different things. Whereas if we start with no starter kit, it's just no scaffolding, right? So we don't have to then go in and prompt Claude to remove certain things. So I feel like it made it a little easier for our specific use case today. But if it is an application that you want to have authentication everything, I would definitely recommend using one of the starter kits. Um if you I know Taylor had shared I think Taylor put it in Friday. We have a kind of prompt to get started for agentic coding using Laravel. Um, and if you were to use the prompt that he put in the docs, it will by default bring in the react and inertia starter kit. This is the prop I'm talking about. So we just specified here I don't want to use a starter kit just so it doesn't by default bring in one of the starter kits. Okay. Um Luan did ask does Laravel have an MCP that I can connect in my cloud code which is a really good question. Yes it does. Is called Laravel boost. So Hannah can you scroll up? Yeah, if you see in Hannah's prompt, she put I want to create a new Laravel application using no starter kit. I want to install sorry I want to install Laravel boost for it and make sure to use boost. So this is the MCP or like Laravel boost itself is built using uh Laravel MCP and it also has skills and different stuff built into it like there is a um Laravel skill that we shipped last like as early as last week too or as recent as last week. So all of that is bundled into Laravel boost. So by telling the agent or the model that we want to use boost, we want to install it and use it, that is going to bring in all of those skills and everything. That was a really good question. This step always makes me really nervous because it takes a while. Yeah, it's good. I was timing mine earlier to make sure like what we should expect to for but planning takes a little bit of time as well. And I just I kind of yoloed it. I didn't even plan earlier when I was doing a run through. I was just like just do it. Hopefully it'll it's almost there I think. Oh, so boosters MCP. Got it. I thought that was another Laravel tool. Let me actually go to the website to show that boost. Yeah. So I do kind of think of it as a tool. It's built using the Laravel MCP, but it allow it accelerates AI assisted development by providing the essential context and structure that AI needs to generate highquality Laravel specific code using any agent. So I think of it as a tool you build you bring in boost you tell it what um agents you want to work with like if you're using cursor if you're using cloud code if you're using um what codecs and different things like that and then it will autodetect like say if you're starting an application using the react starter kit with Laravel then boost will say hey we see you're using this if you brought in four Ify, it'll say, "Hey, we saw that you have fortify. Do you want to bring in this this skill and go ahead and download the skill for this?" So, by bringing in boost, it automatically like detects what skills are relevant to bring in. Um, I think by default now it sets up the new Laravel skill that was shipped last week. So, it just makes it easier to do aic coding using Laravel. provides a lot of context um because you know in models there's usually like a context gap where the models are updated and then we constantly ship updates to Laravel. So by like by the time the models are released is already outdated on certain things that we've shipped and boost helps bridge that gap. All right, we've got a plan. This is the website. All right. So, it's gonna create a Laravel app, install our front end dependencies, customize our theme and colors based off our green, dark, white that we gave it. It's going to rethe the homepage, create a base layout file, and build and verify. So, I think this is a good first step. Let's approve it. All right, let's see what happens. Um, and then Zayn said, "Not only MCP, it's also a context in Skills Manager." Yeah. Yeah. Because it's we do have a Laravel MCP, which Boost is built using, but I wouldn't say Boost itself is an MCP. Um and then Sassy Muffin said, "So Laravel core team still developing the framework themselves or is Claude driving dev now? Always appreciate the elegance of the framework but concerned concerned that we're heading into Larosop era. There's some of the team who still mainly writes code themselves. Um, there's a lot of us who are using AI a lot, but still with anything we're using AI or agentic coding for. We're still keeping the quality there. We're not just like accepting what it gives us. We're making sure it's at the bar of quality that we expect, honestly. And I know for me myself whenever I've used an agentic coding flow I don't personally like if I was doing a a side project I for sure would do something like this for work I am going to have like cursor open like an IDE open and I'm going into the code myself and I'm double-checking everything it gives me and I'm constantly trying to make sure it's optimized or it's clean because a lot of times it gives me a solution that works but I don't necessarily like the way it did it. Um, so yes, at Laravel we're leveraging AI now, but we're still keeping that quality there and we're not we're definitely not going into a Larop era in my opinion. We are very conscious of slop, right? of how using just purely AI you can just provide uh produce slop and we're not we're very I guess conscious of that and making sure we still keep the quality Nib said make sure to use skills along with Laravel boost MCP yes which if anyone has specific skills that they use a lot or that they enjoy Please let us know. I'd love to hear that cuz I'm always feeling like um like I really don't know the skills that are out there or the ones that are worth bringing in. I don't want to just bring in a ton. So, I generally just use the ones that are brought in with boost. And then you guys might notice that as Claude's working on this, it's like automatically updating everything. If you expand the um edited a file, updated to-do list part. Yep. Every time it's changing stuff, it's updating the to-do list that it created. So, even while it's still working on this prompt we gave it and like going through the plan, we can see what step is at, which I think is really nice. And Rebecca, I saw um your note about how we connected get to cloud code. I can send this to Leah and she can drop it in the chat. But it's basically just clicking a couple of buttons and and saying yes, you can install um pretty quick. No issues there. I shouldn't say that until we're actually able to push to GitHub. That might be might be uh famous last words. We'll see. We had some issues with that yesterday. But able to get connected. Let's see. Yeah, because like you see with Hannah's um in the bottom, can you hover? It says live stream with Leah. Whenever we were adding the GitHub repository before, before she connected with GitHub, I believe that there it just had um like connect to GitHub and we were able to click that to then sign in with the GitHub account and authenticate it to work with Cloud Code. You could also go through settings and connections and connect there as well. Um, but Hannah has linked a nice little guide on like from Claude's website on their GitHub integration. It's got all the pictures of where to find everything. Do you mind um opening another tab with settings? Like if you go to your H down there. And then you go to settings and you what? I was like, no, I was gonna say, it's okay. Sorry. Let's see. It's still going. It's still going. We're good. We're good. Go back. And then if you go to connectors. From there, if you So, she went to settings for Claude and then she went to connectors. Here you see it has a GitHub integration and if that wasn't connected you could hit configure there like you see for the Gmail one and that would prompt you to then sign into your GitHub account um authorize it to work with cloud code and then when you go into the cloud code session you would be able to connect your GitHub repository. And now I think we can go back. Sorry for the jump scare for you. Well, I just was like, did it stop? That would have been that would have been okay. Would have been okay. Well, do you know what these numbers are? Oh, it's the diff. Okay. Actually, really like that it gives you that and that you can click it to actually see what it's doing if you did want to look at the code because again, no IDE is needed. We are just able to pull that up within this browser session. And thank you for that question, Rebecca. That was a good question. Um, NEP had a question. Which one's better, Codeex or Claude? Take, I guess. Have you just used Claude mainly for AI stuff? I've done a little bit of like in my onboarding a little bit with Codeex, but I've mostly been in Claude and I use a lot Claude a lot for my job. So, it is my my natural home, if you will. I use Claude the most. I want to try Open Code more, especially since I know Open Code, I think, has more of like a free plan. Um, I want to try Open Code. I personally have used Claude the most and I use Cursor for my own programming and stuff. I've only used codeex once. I should try it more, but I just haven't used codeex a lot. So, I'd love chat to know what you use, like what AI tools do you use the most. Well, and now that like cloud's kind of changed their plans and their limits, maybe everyone's going to start bouncing around between all the different free plans for tokens and stuff. So, or using multiple. I know um there's some people who use multiple ones and they might go to like claude code to generate a plan like to do the process and then have that put into a markdown file and then take that markdown file to another agent or like another um model or something and then give it that and have it then actually implement it. I've heard of um I was talking to a VP of engineering and he was saying that he has one model write the code and then one model do an initial pull request review of the code. So he has different models kind of check the other one. So I thought that was an interesting use case as well. Yeah. Which I think is why people like oh man what is it the tool that Beyond Code created is it Polycope? No. um that I think allows you to kind of run multiple agents at once. And I think the tool that Aaron Francis was working on solo is kind of the same idea too of multiple agents. Dave, what is the name? So, hi Dave. Oh, Polycope. He did say Polycope. Okay, there we go. Sorry, I had to scroll up. And that will pull in multiple agents. And yeah, you can run multiple. Okay. Does it do like decisioning around which one to use or is it more just like I think you I don't I don't know. Dave, can you answer that? I think you choose. I don't think it just like fires it up. Okay. But I'm getting a lot of claude codecs. Um, and then I saw a codeex after Claude has no context left, which I when Claude runs out for me, I go to cursor and I use the composer model. So, hi Daniel, welcome in. How are you doing? L had a Oh, wait. No, go ahead. Go ahead, Leah. Don had a good question. He said, "Do you guys have any thoughts on the results difference in the code generated in the CLI or in the browser?" Do you do I? Yeah, I think you know, you and I were testing this a lot this week and running into a lot of a lot more issues actually with um well with like Claude's app versus being in the browser, which was interesting to me. Desktop app. Yeah. Yeah. So, I don't I could see there being a difference there. I wonder if they get piped to different Mhm. you know, workflows. I don't know. Um I want to test it almost after this stream. Like I want to test it with just the CLI tool. Um I would say I haven't tried using the CLI to just create a full application because usually when I'm using the CLI, it's within cursor and I'm so I'm in the IDE. I'm looking at the code myself and I'm like actively getting into the code changing things and I'm not just like straight up prompting it. So I haven't just tried prompting from the terminal to get something without touching the code myself. Whereas like with this in the browser, we were able I was able to create a full application from just prompting in the browser. But like Hannah said, we did have more luck using just a cloud code. um cloud environment within the browser versus the desktop app, which was a little a little interesting. So, if anyone tries this and they're using the desktop app and it's like getting stuck on certain parts, I would recommend you try going to the browser and doing it. Leah, as a heads up, I just checked my usage. What is that? We're at 72%. So, we'll see. We'll see how far we get today with my Oh, we should switch the model from the 1M one. We can do that. We can do that after this. We could also run the second prompt without planning. Just Do you think planning takes up more tokens? Yeah, planning 100% takes up more time. I mean, chat, tell me if I'm wrong, but my in my experience, every time I've done planning mode, my tokens burn through way quicker, which is why I generally don't use planning. But I will say when doing prep for this stream, I did try planning mode and I I realized I was wrong about my earlier assumptions that planning mode's not good. Planning mode is pretty good, but it I was wondering too if it if planning mode helps it move faster once it has some of that decision like you're not, you know, I like Oh, sorry. Continue. No, I just I'm I don't know how kind of the how much work it takes if you don't give it some of the parameters in planning mode. My I see I don't know. I feel like it takes less tokens um when I don't do planning mode. But to me, it kind of feels like it's like with a human, right? Say if you're actually thinking about the solution first versus just blindly trying to solve it, you're going to end up with a better solution. Um, so I think when I did planning mode, I ended up with kind of a better app that was closer to what I wanted kind of more. That's like 80% of what you wanted versus like 60. Yeah. Yeah. Because you're giving like it's you're letting it think and actually create a plan. So it's can come up with a better solution basically. And then also once it gives you the plan, you can change certain things about it. So you're also able to catch certain things that like, oh, it's going to do it this way. No, let's actually like don't bring in a starter kit or let's actually not um like earlier whenever I was doing a run through it brought in this hook like this like weird hook session thing and I don't think we needed it. So if I planned first I would have been able to catch that and be like hey don't do this we don't need it. So you just end up with something more refined versus just letting it like having to go back and edit all the stuff that you Leah, how long does yours take when you do it? Cuz you were saying like three or five minutes and this is totally not that long. But I didn't do plan mode again. I feel like plan mode maybe. Yeah. And Dave had a comment too that he said he uses opus for planning or I don't know how to say it correctly and then sonnet to actually do the work since you've already had opus do the hard work of the plan. That's a good call too cuz I was trying I did sonnet earlier too which I did notice um I think my app looked better when I built it with opus versus sonnet but I did end up with a full application even when using sonnet. Uh let's see and then Daniel said um off which I think is like off topic. I love how engineering itself is more about discussing the problem and let agents to resolve most of the code. Yeah, I think that part's been nice too and being able to focus more on the architecture, you know, like how should we solve this problem? Like what is the best way to do this? Um versus just worrying about the like specifics of the actual code. And then you get to kind of spend more time as a code reviewer, you know, like actually going through it, still making sure it solved in the way that makes the most sense, but you're not having to be like in the weeds creating all of the code. Daniel did say at web somehow the plan mode doesn't work that good. That's great. I was like, Leo, what did you bring me in? Love that. So good. I know. I think we might have just run out of tokens. Um yeah. So 100% usage. So I'm wondering when it's going to tell me it's it's quitting. So we might need to pivot. But how far is it in its plan? Let's see. Welcome page. Okay. One second. I think it was the model or well I mean we also knew that your account you were having issues with the ever since the usage kind of thing that they've got going on. So one of the lucky ones they're keeping me sharp you know they're like you can't use too much AI. You have to really think about when you want to use it. Let's see prompt one. You sent me this one. Is it still going or does it seem stuck? Um, I would say it's I don't know. I'll put I'll put that to the crowd. It looks pretty slow to me. The chat chat want to weigh in on give up on our clotting our clotting. Uh, okay. You know what's crazy, Leah, is that I think you've done this same workflow like four times in one day with no issues. So, I do have two accounts, but I've done it at least two or three times on the same account, and I again did not have an issue. Okay, while Hannah's doing this, I'm going to go ahead and start prepping um mine so we can switch to mine. My cloud code. I'll do it from um I'll do it from prompt one that I'm going to run now. Should I run it with plan mode or without plan mode? And what model should I use? I'll let chat and Hannah decide. I'm going to say plan and opus. Let's take Dave's suggestion. Plan with opus and then switch to sonnet to run it. Okay. And I'm not doing the 1M opus. I'm just doing opus 4.6 because it does show me both of those. Um, so, okay. Florian said no plan, though. No plan opus 4.6. All right. Let's just send it. Let's just go for it. Let's see what I see what it can do. Should I switch to my screen? Yeah, probably. I'll let you know if mine pops back up. I'll leave it running. Okay. This is the lovely thing about using a AI, right? Like it is a powerful tool, but with like the different token things and things that can just happen. Sometimes this happens, but we are going to switch to mine and we're going to start from prompt one. So, we're going to switch to my end. Still doing the same thing, prompt one. And just see where we go. All right, let's see how fast yours is compared to mine. This will be a fun comparison game. This is the wrong one. Stop sharing. I have so many tabs. It's trying to figure out where my tab is. So, sorry. We're We're trying to figure the hardest part of the job, you know. Oh, because it's not in Oh, Florian said, "I like planning, but I also want to see them deployed to cloud." Okay, one second. Sorry, I'm going to share my whole screen over here. So, I'm trying to close stuff. My goodness, I have so many tabs open. Sometimes I so I always have a bunch of tabs even in like Chrome and sometimes my husband will walk past my computer and he's like, "For the love of God, please close some of those tabs." I guess I think that's what we should discuss in the chat. Are you a tab like a lot of tabs person or a single tab person? I feel like there's it's a very distinct group of people. Yeah, I'm a lot. I'm a lot too. Okay, so Oh my god. Hold on. I'll just refresh. It'll come back. This might happen. Okay, so I'm about to fire off our first prompt, which is I want to create a new Laravel application using no starter kit. I want to install Laravel Boost for it. Make sure to use Boost. I want the app to have a white, green, black color scheme. I'm not planning it at all. I'm using Opus. Um, let me move this so I can see. I'm going to use content lib one, which is a GitHub repository I just created. There's nothing in it. And I made a new cloud environment called stream with Hannah. I'm going to use that one. And let's fire this off. We've got some deferring opinions. We've got as few tabs as possible from Florian. And then Ben said at least if you don't have at least 100 tabs open, are you really working? And then Chris said multiple tabs in at least three to four windows. So I'm kind of the three to Yeah, I'm like 10 tabs per four windows, I think, is kind of where Oh. Oh honey, I'm like 60 tabs. 60 more tabs in like each window and then I have four windows to the point where like before we got on stream I had to go in and close the other windows because I didn't want when I used to stream on my own MacBook Air everything. No, I mean my stream was cut out like 10 times per live stream because I it was the fan was going. I was about to blow up the computer with all my tabs, Discord open. Yep. I do try and start the day clean, but it just never stays that way. Okay, so we started this. I almost want to time it. I almost want to time it from when I did it. All right, we're at 42, we'll call it. And it's checking the repository state. So it's already going through it. It's doing. We appreciate you. Yeah. More. We really need more tabs at all times because Dave also said multiple tabs and multiple windows on multiple desktops. I do work with two different computers than the day. I'll switch computers. What? Midday. Yeah. my first day like just you're like it's time for a fresh one like at one my work laptop and my personal laptop I have like a certain meeting or something I'm like okay let's do my work laptop and then I'll be like okay let me go work from the couch and let me now use my personal laptop to like play around with like the cloud code stuff or like working on something stuff like that I'll just like switch my desktops and then I have like a desktop setup with multiple monitors versus okay I work one computer. I don't know about everyone else here, but it's just one work laptop. You never work off another one. Not like if I'm actually working, you know, like my life admin. Yes. But um no, I keep keep the work on the work computer, you know. Gotcha. But whatever works for you. There's no judgment here, you know. Judging that's that's so much judgment. That was a lot of judgment. It's kind of like I'm not going to judge, but um can we see the expanded progress bar? Where is this expanded progress bar? So, we can see what's behind the scene agents plan. Otherwise, we would just be assuming issue being stuck forever. Did you mean for Hannah's? Because Hannah was at 100% of her tokens for today, which is the reason we pivoted to mine cuz I believe it was like actually going to stay stuck just because she's already at that token limit. But if you're talking about the one you're seeing right here for mine, then I would love to show you that. If you just tell me how to show you the expanded progress bar, unless you just mean like these, which for mine, you can tell it's changing. It's going through it. It's not stuck on them. Yeah, yours are moving a lot faster. And I do apologize about having to switch from Hannah's to mine, but with Hannah's account, we did already notice when prepping for this and preparing that her her tokens like I ran a prompt, right? My token usage could be at 3%. Hannah's would be at 50. Like I'm I'm really burning through them at a higher rate. It's like we got to work a little harder on your account. Maybe we need to ask Andre like I know. I was like maybe Yeah, maybe I should go and see if I can get a higher limit. Interesting. Oh, you were reading that one, too? Yeah, I was sorry. I was reading it because Najib said, "I think you should create a video explaining how to use agents efficiently so they consume less context and perform better." I do think that's a great idea, and that's something I'll talk about um with Josh and Kristoff as well. I think like I'd love to do a live stream with Josh too, like showing that. Um, but I also think it's something like a video or a blog post would be good for as well. And we did, um, I did pass on some of the comments from the live stream I did with Josh last week as well where he was showing instruct and stuff because there were some good questions there about how you could um, how like MCPS can use a lot of tokens. So, how you can better like use them efficiently without using all of those tokens. So, we do want to show kind of how you can do agentic coding and use less tokens like without spending as much money for it. Uh, and then Florence said, "We don't know how to be efficient. We have unlimited tokens unless you're Hannah." Yeah. Not on my team. The sales team doesn't get unlimited tokens as it would turn out. I bet Andrew has a special special account. Yeah, because he's an engineer now. So, yeah, exactly. Because he's an engineer now. Um, but like Pushbuck said, the limit bug is very wild. If you look on Twitter, it is something Anthropic is looking into. Like it is an actual bug that they were having where people are hitting the usage rate like super quick this week. So, this is a a bug on Anthropic side, but they are aware of it and working on it. And let's see. Yeah. So, mine's already done. All right. So, we're at what, four and a half minutes. Do we say 42 or 44? I can't remember. Either way, it was much faster. Yeah. So, mine's already up. Um, all changes committed and pushed to a specific branch on that repository. Um, cloud/ol boost setup. If I then go to the repository and I refresh, we see all of this. So, all of it is already live. Um, or not live yet. We don't have it on cloud. It is on GitHub. I'm going to go ahead and log into cloud which I was not signed into or I should be signed into but I didn't have up um from the cloud dashboard. I'm going to do new application now. Let this load and I'm going to deploy the content lib one repository which is the one that cla pushed all of our code to. And I'm just going to create it. I'm going to deploy it. The funny thing um is we did have we did have like the prerequisite set up like Hannah made a new GitHub account. all of that, but it's just her account and the usage this should be pretty fast, too. Okay, I deployed this to cloud. Let's visit it. One second. Wait a second. Visit now. And we have an application. All right. not the specific one we wanted to create. We have another prompt we're about to to send, but we have an application. It's on cloud. You could go to it here if you wanted to. There we go. And then, of course, we would want to change the link for this and everything, but for the sake of this, I'm just leaving it as is. I'm not using um I'm not going to change the link through cloud or through cloud or um use a custom domain or anything. Let's And if you want to put in the next prompt and while you do that I can talk a little bit kind of around our app and what we were thinking about. Um I don't know. Do you have it? I can send it to you. I guess let me test this because you don't see any of the Well, I can test it with that. Okay. I was I was trying to double check what I was sharing if it was like whole screen or just the browser. Yeah, just the browser it looks like. Yeah, you can talk through what we're doing. Oh, yeah. I didn't want to distract you. but um there's a lot of text in here, but basically when Lee and I were talking about this, one of the things that I am doing a lot of is pulling customer stories that are for customers that are similar to the one I'm talking to or um you know, I'm interested in kind of like the content that we're putting out. The Laraveville team is really great about getting different blog posts, webinars, live streams, um you know, all sorts of stuff that is useful for our customers, especially when they're considering a migration and need to kind of understand how to present this to their teams, um present this to their boards, whatever it might be. And so, we came up with the idea of a content library because a lot of this lives in a lot of different places. And so I wanted one place where I could go and kind of look through all the different um kind of like tagged content that we have to pull. So I can say, "Oh, this is a forge migration or this, you know, customer is, you know, using Postgress or whatever it might be." Um, so that we could kind of pull that a little bit more effectively rather than me going and searching our blog or searching Google and seeing what SEO comes up and knowing that something exists. So that was kind of the impetus for this uh this first MVP app. And so it's like a content library and um calendar. So also having a different page to see a content calendar so it's easier to share what live streams and content we have planned. Um I was saying like YouTube videos and live streams specifically because it can be hard for people internally to know. Some of these things we would have to bring in like a notion integration and different stuff. We don't want to show setting up those API tokens on stream. So, we're going to use um like dummy data and stuff like that. We're not actually going to bring it in, but we did in the prompt uh what is it kind of tell it to do the scaffolding for that to bring in later? Yeah, it's like stub out a notion integration, but keys coming later. um cuz we want to be able to export those events and add them to your Google calendar or Apple calendar. So, I'm about to send off the prompt and then we can dive into more like what the prompt says. What model should I use? Um and should I use plan mode or not? I'm leaning towards not using plan mode, especially since we want to ship it. Go for it. Yeah. And I think let's do 4.6 again. Okay, Dave did say plan mode in all caps. Okay, maybe we just do we'll do a quick I nervous. Oh, Hannah said okay. No, no, no, no. Do it. Do it. Do it. It's okay. This is good. You know, we I think Nibil said we have achieved already what we claim zero to deploy. So, anything else is is extra at this point. Why are the settings not coming up for me? That's scaring me. Hello. Okay. Okay. He said plan mode. Florian said no plan. Should we use Opus, Opus, or should we use Sonnet? I think I'm going to go no. The chat's not The chat's not helping. It's you and me, Leah. So, opus or Sonnet? Let's do Opus. That was good. It It went pretty fast through the first one. Let's just We'll stick with the good thing. You guys are no help. box like Florian's like opus opus. Okay, we're shipping it no plan and opus. Florian really won on this one. Here's the no plan opus. He did quadrant. Okay, here is the full prompt I shipped. So, build a Laravel plus blade marketing content hub. No off. Sorry, it keeps saying that. Is it down overall though? No. Okay, it's not. No off. Alpine.js is fine for small UI things. Three pages with a navbar. I want active and hover styling for that navbar and content library as the default. So that should be my um my was it home route or my root my root route. Then for content library for that page, pull blog posts from the laravel.com/feed which is the RSS feed that we have set up and autogenerate topic tags from the post title and RSS uh categories. YouTube and docs integrations are subs for now the keys coming later. full CRUD on content, two tag types, one for content format, which could be blog post, video, docs, and one for topic, which could be forge, cloud, my SQL, Postgress, inertia, like different things that relate to that content. Full CRUD on tags, too. Filter/ search by any combination of tags. Content calendar, read only for visitors, no public editing, events have a title, content type, status, whether shipped, scheduled, canceled, or to record. And it's all colorcoded. assigning and topic tag seed amount the realistic events for now stub out and notion integration uh with Google calendar and Apple calendar uh export per event which is the ICS files and then the customer story form we just want a form where sorry my dog like slammed her like trying to sit up she like hit her head on my desk oh my god but a customer story form where we could submit customers or people in the community we think would want to do a customer story and we put in their name, email, and the preferred format they'd like to do that whether a blog post, a stream, YouTube short, or anything like that. So, that's the whole prompt I sent off. Here is where we're at now. Um, make a plan. Yeah. So, it made a to-do list. The to-do list, if you can't read it, it says create models, migrations, and relationships. Um, it already did that. part not cooking on the building RSS feed service tag autogeneration and stub integration. Um also sorry sorry opus and no plan chat was so divided on it. So divided. Uh Juan said proven cloud will not replace the devs as long as we use him as a tool enhancer and not as a substitute that replaces us to do the job. Yep. I think we confirmed that on the live stream today. Yeah, we realized that it's not always reliable, right? Like there's always going to be a job for developers. If you run out of tokens, you know, then what do you do? Do you switch models or like if you if you're a developer, you can just go in and work on it yourself, take over from where it left. Um, but I do think it's great that using these tools that people who aren't traditional developers are able to actually ship applications and create useful things. And like internally, we've been doing a lot of that not to replace any of the developers at Laravel, but to allow us to work faster, right? To make our jobs easier, just doing different automations and stuff like that. Um, use bare hands. E, it's like basically like running out of gas when you're in a car. You got to start walking. That's the uh the equivalent here. Let me see if I can Oh no. Okay, that's fine. This is still going pretty quickly overall. Yeah, I said oh no because I was trying to do something and it pulled up something else. That was the wrong Okay, you still see the right tab. I was trying to zoom in. It's okay. Um, we are on the fourth step now. So, I already did the RSS feed stuff. It built the controllers and routes and now we are building shared blade layout with navbar. Oh, I know why. Leah, while we wait for this, what would you say to people that are trying to help someone internally get set up on a Laravel app using this kind of workflow? Like what makes Larel good for this kind of use case specifically? I know there's been some comments in the chat. Yeah. Yeah. Yeah. So AI itself or AI itself, Laravel itself is opinionated on how you do certain things. Um, which is pretty structured. It uses the MVC format model view controller and especially like with our um starter kits and everything too. I think it makes it really easy to get started with Laravel. But if you are using AI agents and you ask it to do something with Laravel, um chances are Laravel has a specific way that it would implement that. like it has opinions of how that would be solved and especially using Laravel boost which feeds in all of the docs. It has that context. So then whenever you ask the agent to do something, it's able to look at the docs and find out how the recommended way to do it is. Um, which makes it easier to create an application using it whether or compared to if you try to use AI with something like React or like JavaScript in general where it's not as opinionated. Mhm. You can run into more issues. Like it's harder to just get even like an MVP up and running, you know, because there's so many ways that you can do things and you're kind of having to think more about that versus having using something that is opinion. It is boost being used at the moment. I believe it is. Isn't the original prompt? Yes. Are we using boost for all of this? and making also making what boost to calls Sorry. Okay, there we go. I have a split keyboard. I was trying to remember how to zoom in. What a flex. Well, because I was like, how do I zoom in? And I don't want to seem like I just don't know how to zoom. I was trying to remember what is my keybind to zoom. Let me see if let me use the boost mcp server tools to verify your application. Okay, it's checking. We do we did bring in boost. What are you talking about? Oh, let me use boost artisan capabilities to verify the app and then wrap up. What part of our plan was it on? It was at um where are you? The very first prompt, I think, is the one that says, "Yeah, use boost." Yeah. Yeah. I was trying to see where it was on these is here. Was it not set up? I don't know because it did. I I kind of hate it collapses stuff after it runs it. Ran a command. Loaded. Did it install it again? It did install it, but didn't it earlier? Let me see. Let's see if you can find the boost. That is interesting. Research Laravel boost. I wonder if it installed Laravel and everything, set up a new application, and just ignored the boost. No, cuz it said composer required Laravel boost here. So, it did bring it in. It mpm installed. I don't know if it ran boost install, which it would need to, right? Well, it did lower, so maybe. But I guess that was only after you prompted it. That was after I specifically had to ask it if we were using boost or not. Yeah, I don't think I ran boost install before. It did do composer require. That's interesting. Let's see where it's at. Would I need to restart the whole thing to use? Wait, hold on. Okay, it did say everything was built. So, did it already create everything? So, it said everything was built the pages with a shared nav. It's detailing everything that was in my prompt. And then says we have a boost integration that will be available in the next session for introspecting models, routes, and databases. So I don't even think I used boost that whole time which definitely we should have. So if you are doing this at home uh make sure after so with the first prompt we did install boost make sure that it is using boost. So if you look like we went through it maybe in that second prompt just being explicit around using yeah in the second prompt I'd be explicit saying make sure you're using boost and using um tool cost from boost because it did composer require for it but it did not do boost install so it was not using laral booster there which boost does make it so much easier like Gareth said I think it pushed up again though to content lab one. Uh it did a minute ago. So this should be redeployed on cloud already. It is. Where are we at classic? Doesn't count. Yeah. What is Why are you at a 500? Because I don't think it was It was like on step three and then suddenly it was like, "Okay, I did it all." What is AI doing the Oh, wait. No, never mind. I don't have a database yet. That would do it, too. Let's create a database. gonna create a new database. We'll name it when you create the Yeah. Do you want to talk about why you need a database for this app? Um, yeah. So, we set up cedars and different things also because we're trying to show all of our content and the um stuff that's in the calendar. So, we set up like CRUD for this. Um, so you can create, read, update, or delete any of these things. to create them. It's trying to store them to a database. We don't currently have a database. So, even when we're trying to pull the content from the RSS feed of the blog to then kind of um backfill our content library, we're still trying to save those in a database and we currently don't have a database. So, let me actually let me see. I want to use Postgress. I'm going to do Oh, no. I want dev, but I want custom configuration. I want to make sure hibernate is on. I'm going to save this. I'm going to create and then I need to save and deploy. Okay, let me go back and read what it said. Um because I think it might have made artisan commands that we need to run to see this stuff. But any artisan commands or cedars that we need to run redeploying us. It looks like it's done. And there we are. Okay. Yeah, I was like 500. I was like, what is going on with this? Um, okay. That was user error. We needed a database here because we did CRUD functionalities. So, we needed a database. I just had to create that through the um interface of Laravel cloud to add that database. It redeployed and now we are cooking. So we have this content library. Um I'm going to click the import from RSS button here which should be able to then get all of our content, all the blog posts through the RSS feed because this is public. So we didn't need an API token or anything for that. Okay, I clicked it. You can see it's loading. And then look, we pulled in all of those blog posts. And um I can show you too where that is from, but it was from I think it's just feed, right? Yeah, I think so. Which is the RSS feed from the blog. You could also get here if you went to laral.com/blog and you clicked this um RSS feed icon right here. That also takes you to this website. So, I pulled all the blog posts from this. That is how we got all of this content you're seeing right here. And you can see it already tagged it. Each of these things are blog post. We probably wouldn't want this RSS um little badge up here. So, we'd prompt Cloud Code to remove that. But we have that all of these are blog post. Um we have tags on them that it relates to Laravel and then my SQL because this is um database tools. This one is nightw watch. We have cloud and Laravel. We would want to add nightw watch here too. So we could like fix how it is um choosing what category tags to put on these. So that's something we could prompt again to fix it. But off the bat, I'd say this did pretty good. Like here we have cloud Laravel and deployment as our tags. So I'd say it did pretty good shipping this app uh creating this app terminal no code editor no get installation no not even boost because it wasn't you not even boost. Oh man, if we can do it while on this live stream, you can do it because you saw the issues we ran into here. Um, definitely make sure it is using boost. I would like every prompt you give it, I would make sure it's using boost. And if you notice that whenever it's showing the logs, you don't see any tool calls where it's like saying something about Laravel boost, I would send a prompt again like are you using boost for this? Are you calling any doing any tool calls using Laravel boost? Because as you saw, you can ask it to create the application using Laravel Boost, but it doesn't always run the right commands. But if you are um if you are trying to do a gent coding and you are using a terminal or you you know what a terminal is, you're not as scared to do this in the terminal. I would also suggest getting started following this prompt that is in our docs because this I feel like is a very smooth experience as well. But this is definitely something you can do if you're someone who doesn't want to use a terminal. You don't want to open an IDE. You just want to use cloud code the browser or desktop application have a GitHub account and then use Laravel cloud to deploy it and test out your application. Let me share this. But yeah, I'm pretty proud of what we built even with Hannah running into token issues. Um I'm pretty proud of this little thing. Uh we can show off the different pages too. We have the calendar which I believe is empty but our notion integration. You guys will have to check back in. Maybe I'll keep um I'll keep vibe code on this and then report back to I think we do have a cedar for the calendar event. So let me do my um let me seat it. I'm going to go into where am I? Okay. I'm going to go into commands. I'm back in cloud. I'm going to go into commands and I'm going to do PHP artisan dbced and we are in production. So I'm going to do force and use the force flag here. I'm going to run this command because it did create a cedar. You can see here we have a calendar event cedar to create fake events for our calendar right now. Just so we can see what that looks like. Make sure it um like created everything fine. It at least has the UI details there. But we needed to run the cedar in cloud so that it is running that for our um database. And now if we refresh, we can see our lovely events. Nice. And then you could hit the IC to download it for the Apple calendar or you could hit Google here to add it to your Google calendar. man. It was a roundabout way of doing it, but we were cooking a little bit. I think uh Kazu Kazuhiro had a comment to just saying like it feels that insane just a couple of years ago getting to this point would have taken much longer. I think yeah, that's kind of where my mind's at too. Like it still feels like magic to me and I know there was not a lot of magic on maybe this particular live stream with all the little hiccups. But even with the hiccups, right, we've only been live an hour and 13 minutes. Part of that is talking to people and we built this full application. Like if I was building this myself, I could pro like I could do it in a day, right? Like within a couple hours, but it wouldn't be this quick. like half part of it too is you trying to do it running into like the token issue and then I took over at what like 40 something minutes in and we already have this full application 30 minutes into to building which is pretty cool and I tested and like let's say AI SDK um I was testing the different functionality here I wonder if it's type if I just do AI Okay. I wonder if it's case sensitive. Yeah. So, I type in AI and it's filtering it for what we actually want cuz we did use AI and Laravel wrapped. Yeah, those are all I was like, is it just giving us random ones? But then I realized we just have AI AI content. Well, it doesn't seem like anyone's going to probably quit their day jobs to move to um, you know, exclusive cloud browser coding, but I think a great use case for folks on your team that want to get started um, but aren't, you know, I mean, I remember when I was first learning how to code, I was like the terminal and ID, like there's all the different pieces you need, and I feel like this um, makes it just a little bit simpler to get going. Yeah, I think so, too. I think I would still personally prefer using um AI in the terminal myself, but I think it's really cool being able to do this, you know, like just be able to fully prompt it, not look at the code or anything, just do this within a browser and get a full application up. And I feel like it was fun regardless of like showing had a great time. Yeah. Doing this live. I'm going to use this in my day job. So, this was a selfish uh you know, ambition over here for for me. So, maybe I'll be back with my next project to do it with Leah. So, maybe not on stream or maybe you have me drive. Yeah. But does anyone have any questions? Does anyone have any questions about it or just like general things um you want to add as we start kind of like winding down to end the live stream? like is there anything uh any of the steps or prompts that you feel like weren't clear you want us to clarify on a little bit before we end stream or um questions about if you have co-workers or people are trying to follow this uh certain things that we could clarify for them or tips we might push back um in the meantime he was like who writes such nice blogs I know I think you've written like three blogs now um Anna at Laravel has really been cooking on all the different blogs. If you don't read the uh Laravel blogs, I would recommend you do because they're really good and there's been a lot of technical blogs technical blog post uh currently which gives more of an inside look into things at Laravel and different things as well. So, let me just show the link to our actual blog too which is laral.comblog. Um, there's a really good one on load testing recently that I think got published by Devon. Um, last week, but I would check that one out too if you're interested. The case. Yeah. Yeah. Yeah. Which you also tweeted about that one I think Saturday. Yeah. Gareth, I do really like Herd. Um, I use Laravel Herd and I do think for people who are trying to start out and want to set up a local dev environment, right? They don't want to just do the cloud environment stuff like Hannah and I showed during this live stream. I think Herd is a great way to start. I know if you run the prompt I think that is in our docs, um, I think it installs PHP and all of that to your own computer versus using Herd. But I think Laravel Herd is also a great way to get started with a local dev environment. I didn't want to go back to our app. I feel like we deserve some clap or something. A cheers. A water cheers over the Don't drop it. I feel like I thought I thought it was your water bottle when your dog filled out. No, she's in my lap um right now. Oh, Dave had a comment too saying um there's an excellent blog post from Pushback about how well different AI models perform with Laravel. So, I know that that was a topic of conversation. So, thanks for calling that out. Which Pushback, I don't know if you're also working on something to talk about like how to most efficiently use AI models and agents and stuff like that, like how to I guess get the most bang for your buck, making sure you're not like using a ton of tokens every time. But I know there were some people talking about that and I know Devro I think will definitely be trying to create more content around that too because it seems to be something a lot of people have questions about. I know it's something I want to learn more about myself too because sometimes I just prompt things and I could do it in a more efficient way. I definitely need to learn more about that based off my experience this week. Where is pushbox? When was the one about the different model? Oh, it's this one. Which AI model is best for Laravel? Yeah, that was a really good blog post. Yeah, we got we got claps in chat. Let's go. We got some claps. Thank you, Ama. Thank you, Dave. Thank you, Pushback. Thank you, Florian. Um, and Pushback said, "Use GPT5.4 Claude with Polycope is the best things ever." Okay, I'm going to try that. And we will be doing more live streams. Like I'll be doing more live streams with other people from the Laravel team who have built different applications who aren't like traditional developers, but they've been building applications using AI and showing how they've done it, whether they've used a terminal or different things. Um, and Josh Josh and I will probably do more streams of building applications on stream using uh AI agents and stuff like that as well. Thank you, Nubio, for the claps. Thank you, Chris. We got some validation. Maybe our next app will be an app that can monitor your token usage and alert you to when you need to switch models. Got it. It's pretty meta. It's a good one. We'd have to test it. Why? We know who to test it on. Um and here is the blog post that is the one you see on my screen right now for which AI model is best for Laravel. I've pinned the link right now. Um and then we do have that is the best question. how to use the lease tokens because I'm spending tons of money for topup. Yeah, and we got this Josh and I got the same question last week during the live stream for Instruct, which is a tool to provide UI feedback to AI agents. Um, that Josh Siri who is on our Devril team, he built that. So, we did a live stream showing it and we got the question on that stream and I feel like it's a really good question, too. is like I just said it's something I personally need to practice more of too of like the ways to use the lease tokens. Um, and then we do have a question. Maybe I'll say question. Before AI, we used to dig into documentation. Now, to be honest, I've not read even the boost documentation. Is it only me or you guys do the same? I actually feel like I read just as much documentation now, if not more. Um, because I maybe it's just a me problem, but I doubt AI's answers sometimes, especially if I'm just like prompting it for an answer versus like generating code. And so I will then be like, "Where did you get this from?" And then I'll look into the docs. Like if it tells me from the docs, then I look into the docs and I proof check what it gives me. For the code, I try to like if I'm not if I don't really like how it solves something, I'm not sure that's the best way, I'll look things up and I'll look into the docs and different things as well. Um, we have a question about instruct. What What's the name, please? Is it public? For instruct, yes, it is public. Um Josh Siri instruct. Here it is. There's um two packages. There's just the regular instruct one and then there's the instruct/ Laravel one which is fine-tuned for using it with Laravel. Trying to get to his instruct one. Okay, there it is. It's a general instruct package. It's mainly TypeScript. So here is the link to um the repository for instruct which does tell you how to install this and there's quick starts for the framework you want to use it with like for Laravel and all of this is here. Um if you go to Laravel one it tells you here how to get started with that and everything. So, there is that. And there's also a YouTube video um which is the recording from my live stream with Josh that we did last Tuesday, a week from today, um where he's walking through Instruct, talking about how he built it and then we're building an app from scratch using AI and using Instruct to give um UI feedback to the application that we built. So, let me share that link to that live stream. and it is right here. That is the link to the YouTube video to watch. I keep smacking my mic. I'm sorry. To watch the recording of the live stream with Josh. That's already happened, Leah. Or that's upcoming. Okay. That happened last week. And then Pushpack said, "We have cut down guidelines almost 40% now recently and routine maintenance going on to trim it down more." Which we love to hear Um, and then Najib was saying, "I use I ask AI instead of docs nowadays." I like both. I like to do both. What do you do, Hannah? Do you go to docs still or do you use AI like to ask questions? Oh, man. I mean, technical docs like am I going to the Laravel docs? Not that often, but I I do go to the docs a lot still. I just feel like go straight to the source or I have AI link me out to the docs so I can verify. That's how I am. Yeah. Uh Florian said, "Who's got time to read? We need to move at light speed and ship." I I like to read. Even docs, I like to read. Okay, so I think we're going to Oh, let me before we wrap up. Pushback said, "If you are not on updated version of Boost already, please do it." So yes, please make sure you're on the updated version of Boost. Even if you're using AI, you can say like, "Hey, please make sure I'm using the updated version of Boost." And update it. You could prompt it and it will be able to do that for you. Um, but like you said, they did optimization, so it uses less context. So, make sure you are on the updated version. But yeah, let's start wrapping up. Uh, thank you Hannah so much for being on the stream. I'm so sorry that it was stressful for you. Thanks for having me. you know, my first stream. So, it can only, like Florian said, it can only go up from here, I think, is where we landed. But thanks for everyone being so kind in the chat as we ran into technical difficulties, as is the way of these things. So, I guess one last I'm so proud we ended up with one last little proof. We did end up with a application. Yeah. And one that I'll be using. So, I'm gonna have to get the the cloud URL from you. So, and I did have ones from my other runthroughs I could have shown if I needed to. It seemed we didn't even need to, you know, but we didn't even need to because we were able to get an agile application up within what 20 30 minutes for this whole thing. And of course, we could optimize certain things by prompting to claude further. Um, but the whole point of the stream is more so just to show that you can go from scratch to having a full Laravel application without needing a terminal, an ID, a local dev setup or anything, which I think we did that. No mechanical keyboards required. You can do this. But we prefer you do have mechanical keyboards. Hannah's dissing me with I'm just kidding. It's fine. You work from home, you know. No two laptops, mechanical keyboard, uh standing desk. lots of important to be comfortable at your home office. Well, we did get if it helps because this is your first live stream. Florian said that was awesome. Thanks, Hannah and Leah. Najib said it was awesome. So, you did great. I got two awesomes. I'll take it. It's a win for me. And even on April Fool's Day. Yeah, this was not an April Fool's stream, everyone. Um although we did get some questions around that. So yeah, we did. That was our first chat. It felt like it a little bit at the beginning there, but we we made it through through the hiccup. We should have been like April fools. Um I guess Hannah, do you have any closing thoughts like about the stream today using AI to um build Laravel applications? Like any closing thoughts where people can find you if they want to find you off stream? Yeah. Um, you can find me on LinkedIn. I've got this crazy last name, but you can also just find me at hannaharabel.com. Um, happy to talk vibe coding, cloud, all the things. And I think, um, you know, one thing that I think is amazing about Laravel, but specifically about cloud is that you can click a bunch of buttons and get your app up on the internet, which used to be very hard to do. Um, and so it's a really easy process. So encourage your co-workers to try Laravel, to try cloud. Um, you know, I'll be I'll be do more in it, too. I feel like I've got more ideas now that Leah got me halfway there. And, um, I would say don't be tell your friends that might be afraid of using AI to code to, you know, the AI is not going to judge you. So, just give it a try. Um, and there's lots of help here, lots of people that want to see other people building stuff. So, let us know what you build. Yeah. And this live stream should show too that even though it might not always be the like most direct pathway like to making an application like using AI sometimes stuff can go wrong like you run into limits or it could like go a little off the rails. Don't get discouraged. Just try it again. Try again. And you can ask the AI, what should I do next? I feel stuck. I don't know where to go from here. Right. Um, so you can you can get pointers that way too. Yeah, because you can debug with it. You can give it a prompt and it can easily fix things. So don't get discouraged. You're I'll give you the same pep talk I gave us before we started, but you're doing great. You can do it. Just just don't get discouraged. Keep going. And it's really inspiring to see like what you can build. And hopefully you're inspired from seeing what we built in this live stream. Uh like Hannah said though, Laravel Cloud's absolutely great at getting something up and running. like we were able to use that instead of having to check locally what our application looked like. We just hosted on cloud. Even from the first step when it built a um application using the starter kit before we did the actual content library app, we put that on cloud and we were able to see right away each time it pushed up again and when it pushed up it would auto redeploy the application from the new um commit or like push from our GitHub repository that we deployed from. And tomorrow I'll be doing a live stream with Devon. It is our scheduled Laravel cloud office hour. So if you do have questions about cloud and how you can use Laravel cloud when shipping things using Laravel and AI, feel free to join the stream tomorrow. It's going to be at 11:00 a.m. Mountain time, so 100 p.m. Eastern time, which I think is 5:00 p.m. UTC, I think. No, because we started at 11, didn't we? It was 7 p.m. But that's I don't think Oh, for UTC. For UTC. Sorry. Yeah. Yeah. Yeah. Okay. I'm bad at time zone, so correct me if it's wrong. But that live stream will be tomorrow. It'll be at 11 a.m. Mountain time, 1:00 p.m. Eastern. It's Laravel Cloud office hours. We will have one of our uh project managers at Laravel on the cloud team who's also going to be a special special guest on this office hour session. and and is Andy and Andy will be talking about scheduled auto yeah scheduled autoscaling on Laravel cloud which we last week I think so he'll be talking about that and doing a demo so please join if you can and I'll see you there tomorrow yeah Floren said 5:00 PM UTC I'm not crazy okay so I'll see you tomorrow bye everyone thank you for being happy fool's day do not get fooled