Vibe coding is an AI-assisted development approach where developers use AI tools like Claude Code to generate code, manage databases, and configure applications, reducing the need for manual coding while maintaining developer oversight. This workflow involves using AI for scaffolding projects, managing database migrations, configuring authentication systems, and troubleshooting errors, with developers focusing on high-level architecture and decision-making rather than writing raw code.
Installieren Sie unsere Erweiterung an, um sofort in jedem Video zu suchen
🔴 Live vibe coding 3 web apps with Claude Code Typescript Next.js Supabase | Come say hi!Hinzugefügt:
Hello anyone. This is Anything. Today I'm working on the usual three apps. Uh what you see right now is Eco3D. This is a game where you can uh breed and raise dragons and then you can 3D print them as well. So this will be using real 3D models. As you can see here, these are from Saber 3D. Uh and then I'm mapping the models onto the animation skeleton.
Um, and so that's what we're working on here. Then we're also building um as anything.dev or also known as uh gazolo.dev. They're same domain or same website, different domains. Um, and this is currently what we're running into. So I'll be working on that. Um, in the last um session I implemented a lot of changes, but it's currently very broken.
So we need to go through and fix it. And then beep.buzz. Um, we're going to be doing a similar thing. In the last session, I also uh ran a large openspec change. It implemented all of it. Now, we need to go through and make sure it all works. I want to move things around, too. Right now, we have a crowded head uh header with three sections, and I want to remove this main learning screen that we have here, and I want to integrate that into the play screen. So, now we have a platformer that's a click to move platformer like this. Um, and we can interact with things. that these dudes here, these two characters will basically replace this learning page.
So, this was the landing page initially, but now we're just going to move around this world. There'll be other uh player characters in the world, so you can chat with people live and you can see them moving around. Um, but when we hit this talk button, it currently opens it up like this. I think I'll leave it like this for now, but eventually I'll have these um chat boxes actually sort of shown up in the game. So, it'll look like this, sort of presented in the game. Um, but I kind of just want to do some bigger picture stuff first, like moving things around in terms of um having it on the landing page here, the actual game on the landing page, making some of the uh the graphics a little bit more kind of Dolingo style is what I'm leaning towards. Um, and just cleaning up a few things. Uh, this is basically the the AI's oneshot of this process. So all the changes that you see here is just from my description and then the AI has implemented it. I also thought that we could add a jump animation. So right now we just have left and right movement, but if we click up above them um then we can jump. When you tap on the character, it actually taps the MOS code that you if you hold it down, it does a dash. If you tap it does a dit. Um and then it's now processing as a word and sends it up as a message like that. But I still want to improve that UI. So I want to think about all that stuff. Um, and yeah, I think that's the overview.
So let's get started. Um, what are we working on first? Still getting used to There we go.
Okay. Um, so beep.buzz. What do we want to start with? I'm thinking we can start with gazol.dev.
We should be able to um select the project and then deploy. So, we can go superbase uh npx superbase um link. And I'm actually just going to move this off the screen real quick just so I don't show my other uh the names of my other projects. I have a couple of client projects on here. Doesn't really matter, but just like to keep some things uh mysterious.
So, I just want to connect to uh as consol.dev.
And now we're linked. So now we can do a db push npx superbase db push and that should push all of the migrations that we've just recently added. You can see down the bottom here we have an error that was from when I attempted to sign in. Um okay, remote migration versions not found in local.
All right, so we've got a deviation between the two. We can ask Claude to help out with this. It's probably just going to be um hopefully it's just going to be like a naming convention, but we can also reset the database um depending on what migrations we have in there at the moment. So, let's open up the migrations, see what we have. We only have like uh these five. So, what I'm going to do is I'll ask Lord to review what's currently in there um and then ask for its advice. So, rather than just telling it to sort of resolve it, we'll um catch up on what's going on. So this chat has a summary of the changes that we implemented. I compacted it. So I'm going to continue it from here. Yo, thanks for voting. Um, okay. Interested in as anything. So that's actually what we're looking at right now. It's also called gazola.dev.
Um, okay. So I'm getting this error when I try to push try to push.
Oh, by the way, I'll bring the hand cam back soon. I'm going to get a another webcam. So, I'll have the camera on the keyboard, which I think will be a cool touch. Again, uh I'm getting this error when I try to push the migrations.
Uh look at the migration history and uh tell me if I should reset and give me a concise summary concise summary of the changes.
Uh do you think I should reset I should just reset the DB.
It's probably what we'll end up going with. I've actually got to paste that error in there. Okay. Um, and as like a quick uh reminder of where we're at with this one, um, this is gazol.dev here.
There's my face up in the corner. So, the idea is that it'll be like a Vibe Code coaching app or a Vive Code companion, whatever you want to call it.
Um, so I'll have this little dude, this little me in the corner, um, speaking the words on the screen. So, it's not going to say everything, but it will like be a transcript speaking of, uh, of what it is. So, this sort of explains what it is. It's basically a way of uh, teaching people and helping them to build their own web apps using the stack. So, it's going to be like u a scaffolding process. sets it all up for them, connects them with clawed code, so you're not locked into something like Lovable. Um, and then you link your uh GitHub repository. Currently, it's trying to link because it thinks it's authenticated, but we need to figure out why it's not currently authenticated.
But once you are uh set up, it tells you how to set it up if you don't know. Once you've set up your repo, you link it and then that will uh give the app a connection to your actual code and allow it to detect where you're up to um what you know process, you know, what you need to continue. Um and I also have a little chat thing here. We're going to implement this where we have an AI secretary uh that's going to be able to answer questions about how to use the app. But then if you want to chat to me directly, then you get some free credits and you can chat send a message to me. The idea is that it gives me me and the app a bit of insight into your project. So you're not building the thing alone. Um it's kind of like halfway between Lovable, which is really sort of hands-off, uh does a lot for you, and Claude Code. So, I'm sort of trying to fill that middle ground. Um, and that's what we're working on there. So, I just wanted to give a quick overview. I don't know if it's boring, but um, that's what we're working on. All right. So, uh, I'm going to actually change the model here so it's a little bit more autonomous. Going to go with, um, auto mode. Just tell it to continue.
Um, and yeah, so I'm going to come back to this after it's thought for a while.
Basically going on to auto mode means I don't need to keep hitting enter. When it's a very simple request like this, like I'm saying, just summarize what's in there. Give me your opinion. Um, then auto mode's pretty safe. And from my experience, auto mode has been pretty safe in general. Um, it uses the AI to make a judgment call as to whether the action is good to go, whether you can just hit enter. So it's not constantly asking you to um accept the changes, which means that you don't just kind of go into autopilot and hit accept for anything either. So it's even safer in some respects. So for beep.buzz um I want to remove just uh just going to show you where we're at with beep.buzz. So we have the visual reference. If we go back to the homepage, I want to remove the uh play from here.
Oh, sorry. I want to remove the learn.
Have this on the left. That's the default and that will be the home route.
And we're going to remove all of this from here and make sure that all of this UI um yo, thanks for voting, whoever that was. Thank you so much for subscribing. I appreciate you. Um uh yeah, welcome and thank you. So, we're going to remove this. We're going to make sure all this UI is in the game when you actually interact with Beep or Buzz. Uh and then we're going to remove that endpoint. Move the game to the home screen. So, let's do that now.
remove the uh learn tab from the main tabs in the header.
Uh the game should live on the home route, not on the game route, not on the game route.
Uh, make sure that all of the UI from the current home routes is in the dialogue.
Um, in the dialogue for the interaction that shows when the user interacts with people Buzz in the game.
All right. And I'm going to do accept edits on that. Um, it shouldn't need to do any actions. So, I'm not going to switch over to Opus so that I can use auto mode. Uh, I don't think it's going to, you know, stop me stop too much process there. Um, also, thanks for the for the vote. That's two votes for the vibe code coaching. Nice. Um, no one here. Welcome to the chat. Uh, hi. I like when a coder gets limelight. Nice.
All right. I appreciate you being here.
Welcome. Welcome. Um, are you a vibe coder as well? You working on something?
Um I'm hoping to to make an app that might help people like yourself if you're uh building things yourself.
Okay. So um migration summary. So I asked for a just an overview of the migrations that it had already applied and then whether or not we should just reset everything just to sort of catch up with the state of the app. I've made a lot of changes um recently. Okay. So all have RLS and per user policies yada yada. Why the error? The remote has migration. So it has a migration applied that doesn't exist anywhere in the git history. I think it's totally safe to reset because I have split it off into a persisted um dev branch of the superbase database. Um so it should be fine to reset, but I just want to get my bearings here. Should we reset? It depends what's in there. Nothing's in there. Uh option one, repair history.
Okay, we're just going to reset. So let's go. uh npx superbase db reset linked. And I always get nervous when I do this to make sure that we are in fact linked to the correct database cuz I think I got burnt once by this. But we did just recently link and we have the uh the reference here. And I'm just going to open it up in another window just to make sure that it is in fact the right project reference. And it is.
And we'll check cuz I'm nervous. And we can hit reset.
Um, no one here. Uh, no. I'm a generic system designer and coder and yes, I use tools but only 25%. Okay, nice. Yeah.
So, you're more using AI as a support um support mechanism for your work. Do you find that you spend a lot of time still uh like hands-on, you know, working with raw text files or is it like how much has AI encroached into your working? Because for me, like I in the last stream I opened up a text file for the first time in a while and I was like, damn, I have not programmed raw code in forever. It's like very very automated for me now. Um, which is, you know, bittersweet. I spent a lot of time learning how to learning the language. Um, but it's also way way faster, way easier, way more productive.
And the boss likes, you know, the boss wants AI. So, uh, okay. Um, we reset.
So, we can continue. Uh, it applied fine. There were no errors in the reset process. So, now we could have a different response. Let's restart the server. Uh, we might need to clear the GitHub um user accounts uh because I think we might have a stale user now.
So, I'll open that up in a different window if I need to do that. Okay. So, uh we're getting separate errors now.
So, this is a build error. So, I'm going to copy this and I'm going to tell it to uh fix all the build errors. I'm going to use a different chat window so that we can I always type collude uh open a different chat window so that we can separate the context. The context for this one is specific to the bigger picture of the changes that we just made. And this is now fresh context that we can use just to do a very simple targeted fix. Um, and I'm going to use auto mode for this because it it will ask for a lot of permissions, but it's not doing anything drastic. So, I just want it to keep going. Um, so I want to say run build and fix any errors like the one below.
So, that'll run the npm build script.
Um, that should do a global TypeScript check or a type check. Um, no one here says, "I always have to read files and then plan and while I use AI to find bugs and root fix and then plan." Okay, nice. And while I use AI to find bugs and root fix. Um, also, what are you working on? I'm working on three apps at the moment. So, what we're focused on right now is gazol.dev.
Um, so let me bring up this window. This is beep.buzz.
Uh, this is gazilla.dev. So, this one that you're looking at now is also known as as anything.dev. I should get the naming consistent, but um it's basically going to be a way to link your GitHub account. I sort of mentioned this before and and then it will help the person to develop using that GitHub repo with claude code making a web app uh with Nex.js and Superbase. So, it's basically just extending what I'm trying to do here but into an app. This one here is eco3d.shot.
Um, so here you can see the the kind of skeleton animation that I'm working with. And then I'm using um 3D dragon models from Saber 3D uh to then overlay over that animation.
Currently it's a little bit jerky. Like you got the legs the the legs are the worst part. Everything else is pretty good though. In the last stream, we fixed a lot of bugs getting things to align properly. So, it was rotating weird and stuff, but now it seems to be pretty good. Um, we just need to fix the legs next. But the idea is that um I'm going to have many different models, 3D models, excuse me, of dragons. And then the user will be able to um like I don't know if you played those fish games where you collect fish and you breed them and then you get fish eggs and you have to get rare fish and they sell for different money and all that stuff. It's that kind of thing except with dragons.
And the hook is that you can actually 3D print these dragons. So if you get like a super rare rainbow cyber dragon like this one, then you can order the 3D print. I'll print it for you and send it off. So that's the other one that we're working on. And then yeah, beep.buzz. This is a Morse code app. Um I'm now converting it at the moment from its original state. Um which was kind of just a chat app and then like a flat Duallingingo style interface. I'm converting it now into a platformer. So it's click to move. So it'll work on a phone. Um and when you tap on the character itself, it sends Morse code. This will be a multiplayer like an open multiplayer thing. So you'll actually see other characters moving around at the same world as you and then you can chat with them directly using MOS code. Um and so these are the teachers here. You can click to talk to them. It opens up the full um chat. This was what was the original learning thing, the original like core of the app, but now it's inside the game. And then you have enemies. So, if we go over to this chest as well to get hearts and stuff, but this is an enemy. So, if we walk up to this dude, we can attack them by trying to use the the shape that we need, which is just a a dit. And as you go up in levels, it will be like say this word, say this uh sentence, and then it will attack the enemy. If you get it wrong, you might die and go back to the start. Um, and so we built this in the last session. I had wrote up a spec before and then just ran the spec in the last session to put it all together. Um so it's very very fresh. Uh we got a lot of bugs to work out. Um but it's gone pretty far. Like you know the door's working. We can open the door with a DI. Um and they're the three apps I'm working on and I'm going to continue focused on them for a little while. It took me a while to to choose which apps to work on cuz I've got all these project ideas as I'm sure many of us do.
Um but this is what I'm going to focus on. I think they're decent ideas. Um, hey, thanks for saying hi. Um, did you do something called prompt engineering or something to work with AI? Um, yeah.
I mean, I guess I I am a prompt engineer now, you know, like I I was just a straight programmer um, you know, for many years. I taught myself full stack web development. been doing that for about seven years and I've now just sort of transitioned into uh into what I'm doing now which is you know you can call it vibe coding you can call it whatever you like um yeah so I'd say I'm a prompt engineer more than anything now I barely look at uh um you know code raw code anymore and if I do I look at it through the lens of the AI ask the AI to tell me what the code is doing and stuff like that um which is weird it's a new build.
Um, okay. So, before we do anything in gazola.dev, as anything.dev, uh, I'm going to wait for this to fix because that will unblock us from getting these errors in the console and we can actually just, you know, rule out some bugs before we start trying to like layer on other fixes on top. Um, okay, we've made some changes at beep.buzz, I think, to keep it interesting, we can do some work at Eco3D.
And what I want to do first is uh create a spec. So this is going to be a pretty big change. I'll probably end up doing two different um chat windows for this. I'm going to create a spec to implement a authentication process um right now only for admins so that we can put all the configuration stuff, all the animation design, all the 3D model assignment um in the back end and then we can have a front end where you just see the dragons. so we can actually start creating the game. Um, but as I'm saying that out loud, I'm thinking that we could leave the signin stuff to later and we can just move the game to the front end and then clean up the studio and then add authentication later. So, I'll probably do that. Uh, no one here says GitHub and that 3D visualization game is the best idea you got. Nice, dude. All right. I appreciate that. 3D visualization. Okay, cool. Cool. And the GitHub one. Nice. Yeah. Beep. Buzz. Uh the other the third one um I think is kind of an interesting low barrier of entry thing just like to I might end up sort of dropping it but I find three projects is a good way to keep momentum going in the streams keep it interesting. Um so I'm going to say review uh the current state of the homepage uh and the studio.
Um, so I want to move those two. I want to combine uh I want to remove most of the animation stuff uh because we don't actually need it. Um I I want to simplify it. So let's actually bring it up so you can see what I'm talking about.
Um okay. So, we have this all this stuff right here. If I refresh the page, we'll get that dude back up. All of this is kind of useless. Now, this was ways of setting how the character looks. So, we can actually add more legs. You know, we add these legs at the back. It kind of looks crazy. And we can make them uh make the segments longer like this. We can make the uh segment count longer so the whole thing's really really long.
But all that's useless now because we're assigning a 3D model. Um, and we're using this studio. I'll show you this studio in another tab. This is how we actually assign. Let's load in one that we've done before.
So, we don't need to determine the length of the segments. We don't need to um calculate how it's going to move or anything. All that should be resolved from how we assign the 3D model to the animation skeleton. Um, so I want to remove all that stuff. All this is now useless. And I want to combine this animation page into this studio so that we can just basically click a button and see an example of how this will move. So I will use I'll have a look at the UI and I'll just think about how we can do this. So currently we have two stages.
All of these are models and you can actually see this right now at Eco3D if you're curious. You can go through and click all these different models and see what they look like. So you select a 3D model of the dragon and then you go after you've selected it, you then do the segment grouping which then it's a little bit painstaking. You go through and position the nodes and you tell the skeleton where it's actually going to line up. So that's how we can get these to be the right length, the right position to fit the 3D model. So we need a third step. Uh let's add a third step for the animation. Uh, I'm going to add just wondering how we can add it to the UI. So, we've got the this is all that stuff.
Save at the bottom. Um, yeah, let's add it as a third stage. Right at the bottom, we'll have a button that says um continue to animation.
Uh, after we've saved all this configuration, and then that will bring up the equivalent of this um, which is what we see when we assign this dragon.
And then we'll start fine-tuning what we can actually do on that animation screen. Um, and then on the homepage on this page right now, I just want to see uh I guess just an example like what we have now of this dragon and eventually it will be multiple different dragons.
It'll just pick a random one. So that's what it'll do for now. All right. So review the current state of the app and the studio. Um I want to so let's say add a animation step to the studio flow.
Um there should be a button at the bottom of the note assignment uh with the label uh animates. I think that's good enough for now. We can always tweak it. That should continue the process onto the animation step onto a third third animation step.
Um the animation step should only contain should not contain um should show the should animate.
I actually don't want to bring in the existing like the black background and everything. I want to have this dude, this kind of animation right here in this screen. And then I want to be able to switch back and forth and it goes between being still in place where we can position the nodes and moving around. Um, okay. The animation step should yeah animate the uh model in place.
So in the current um scene in the current scene um without yeah at the moment what should be in the actual sidebar uh and then switching back switching back to the other steps.
Actually, we'll just keep it simple. Um, the anim in when in the animation step the uh sidebar. So, what do we actually want in there?
Should not contain. Saying what it shouldn't contain doesn't make a lot of sense. We should just say only what it does. Um, so let's have a look at the current version. See what we can salvage. What's actually useful. We don't need segment count. Don't need segment length. Um, stiffness.
Stiffness could work actually. Let's like attach the dude and see if Let's refresh. Get the model in here and let's see if stiffness actually has an effect.
Does it impact?
because I don't know if any of this is actually I think that when you apply the model it just like locks in all the stuff as much as it needs to because limb reach you know that doesn't make much sense cuz the limb distance is set the step threshold could be a thing but I don't think these things are applied so I think actually what we'll do is I'm just going to leave it open-ended for the AI to decide and then we can come back and tweak it. When the animation uh when in the animation step, the sidebar should contain only the UI that will have an effect on the um dragon animation when the that will have an effect on the dragon animation.
For example, the current uh animation UI from the homepage includes a lot of settings that aren't used.
Um, and then we can just say eg segment length is not a factor because that is controlled by the node placement.
um in the previous step and we can actually include another few in there. Uh for example, segment length and um number of segments uh number of nodes are not a factor. They're not factors because they are controlled they are controlled by the node placement in the previous step.
Um yeah. Okay. Uh we're just going to do accept edits on that. Not the auto mode.
And let's move on to the next thing.
Okay. Gazilla.dev. Has it cleaned it up?
Looks like it has. So it's fixed the error. Let's restart the server and try it again. And we're just going to try and see if we can sign in. See if we can link a GitHub repo. Um, and yeah, I think I think I agree uh I agree with you. No one here. Um, that those two are probably the best ones.
Um, you can say it doesn't affect the model when Twix. When TWEx You can say it doesn't affect the model when Twix. I don't know what TWX is or T-wex. T-Wex sounds like um a dinosaur like T-Wex. Uh, but I don't know what you mean. Um, but thanks for chatting, dude. I appreciate you being here even though you say no one's here.
Okay. So, it is still trying to sign in.
Um, but we're going to fail to load these repos and it's going to fall back.
So, this will time out. Yeah. Then we fall back to the default state. So, the authentication isn't working. Um, it might be on GitHub side because we need to remove we need to like purge um the old users like as we're developing and it's separate to the user cache at superbase.
Okay. Um, so let's fix that error. I can I'm just going to close this chat window. Now, I kept that as an aside because it kept the context for this chat clear. So, this chat is the like has more context about the app that we're actually the changes that we've recently made, the larger picture, what's left to do, stuff like that. Um, so we're still getting it looks like the same error. So, I'm going to put this error into here now, now that we can rule out all those build errors that were fixed in the other thing. So uh I tried to sign in uh to GitHub using the link account button in the uh main wizard flow.
Wizard flow not button button. Uh in the main wizard flow uh I got an authentication error.
I got an authentication error. Um then when returning when refreshing the page uh the connection times out and it falls back to the um initial do you have a GitHub account uh stuff stuff um do you have?
And I get this error.
Um no one here says uh I mean I mean last two or three lines in your prompt that will make AI to implement all of the tweaks you have like step size or more. So that was this prompt in Eco3D.
Uh let's see.
Uh for example, the current animation UI for the homepage includes all the settings that aren't used. Eg the segment length and number of nodes are not factors because they are controlled by the node placement in the previous step.
Um we'll make AI to implement all the tweaks you have like step size or more.
Yeah, I I think I'm with you. Um, so you can say it doesn't affect the model when tweaks.
Yeah, I think I'm with you. Um, are you sort of saying that by ruling these things out, the AI is going to intuitit or interpret what is what sort of remains that will be useful um to use uh when the model is assigned to the animation skeleton. Um, I think we're on the same page, but uh hopefully hopefully it does pick up on that and it knows what to keep in and what to cut out. Um, we'll see how we go. All right, so it's got back to it. That confirms that the migration never ran. I think it's wrong about that. Let me check the O call back so I can flag. Okay, the O call back does it in this order. All right, so before assuming uh so we'll say use the superbase MCP.
This is a huge one. I'll probably say this a few times. you want to use the superbase MCP. If you're working with superbase, set up the MCP. Um, and same if you're working uh set set up the playright MCP too uh as well so that you can get it to visit a page. You might need to authenticate for it, but then it can actually look around the page, click on things and understand what's going on, take screenshots and stuff like that. The other one is Trigger is a really useful MCP as well if you're working with Trigger. Okay, use the Supervis MCP to look at the migration history.
And before I actually tell it to do that, I've got to check that we're actually authenticated.
We don't actually have it in here. So, let's go plugins and let's go superbase.
What's going on? There we go. I guess it's just install the user scope. We want to install for Yeah, user scope.
Um, no one here says, "Uh, these are tricks I personally use because I always use free clawed web and for bug projects I can only prompt only once. So, I have to make sure uh so I have to make some roundup that will work." Yeah, that's prompt engineering, dude. Sounds like you're a prompt engineer yourself. Um, I recommend getting Claude code if you can. I think it it requires the pro tier. They actually tried to remove it from the pro tier. They tried to make you sign up to like a higher tier, but they've got it back in there now. Um, and uh, yeah, it's definitely worth integrating it into your actual IDE. Uh, I used to also go back and forth between the web and uh, the terminal or the web and the interface, the IDE. And it's just so much better to have it built in so you can tell it like look at this file, grab this, do that, and it's worth the expense, I think, if especially if you're working in the field.
Um, so it looks like we've got a UI issue here.
Um, let me just try MCP. See if it's installed.
Superbase. We want plugins.
Reload plugins maybe. Have we got it now?
Plugin. Superase. Superbase. See if this works.
Um, allow.
That should open up. Is it opening up in this browser? Yes. And it's fine that you see this. Okay. Let's authenticate uh organization to grant. I don't really want to show the organization list. So, I'm going to bring it up over here.
And we want it to be this one.
Okay. So, let's try it. Now, this is a new um user that I've set up just for streaming. So, I I still need to set up some things like this.
Okay, so we're connected. Um, let's try it now. Uh, let's send that prompt again.
We didn't send it. So, uh, use the Superbase MCP to check if the migrations were applied.
I'm confident they were.
They were. Um, I reset the DB.
Um, no one here says I'm a 19-year-old student and I have I I don't have money.
Yeah, that's fair, dude. Um, yeah, and if you can leverage the free tier, if you can use the web and do some clever prompt engineering to to get what you need, then it's definitely, you know, massive, massive help. But when you do have enough money even just for the minimum to get Claude code, you know, you can justify it by thinking about the work you'll get, you know, how it'll help your job prospects and stuff.
Um, even if you just tried for one month, like I'm not I'm not trying to shill, you know, I guess I kind of am promoting Claude Code a lot. It's uh it's a big part of my my whole thing I'm doing here. Uh, but it's just like gamechanging. It's the kind of thing now when chord codes, you know, goes down, if there's ever a period of time it goes down, I just find something else to do.
I don't even try and continue working um because it's that, you know, makes that big of a difference.
Your uh V2 migrations did not apply.
That means that I've applied it to the wrong database. Um I applied it because I linked Superbase to the database. So I wiped the main DB which is fine. Um but it's because I have a development branch of the database.
So I have a development branch of the database. So I can't remember how I manually I think you got to pass the project ID.
So I'm going to just keep it up in a different window so you can't really see what I'm doing at the moment. But I'm just getting my dev database up and I'm copying the uh project reference from the dev branch of the same DB. And so I'm going to tell it to use the project ref uh flag to reset that. So I reset the main DB uh by mistake. I'll say not a problem because otherwise it will probably start to try and fix it. Not a problem. Um, I want you to use npx superbase uh db reset. Actually, let's just see if I remember the command. The only reason I ask it to do it is because I don't remember the exact syntax, but I think I think I do. npx superbase db uh reset and then we want project ref and then that I think npx be reset project ref. And I just got to check that we are in fact on the right database. I always double check this stuff.
Okay, that looks good. Uh yeah. All right, let's try that. It's going to give us Okay. All right. So now I'll send it to it. Say like this is what I'm trying to do. Can you make it do it? Um, I want you to to use that um with the project ref to reset it. I tried doing it here.
Okay, once we reset that, then we can rule out the superbase side of things and then I might just need to figure out what's going going on in GitHub if we need to change the application settings cuz we have a GitHub app configured.
um for this project. I'll ask it to tell me what to click and stuff as well to find it again in GitHub. Um okay, so two issues with that command yada yada. The command you want is no.
See linked uh linked only resets the main DB. I need to reset um the uh dev branch which is the project ref I shared. I'm going to tell it to search the web uh search the web to find out how to do this using the CLI. I think I can actually get it to do it. I'll do automate for this. I think I can just basically delete the dev branch and create a new one. But that will change the project ref. And then I need to change the env set up in Doppler. And I don't want to do that right now. I do want to do that later. I'm going to change it to be an ephemeral rather than a excuse me, a persistent branch. Um, same thing. Uh, one time by mistake I wiped my whole DB then I have to build it from scratch. Yeah, we've been there.
We've all been there, I think.
um it's like once bitten, twice shy. So now every time I go to change anything with the database, I'm like, is this the right database? Am I doing the right thing? Um the database is like it's also like a good opportunity with work because um people need someone to like protect data. If you're working with AI and people are like, you know, they think that sort of programming is cheap now, you know, it's not really that important to have a human in the loop, that's fine as long as you're working just with code. If you're working with data, like I was working with a client that uh was scraping a lot of auction data for um cars and vehicle sales and um it was just like you had to keep that. You had to change the database, change what it's doing. But they spent hours and a lot of uh a lot of time, a lot of API credits to get all that data in there and you have to preserve it and not not even corrupt it when you're changing the way that you manage it. Um so it's a good kind of area to focus on moving forward with AI I'd say. Um okay so the answer there's no superbase branches reset command but linked doesn't mean main it means whichever project you're currently linked via superbase link. So the trick is to relink the branch. Okay, awesome. So we link to the project wrap. I did remember this. I did remember this. I've forgotten because the main project I'm working on at the moment uses um automatic branching. So when you create a new branch and you push a PR, uh you open a PR, it will automatically provision the database um the development branch of the database and then link it to it. So then when you merge back in, it automatically uh pushes those migrations. So, I'm a little bit rusty, but this does make sense. We're going to link it first with superbase link, and then that's where we pass the project ref. We're linking it now to the development database branch, not the main one. Uh, so we've linked, and now we can do the DB reset again, but without the project ref like that.
And then we just go d- linked. So, we've now linked to the right one. That looks good. Okay. Uh, and I'm actually going to say add that to the claude file if it's not already there.
Um, now system design and security is the main thing, not coding. Yeah, totally. Totally. And it's a little bit daunting because you need to like have enough work like the there needs to be um enough for you to do because some a lot of the times you the design of the system doesn't take that long and then implementing takes the time and anyone can do the implementing side of things.
Batman, how you doing my guy? Welcome to the chat. Um it was good to chat with you today about your new project. I'm very excited to take a look and get into it. Um, thanks for voting as well.
That's another vote for um the for as anything.dev five code coaching and that's what we're working on right now.
Um, but yeah, welcome dude. It's good to have you here. Um, and I'm excited to hear that you're working on something that you're interested in. Um, and I'm interested to to be involved.
Okay. Um, so we, so that's just expanded the claw.md file to then update um, the reference. So then next time we don't forget how to reset.
Okay, we didn't it didn't work. Um, npx superbase db resets links superbase is not in the registry. So this is different. This is about calling ah I spelled it wrong.
supervase. So, I'm actually wondering if it would have worked before when we tried this reset because that was the same error that was caused by my misspelling.
Well, it works this way. So, let's try it this way. Uh Batman says, "Man, what are you doing? Long time no see in live." I know. Um I've been busy. Uh I got a I got an hourly job. I'm still doing freelancing. Um, but I've been doing a lot of a lot of professional this, you know, the same stuff I'm doing here, but getting paid um for a startup.
It's been fun. Uh, but a lot to keep up with. Uh, and now I've also figured out my sleeping pattern. So, right now it's past midnight, but I'm like taking a nap in the afternoon and stuff so that I can still be up uh to work during the day and then um do this at night. Uh, and what time is it for you, Batman? By the way, I was just wondering. Same with you. Uh, no one here. I'm just curious what time it is because I'm also thinking about time zones and for the audience and all that stuff. Okay, so we've reset the DB. Uh, now we can try let's reset the development server and let's try uh see if we are signed in and if we're not, try signing in again.
By the way, Batman, I don't think you've seen the kind of redesign for this. Um, this is the new look um for as anything.dev. Uh, I'll be taking down the current site uh soon. Okay, nice.
That's perfect, dude. Um, 8:33 p.m. in Nepal and 8:18. Awesome. That's perfect.
That's exactly the kind of uh time zone I'm going for. That's like peak, I think. Uh, so sweet. Very very cool. Um yeah, so the way that I'm going to do this app um Batman is basically you've got me chatting away at the top left a little video and that will be explaining the text on the screen. It'll be writing in um and basically what we're doing is we're creating a vibe code companion. So it will create the skeleton, the scaffold for your app and it will connect to your repo and monitor your repo and basically give you advice on how it can be uh restructured and changed to you know follow the the best latest not necessarily the best but like the latest practices that I like to follow. Um and then you can hit chat and you can chat with me and I can see your repo. Um, and yeah, we can we can build an app together. It's the idea of this.
So, I want to try and link. So, let's link this account. This is currently not working. I think it's still not going to work, but we're just troubleshooting why. Okay, sweet. So, now we can install and authorize the app. Um, we're signed in as me. Um, okay. So, this is the new permission screen. This was added in the last uh stream. Um, basically just telling us what the app can do. Um, we want only select repositories. I mean, let's just go with all repositories, but I actually thought that I think we're going to have two selection interfaces here. One is the permissions of which repos we can select from in the app. And then when we go back to my app, we have the option to say which app which repo are you working on right now. So, the only permissions we have are read access to the metadata and read and write access to the code, which is pretty heavy.
I was hoping it would phrase it as like PR only. So, the idea is that I'll open a PR and you can decide whether or not you want to merge it or not. Uh, read access to the email address. That's fine. Let's give it a go.
Uh, use my mobile.
I don't know if this is bad actually.
You're seeing this. Oh. Um, I don't think so. Surely not.
Well, it's approved anyway. It's still in development. So, okay. So, now let's see if we are somehow connected here. Let's go to profile.
Okay, we're connected. Um, let's see if we've got any uh errors in the terminal.
I don't know if this is a fresh error.
Um, no active repo. Okay, so that's fine. That's just saying that we haven't yet linked a repo. So, let's ask about the context for that. Um, I also just want to reduce it back down to Sonnet just to save a little bit of credits here, a little bit of tokens. Um, and just say, so I've linked to GitHub. Um, how do I where is the UI?
Where is the UI in the app for selecting the repo?
Um, uh, no one here says, "Did you create a git repo for the GitHub project? I also want to see the codes."
Uh, yeah, I I don't know if it's in the description. Um, it should be. I'll add it uh before next stream if it uh if it isn't. But yeah, they're all public. So, each of these three repos are are public. You're you're welcome to submit a PR if you think that it's that if you have any suggestions then you're free to make changes. Um this is one time thing so no problem. This is one time things no problem. Um I'm not sure what you mean there. Uh Batman says and about the project we talked earlier. Uh I give it a look and you can absolutely vibe code and commit.
Sweet dude. Uh yeah I'll open PRs. I think I like to kind of, you know, give you the the last say about whether you want something in the app. Um, and we can set up a system that can uh do a preview deployment for you, too, so you can actually see what it looks like before it goes in. Um, but yeah, I I haven't had time to read your uh PR. Um, but uh I'm looking forward to it. I plan to do it tomorrow and uh yeah, and I'll sort of also keep an eye on the state of it as it goes, as it grows. And um yeah, awesome. I'm excited about it. The repo picker is in step two of the wizard. It appears automatically once you've authenticated. All right, so let's go back to the setup. I'm going to need to change this like cuz right now we it's still asking, do you have a GitHub account? But we've just connected it, so obviously we do. Uh let's try refreshing because I think this is an error. Yep, it's failing to load the repositories.
So, we're It must be this error that we're still getting.
Let me see. No active repo. That's a chicken in the egg error, though, because we're trying to select the active repo. Um, and it's not letting us. So, it shows the loading spinner uh for a moment, but then falls back to the um do you have do you have a GitHub account screen?
Uh this error in the logs.
Oh, that's not the error in the logs.
Copy this like this.
There we go.
Um, as per your time, G. Uh, also I am planning on buying Claude code. Shall I?
You shall. I mean, I suggest you shall.
Um, get the the cheapest version that allows you to use Clawude Code. Um, and just give it a go. you know, you might want to try uh try other models, try other agents, agentic workflows, but in the end, chord code is definitely in the lead in terms of just usability. And uh once you try it, it's one of those things where you don't want to be dependent on something, but it's just like being dependent on the internet. I think it's just so critical.
All right, so it thinks that it has the solution here. Use scaffold progress runs unconditionally.
All right. Okay. Yeah. So, it is a chicken or the egg. Your user repossess is empty because we haven't selected a repo yet. Um, so the fix is to gate it on having an active repo. So, if we don't have an active repo, it's not going to tell us that not having an active repo is a problem until we've actually set one. So, that stops the 500. Now the real problem, your user repos is empty because the install call back ran before migrations existed.
You need to re-trigger the GitHub app installation.
Go directly to your GitHub app install URL in your browser. Um, so I want to check your theory first and I always like you got to identify that it has theories and then it presents them as fact. So it thinks I'm trying to clarify on what what happened and what it thinks happened. So, I reset the DB then linked the GitHub uh linked the GitHub account.
Uh does that does that like mean your theory is false?
Is false because it might not. I'm not exactly sure what it's referring to. Um yeah, it looks like a lot of people are saying uh as anything.dev should be the focus. So I'll I'll stick with this one for now. At least while we're on a roll.
Uh, good point. Let's let me check what's actually in the DB. Yeah. So it's going to see that that we've applied the migrations. The table I think is empty.
Let's actually write this. I think the repos table is empty.
Uh, I need to ask what it would mean for it to be empty.
I didn't see any step uh in the in our app to select the repo.
Does that is that why would that be why the repos table is empty?
Is this a chicken or the egg?
Uh, chicken chicken chicken chicken or the egg problem problem.
So, I'm signed in via oorthth. Um, but the GitHub app installation never completed. Here's what happened. After oorthth, we went to the call back. It checked for the GitHub app slug.
Okay. If it's not there, it redirects instead of the GitHub installation page.
The install page is where the repos gets saved.
Um, okay. That nullifies what I'm about to ask here. And I need to ask something else next. Um, Batman says, "Do we have any free alternative for claude code?"
Uh there are there's an open- source one. I forget what it's called. Um but it's actually pretty decent, I think, but it's just a a noticeable step down. And then you can decide what model you use.
So you can use a free model with a free open source agent, and you can have the same effect that you see here. And it's they're they're pretty good. Um and I think they're going to get better, especially since uh Claude Code's source code got leaked. Um, Codeex as well. Um, I don't know if it's free. Uh, but I haven't really tried Codeex very much.
I've just focused on Claude Code.
Anti-gravity. That might be what I'm thinking of. Um, good call there. Uh, no one here. Um, so, uh, confirmed you're signed in via O. Uh, the O user exists, but the GitHub app installation never completed.
So when you say say it never completed um for that GitHub app slug if it's not set it redirects instead of the okay yes so let's say first of all yes the slug is set um I have created the app when I clicked the link account button it redirected to the uh app installation to what I think what I think is the app installation page um where it showed what uh privileges where it showed what access was being allowed and I clicked to authenticate the app the app.
So, did it do the thing?
What am I missing?
I don't know. The last two sentences are probably counterproductive.
Um, Batman says anti-gravity is too slow and takes too time, too long. Um, I use both. Uh, they reset the limit every week, so it gets the job done. Um, yeah.
I mean, if it's free and slow, then, you know, do like take your time writing a prompt and then wander off and come back because if it's doing the same thing effectively, if the actual quality is there, but the time is the issue, then it's definitely, I'd say, worthwhile, especially if you can do multitasking, if you can use like uh send off multiple prompts for different things that you're working on. Um, cursor I think specifically is a harness and so it you you plug in other AIs into that harness.
Um, and I don't know how agentic it actually is. I haven't I've done some research with cursor and comparing it to the to claude code and stuff and it doesn't seem to satisfy the same requirements that I need. Um, but a co-orker of mine is trying it out and and they think it's pretty good.
I think it's really good for pure vibe coding like if you really aren't very technical or you want to like stay away from the very technical stuff but um claude code's better for the other side.
Uh no one here says use anti-gravity for scanning and generating a plan and use codeex to implement it. In this way you can work weeks and you don't and you won't hit the limit. Nice. Um, and for complex tasks, use anti-gravity claude.
And for cursor, uh, is not recommended because you can use only two times a month or a week. Okay. Yeah. Yeah. And they're starting to clamp down like um, GitHub Copilot has uh, stopped receiving new users and they are limiting the capabilities of their models. I mentioned earlier Claude Code tried to limit uh tried to remove Anthropic tried to remove Claude Code from the pro tier which received huge push back but they're now like reaching their cost limits. They they've been running at a loss like Netflix was and so now we're going to start the the initification. I try not to swear on stream but um okay so the in the install flow looks correct in code. The critical question is whether GitHub actually redirected back to this. Okay. Check your dev server terminal. Did you uh get a get to this? Let's give it a go.
Actually, I'm just going to copy.
Let's not copy the whole thing. Let's see here. Um, this was when we're refreshing post request gets refreshing.
Not seeing anything.
Invalid request. Error. Invalid request.
Okay. This is useful.
Okay. So, we can send this.
That'll be what we're what's stripping us up. Invalid request.
Yeah. Otherwise, I don't actually see a call back. I think we just got redirected back to the homepage with uh the error in a query parameter.
um go back to here.
So I don't think we got redirected back to the uh or call back.
I think it went back to the homepage with this query param.
I think these probably multiple these query params.
Yeah. See this is the home route slash and then we've got a question mark which is the query parameter um marker.
Yeah. So invalid request error error code is bad oorthth state error description. The oorthth state parameter is invalid.
Okay. So I guess that means it probably is on the GitHub end of things. So we'll get it to tell us what to do in GitHub.
Um, okay. As I'm leaving now, carry on and uh and yeah, do give a look at our project. We I definitely will. Thank you very much for dropping in Batman. Um, have a great evening. Hope you sleep well. Uh, and yeah, I look forward to working with you on your project. Um, yeah, catch you catch you next time, dude. Okay. Um, so while that's thinking, let's catch up with Eco3D. That's doing a type check.
So I think that means that it's finished working on it. Let's have a look at how it turned out. We should have So this page shouldn't be that changed, but what we did was we moved we added the animate stage. So, if I now hit animate, then it still goes to the black background. It's actually frozen.
Let's refresh.
Okay, it's properly frozen.
Okay, so it looks like it's it seems fine now. I think it's the black It looks like it's overlaying I'm going to close this because it's going crazy.
Um, it looks like it's overlaying the previous animation scene onto uh on top of the node placement scene.
Um, bye dude. Uh, I don't know if you're still here. Um, no one here says I also do the same thing. I take a nap in the afternoon so I can work late at night.
Yeah, cool. What am I drinking? This is peppermint tea. I don't know if you can see it. I forget where my camera is.
Bump my microphone. Peppermint tea. Uh, it's all I ever drink to be honest.
Peppermint tea all day.
It's pretty like vanilla of me. It's not very, you know, it's not exciting. If I drank coffee, I'd be awake all night though. Um, by the way, I hope it wasn't too loud when I bang the microphone. Um, yeah, that's cool that you also do bifphasic sleep. Um, I find it it really helps. uh you know get a little bit more out of the day as well rather than just kind of getting more and more tired. You get that extra that second win, the second half of the day.
Uh okay, before I go back to gazilla.dev, I just want to finish my train of thought with Eco3D. So when uh I continue to the animate screen, uh the performance drops dramatically.
We don't really need to say that. We can say it looks like the animation scene is overlaying the node placement scene and we can say causing a drop in performance.
Um, I basically I want it to look like uh look like the creature the dragon that we just placed the nodes on.
the nodes on in the node placement states placement step starts moving starts animating moving animating in the same scene uh scene no background no black background um Oh man, I absolutely love peppermint tea. Uh you're drinking for digestion? I mean, I guess so. And just in the sense that like if I drink anything else, I get like, you know, sautami. Um sometimes I drink ginger tea, but I like to have tea all day. And if you drink too much ginger lemon tea, I at least I start to get like dehydrated. Um I start to feel like, you know, I guess like I've been drinking lemon juice. It's probably because of the lemon. I don't know. Um, but yeah, it's the one drink that I can just drink all the time. Um, and I like I like consistency.
Bit of a strange one like that. So that error means GitHub redirected back to your homepage with the oorthth params instead of the call back. So superbasis's client saw the state param on the homepage and tried and failed to validate it as the oorthth state. So that means it's not redirecting. I think it's got to do with the call back uh URL configuration in the GitHub uh app configuration. So we actually need to change it in there. So the issue is in GitHub settings, GitHubs apps have two separate URL fields. The callback URL and the setup URL.
Okay. So the setup URL is this. Oh, you know what? It could be which um are we at 3,000? Okay, we are at 3,000. Uh if it was at another one, it could be a problem there. Um okay. So all right. Um also check the redirect on updates checkbox. Uh, I want it to tell me, so give me uh concise and specific instructions on how to navigate to these to these uh configuration options in GitHub and what I need to change change and how to do it.
Um, I don't know if you're still here, Batman. Um, but I you are uh Yeah, I uh Oh, as is it okay to ask you for your Insta? Uh, we could connect on there, too. I don't really have an Insta. I think I technically do. Um, but I just I don't really use any social media, so I can I can give you my Discord uh and my email. Um, but that's that's pretty much it. I I'm not a real social media dude.
But I was going to say, um, it would be cool, uh, potentially once we get the project going, if you'd like like it to be on stream, I can do some work on stream on it. Um, and like, yeah, that could be fun. Uh, just something I was thinking of. Um, but yeah, happy to chat mainly on Discord is the main one. Uh, but yeah. Okay, so github.com top right avatar. Okay, here we go. So, I'm going to I'll try and do it quickly off screen because I don't really want to share. I might move it onto the screen in a minute, but just for a lot of this stuff. Settings. I'll try and keep this off the screen for now.
Uh, okay. Developer settings at the bottom.
And GitHub apps.
Okay.
And then we want click the edit next to your app.
Uh, okay. I think I'm there.
Um, scroll to the post installation section. Sorry if this is boring content. Um, all right. See you, dude.
It was awesome chatting with you and uh I look forward to working on the app.
Um, catch you next time. Okay, so homepage URL, callback URL. Okay, it's currently pointing to the Superbase one redirect URL superbase.com project authentication the setup URL I don't know if it actually I think I can show this on screen now but we've only got that's start out I think this is fine to show you on screen Uh, we have the private key showing here.
Okay, I can't show this on screen. Let me have a look. Setup URL optional. Uh, unavailable when requesting our during installation.
Okay, I'm just going to Ctrl A and Ctrl C everything on the screen and say I'll paste uh everything on the settings screen, app settings screen from GitHub.
Uh tell me what to change.
Okay. And I'm not going to scroll up because I think if I scroll up, you might see a private key. Um, call back URL field under there.
Uh, we want to set it to this call back URL.
Callback URL is currently set to this. I can share this. The call back. Yo, welcome back. No one here. Uh, glad to hear you're still here. Um, not the bullvac, the callback. The callback URL is set to this.
Um, I thought that was correct. Yo, Egg, welcome back, my dude. Um, who's your favorite uh py man? Uh, who's your favorite pie man or Java lava?
I don't know either, my guy. I'm so sorry. Who's your favorite pie man or Java Lava? I don't know. I feel like it's it's something I should know. Uh but welcome back. I also wanted to say last time um you were here, you mentioned that you were you watching in the early days from, you know, 20 to 100 subs. Um and yeah, I just I really appreciate you jumping back in. Um yeah, it's cool to have you here. Longtime viewer. Okay, so I thought that was correct. Um did I copy something else or was it just that? No.
was correct.
The callback URL should be this apparently.
But yeah, I thought that it should go to Superbase and then Superbase should come back to Yeah. So that should be as is. That's for the Superbase Oorth Exchange and it's right. The only thing missing is the setup URL. Okay.
Uh we should do this. Okay. I don't really understand.
It says optional.
Uh, it says this optional and I can't copy that.
Unavailable.
Unavailable when requesting oorthth during installation.
Um, uh, who's my favorite? He's saying Python or Java. Um, yes. Okay. Personally, I'm a Python guy.
Okay. Nice. So, I'm either a Pyman or a Java lava. I think that's what it means.
Um, I'm Python. Uh, but really I don't know.
I don't know much about either. I'm I'm like was always Typescript through and through. And now I guess SQL. Well, not just now, but SQL as well. But even more so with AI like you can write any amount of SQL you need. Um but yeah Typescript would be my answer. Uh Python I think would be my second choice. It was always like something I was looking at to study when I was learning uh JavaScript and Typescript. Um but yeah how about yourself? Are you a Pyman or a Java lover? Um and no one here is a Python guy. So like me or at least you know I'm a Typescript guy.
So that check box uh request user authentication or during installation um is checked which is the problem.
Okay.
When it's on GitHub ignores the setup URL and redirects post install back through oorthth to superbase to the superbase call back which then fails with bad oorthth state because it's a second oorthth attempt with a mis mismatched state. So uncheck that.
Apparently during installation the setup URL field will become available. Uh check redirect on update.
Okay. And then we want to paste that in.
I got to admit I'm not 100% clear on exactly why, but I'm just following the following the AI lord, the the boss, the digital the ghost in the shell.
Um, so let's save.
Okay, so do I need to delete the user on GitHub before attempting the sign in again?
the sign in again.
Um, Egg is a is a Pi guy, too. A little bit at least. Nice. Nice. Um, awesome. Uh, have you built anything with Python or are you a programmer in general? Have you been making stuff? Um, always curious to hear what projects people are working on. No, just try link account flow again directly.
I don't know if that'll work because I'm already linked, but let's try it. Let's go back to here. That's beep. Buzz. We want this one. So, let me try disconnecting.
I don't know if this will work.
Okay, I think we're disconnected. It's also clunky. It's like such a work in progress, but let's see. link the account and now it just goes straight to GitHub.
And why is what page is this?
Goes straight to GitHub and it gives us it basically shows us that we're already linked.
That's kind of strange. It's already got the access all repos um and then gives us the opposite. Okay.
So, I think we do need to reset it, but I'm just going to confirm that first cuz all Okay. So, uh when I disconnect and then click click link account again, it just redirects just redirects to the GitHub setting page for my uh account for the app in my account. So, it's like the perspective of the user that signed in that's linked to the app looking at the app settings in GitHub.
Um so h the only thing that matters is that after the oalth completes see we've already authenticated when I hit disconnect I don't know if it's the same as signing out um no one here says at the time uh of start I show so when you started you chose Java but then uh when you did some research uh I know AI is best at Python so I started in Python. Um, but now I'm using AI to write Java or Rust code for UI while you maintain in PI. That's a lot of languages. Um, I think it's really good to be flexible with languages now, especially with AI. I don't think it's too important anymore. I think it used to be like a real life choice. Uh, what are you going to spend all your hours getting really really good at? Um, whereas now uh it's more about what kind of systems will you build? like where will your specialization be in designing these systems and what will you tell the AI to write so rather than what will you be writing but what will the AI write for you is kind of the new question okay so that's because the GitHub app is already installed so that's what I thought since you enabled redirect on update you can trigger the redirect from the settings page on the GitHub app settings page you're on find the repository access section. Yep. Um, make any trigger or change. Toggle all repositories to only select that repository. Click save. This will update that, redirect you back to that.
All right. I mean, it seems clunky, but I mean, the only thing that we can do is select a specific repo. Uh, let's just go let's be meta and let's choose um let's choose the one that we're actually working on right now, which is gazola.dev.
Okay, save those changes. That should redirect us back.
Should redirect us back. And then we got uh problem.
We got a problem. Let me bring it up for you so we can I can show you what's going on.
So uh we got this URL.
And what did that do? So, error on the redirects, but it seems like we're making progress.
We now have that loop. Um, we're getting redirected back to the site.
Also, by the way, I stream for about 2 hours. Um, I'm going to try and be here every every day would be ideal, but it usually ends up being every other day.
So, probably not tomorrow night, but the night after. Uh, and uh, yeah, I stream from midnight, uh, Melbourne time to 2:00 a.m. It's about 1:30 a.m. now, so I might start to get like less, I don't know, less alert, but uh, I'll try and keep my keep my focus, keep my energy up.
Good news, the redirect worked. The error is in our check.
It's failing because you triggered it via GitHub settings. Save. Okay, well, that's a good sign. and fix the install call back to skip that when it's an update action. All right, nice. So, I think that we resolved it. So, after this is fixed, we should be able to refresh the same page. Let's try it.
Okay, maybe not.
Let me uh make another change here.
Let's uh go. I thought we'd change it to all repositories now, but let's now save. Change it to a different repo.
Uh we'll just go with Eco3D.
Save. Redirect back. Missing installation ID. Okay, we got this. But a different error is always progress. Uh this error now.
Oh, actually before I just throw it straight back in, let us start again. Let's go back to the local OS 3000 and try and trigger it from the start because it might be because it was a stale authentication cycle.
So, let's go link. It's going to go back to the settings page rather than the fresh um installation. We need to make one change. Let's go all repositories.
Hit save. Now the redirect back should work. It doesn't. Okay. So, of course, it doesn't. Now, go back to the app settings page. Click save again. It should redirect to this pass validation um error. Again, I know this isn't the most, you know, interesting stuff, but um my idea is to be less focused on like high quality, you know, engaging content and just to kind of show the whole process of creating these three apps. Um, and uh I'm just going to keep going, try and be consistent with the amount of time I put into these things and then show the whole process.
What error shows in the dev server terminal?
Good question.
This error. Missing required environment key. Oh, what? GitHub private key. Okay, that's weird. Uh, I'll copy this, paste it in, and it's going to tell me what I already know. But I'm just going to go to Doppler. Uh, I keep all my keys and secrets in Doppler. I recommend using it. It's a good good system. Um, this is where it should be. So, I'll just be able to search in here. It should be in the dev environment.
And we want GitHub.
We got the ID and we have the private key in there, but there is a trailing underscore um GitHub app private key.
Yeah. So, it's just because there's a trailing underscore. So, it's a formatting issue. So, I'll save that and apply to all of the environments.
Doing it in in the off screen just because I I don't want to show you my secrets. Um, okay. So, let's try it again. Let's go back once more.
And we want to go back to just the local host and do the same cycle.
The other thing that's changed with AI in development is that I find that I'm using having more of a QA role. You know, even just in like the the classic way of uh I don't really want to share too much of this like many of these. So, I'll just pick the first one. Yeah, it's more of like quality assurance. Like you're just trying things, giving feedback to the AI, reporting on bugs, describing the bugs, saying what's working, what isn't. Um, yeah, it's not as nice like programming used to be a lot more like specialist and expert, but you know, okay, still good to have have work to do. I think that what I need to do is actually reset the dev server so then it gets the Doppler envir again. So before we send that off, let's try it again.
Let's go back um clear off all of the endings and just go to localhost and try it.
And this time we'll change the setting again. And the redirect should work. all repositories. That's a setting we want anyway, you guys. You guys. Okay, so the error might be different though.
Uh, okay. It is different. So, it's now getting the key, but the key is in the wrong format, it seems. Um, so I think I added the key, but I might have added it incorrectly.
I added the key, but I'm getting this error.
All right. And to switch things up, I'm going to switch projects. Let's have a look at Eco3D and see if it's now uh working. Before it was uh hanging. I think because it was trying to overlay one scene on top of another. And I think we're at 3002. No, 3001.
All right, let's give it a go. Head over to the studio.
And then I'm going to remove that whole animation screen. Oh, yes. That looks good. No, it doesn't. It's frozen already.
And I can hear my PC.
my PC rev like a jet engine. So, uh, something's going wrong there.
Yo, Egg, uh, I use JS, Python, and HTML.
Nice, dude. So, your Python be mostly backend server logic. JS would be the front end logic, I'm guessing. Uh, but I run them on Pi.
You run JS on Pi? So, I'm guessing you are using Flask. Okay, nice. Cool, man.
I'd be interested to see some of your projects. Um, okay. So, that looks good.
That looks good. But there is a performance issue.
There is a performance issue uh when the dragon is animating in the uh studio page.
Uh yeah, the browser lags heavily heavily.
Um, don't just try to fix uh look at the difference between the code the code in we'll say the existing code no the code in the homepage that handles the same thing and consider the differences in the logic and the context. text um of the two implementations and help me figure out why one is working but the other isn't.
Um my PC specs are actually decent now.
I actually don't mind sharing them now because uh I previously like I was on a backup PC for quite a while, but I just recently um got my main PC working um because the power supply unit was busted. Busted. It was broken. Um but yeah, so I'm using this.
Um, so it's a the graphics card is a um GeForce 3060.
Um, and the processor, yeah, it's a Ryzen.
But yeah, so it's very like it's kind of power hungry and it runs very hot, but it's quite it's also getting a little older now as well. Um, but I think I bought it when these specs were like it's kind of they're still competitive. I I feel like computing, you know, we reach the end of Mo's law, at least mostly. We're starting to plateau. Um, so yeah.
Um, I don't know if that's still considered good, but it does everything that I needed to do, and it's so much better than my backup PC that I've been working on for so long.
Um, okay. So, Um, which version of RAM? I don't know.
I I don't remember. Uh, there's a better way to check the specs, right?
System information.
Uh, here you go.
Sort of like struggling to keep the screen.
I don't know if you see the RAM.
I don't know if this is like I'm I'm sure this wouldn't be sharing like anything too sensitive.
I don't know where the RAM like spec is though.
I don't know. I'm not a hardware dude.
No task manager. Um I don't know if I want to bring up task manager if that's what you're asking.
Uh, I'm just like I don't know what's actually contains potentially like stuff that I I shouldn't share on stream. I think the specs are fine, but if I open task manager, I think it'll just show the processes that are running. I don't think it's a problem, but let's give it a go.
Um, oh, are you asking like what is absorbing the RAM?
Um, GPU VR RAM.
Yeah, I'm sorry. I'm not a I'm not like a a a specs dude. I just know programming.
Um, RAM. RAM.
I don't know, y'all. I feel like I'm failing here. You tell me what to click, I'll click it. But yeah, I'm not too sure what you mean. Uh, GPU, VRAM. Oh, it's 12 GB.
Uh yeah, 12 GB VRAM on the GPU. I think that's I think that answers your question. The version of RAM.
Uh how do I find that? Can I find it from what like what I showed you? Yeah, dude. I I don't know. Uh it's a I can actually ask Claude. Um, what version of RAM is in the GeForce 3060?
64 gigs of physical RAM.
So, that's Yeah, that's the physical RAM on the computer.
Uh, and this is what GeForce does. Click performance.
Where is performance?
Uh, do you mean like search performance in like click performance where in which UI?
Yeah, I don't know. You'll have to help me help you on this one.
Um, okay. Well, I I think like that might be the best I can do at conveying.
I don't know if it's if it's any good, but yeah. Anyway.
All right. So, in task manager, I think he's saying something like DDR5 or DDR4.
Okay. No, I think I get what you're saying. Uh task manager, you want to click performance.
Uh, one of these. This one performance.
Um, and you want me to check memory? I'm guessing I think this is what uh form factor DIMM DDR5 or is this uh am I doing it? Is it happening? I think it might be happening.
I don't know. Let me know. Let me know.
Okay. Uh, the GitHub app regenerates private keys in that format, but Jose's import.
I guess that's the name of the package.
Expects this. Let me fix the code to use nodes thing. All right.
So, handles that and that. Okay. So, that's the package problem. Let's try resetting. I don't think we actually need to, but I'll reset the dev server.
Move it to the side. I can't see the DDR.
Move it to the side. Let's try bring it in like this. No, can't see the DDR.
Which side?
Um, so I don't know if it's on this side or if it's on this side. You mean?
Uh, I don't know where the DDR is. Like I'm not good at any of this stuff.
Um, create private key from the Okay, so this now should be fixed. Let's give it a go.
Let's go back.
What we do here is go back and let's go. Uh, yes. Yes.
Try and change the setting again.
Uh, it's DDR4 RAM.
Okay. It's kind of like, you know, when they lift the hood of a car and they're like, "I've got a twin thing. It goes real fast." And I'm like, "Cool, man. Looks shiny." Um, let's just connect to Autodev and then hit save.
Yeah. Windows 11. Um, it's measured by speed not written Windows 11. Yeah, I should probably Yes, this looks good. Here we go. Confirm Next.js and TypeScript.
Okay, clude code prompt. All right, so this is a this now means that we've connected.
This is the next step in the process.
Um, I don't really want to think about this. So, I want to think about how we've connected and how to check.
Here we go. There we go. Okay. So, it's automatically linked to the one that we selected. I do want to be able to like we need a a button in the profile page that will actually enable us to change these GitHub app settings, but for now, I'm just going to leave it connected to one account. That's good. uh basically a smoke test passed um that we are able to link to the GitHub repo.
So now we can start checking the other stuff. Um and then once we get an idea of the whole flow, we can start to actually improve it. But I just want to do an overview. Uh if I hit check step verified against your repo.
I'm kind of interested to see how this check is working. Let's actually ask Claude about that. Okay, that's connected.
Uh, I'm at the check the I'm at the uh confirm. I'm at step three.
Step three of the wizard.
How does it check? Uh, how does it perform the check when you click the check button?
So I think that all it really does is check the package probably and just do like a GP um to see if it contains uh Nex.js.
Um by the way I think you're on u Mangaro I think Egg. Would you recommend that? Uh should I change from Windows 11? Um if um if uh Clipana No, that's Batman. Um I can't remember the username.
Starts with a K. If another user was here, they would say to to use Arch. Um Kamar. No.
Ah, I can't remember the name. I'll remember it in a minute. Um, here's exactly what happens when you click the check button. Okay. So, uh, plain language basically it gives you like the code version. I just want to understand.
Yeah. So, it reads the package JSON from GitHub checks that the next is listed as a dependency. Um, I thought it was also checking something else. Yeah. So, next.js with TypeScript. Um, does it check TypeScript at all?
TypeScript at all.
Um, just the next six chips. Okay, so we need to fix that, but that's okay. Um, Koma. Koma, I looked it up. Uh Koma is an Arch Linux fan. Uh and they would they would want me to join Arch. I think um you'd recommend Menaro uh Egg, but I I'm actually considering Arch. I just need like a time when I have like room to change these things. Time in my life to transition to because at the moment I've just set up the PC again.
Okay, so the next step is installing the core dependencies. Um, no one here says I use Ki on my laptop and Windows 11 on the desktop because of app compatibility compatibility issues. If not, then I would probably use Ki Linux. Okay, nice.
The other thing is gaming. Like I I like Steam. I have a few games on there. Um, and I still want to be able to use that, but I think you can do that on on Linux now. Um, I'd need to look into that.
That would probably probably be the one thing holding me back that and just the transition you know changing to a new OS uh install core dependencies. So the next check so basically we we go through this process of aligning your repo with the the ways that I recommend building the app. And it's kind of like a a gate system, gating system to make sure that I'm able to like make informed suggestions and like and help with the development. Um, okay. So, we're going to install these peer dependencies.
So, it will check if it already has them installed. So, because this is a repo, this is actually checking the current project that we're working on right now.
It's checking this um gazola.dev or as anything.dev. It already has everything that we usually set it up with. Um so give me the plain language version of what is checked in all of the checks in the wizard wizard.
And what else do we have in changes by the way?
Few fixes and claude MD change.
Okay, so we check that next.js is on there. We check that we have tushand and that one, but it doesn't check all of them. Um, we need to make sure it checks all of these things. But before we even do that, I want to just like, you know, go through this part really fast and just see get a feel of where we're at in this app in general.
Um, so we check shad CN, we check the boiler plate, make sure that the initial page exists and doesn't have all of the placeholder stuff. Uh, we make sure it's connected to Superbase. Um, make sure there's a claude file. MCP.json, that one will be interesting because that can be kind of annoying to set up.
Basically, we got to make sure that we keep that up to date. Openspec. Okay, nice. Um, so I'm just going to go through and run each of these checks.
I'm not going to think too hard about any of them. I just kind of want to blast through. We're just making sure.
So the app page doesn't exist apparently. So this check is failing, but we can still progress. So I'm also just like learning.
I think in the future what I'll do is I will make these checks stop the progress. So you can't actually continue until you uh align it. So each of these prompts is meant to be passed to your AI agent and then you push the code to the repo. Then this app will check the code and make sure that it is aligned. Um and it'll just be that sort of you know an informed and opinionated companion kind of thing.
Um, uh, no one here is almost a full stack AI developer and mid-level cyber security. Nice, dude. Cyber security is a good field to be in for sure.
Okay, clude.md skills. Uh, we want to write this to the repo. So, it's doing a write without actually reading anything.
And if I do hit write, what does it actually do?
files written to your repo. I should have asked. Okay, so um for step, which step is this? Eight.
Four step eight.
Uh what actually happens? How is it writing to the repo?
To the repo. Does it create a branch?
Uh, does a branch slash PR?
Does it write to main um use blackbox backbox? I'm not sure what backbox is. It writes directly to the default branch via the GitHub API.
No branch, no PR. It uses put file which calls the GitHub uh contents API and creates a commit directly on whatever branch. All right. So technically uh we are linked to this current repo that we're working on right now.
So I think that it's just written the claw.md file and the skills. So it could have overwritten.
Uh so what I'll do is okay. So, I've linked the app to the to this current repo, current repo, and I clicked that button.
um pull the latest changes and look at the git history and tell me if it wrote a commit and if it did what the commit contained. Commit changed.
Uh because that's not cool to be honest like to just write straight to the repo.
So this is something that we're going to have to update. Uh, but we're getting to the end of the stream here. So, for now, I'm just kind of doing a scouting mission to just get a sense of what's what's been completed. It has mostly followed the spec that I wrote out, but it's deviated a little bit in its execution. Um, by the way, uh, thank you to whoever else subscribed. Um, I think we got two people that said they subscribed today.
So, that's really cool. Thank you very much. Um, really appreciate it. MCP configuration.
So again, this is just going to hit right. And we have paste your Superbase ref below.
I think there might be a smarter way to link Superbase to this app as well, so that they're not copying and pasting. I want to like remove any need for the user to go copy something like figure out where it is. We should be able to link it somehow and then grab it a little bit more easily. Um, but that's something to to bridge to cross another day.
So, this we need that to set up the MCP settings.
The other thing is that I probably won't have I don't know. I'll need to think about this and I don't want to write this cuz it's going to disrupt the MCP settings in the repo. So, I'm going to continue.
And then finally, we have initialize openspec. It's going to check if we have openspec in the repo already. We should uh but it doesn't look like it's working. So, it's another bug to fix, but we'll continue on. And that's the end of the opening workflow. So, I'll just explore the rest of the app.
Okay. So, the idea is that this will give you insight into your repo. It'll be like a bit of a map. So, it's like halfway between looking at the files, looking at the codebase, and uh conceptualizing like you'll actually see it laid out. Um, it won't be like a web builder. It's kind of halfway between the files and a web builder where in the builder it's way abstracted and you just see the pages, you see the results. I want to expose a little bit more of how the pages are organized, um, how the functions are implemented, what the database structure is doing, uh, how to configure the theme. A little bit more technical but not too technical. So I want to be halfway between there. So app workspace. So this should be showing us the app directory.
Um not exactly sure what it's saying here in the model and present in the repo.
Okay. Unbuilt planned. So we got no routes here. We got home here.
And these are unttracked segments and about. Oh, you know what it is? Because we're currently on a uh a new branch.
This is a branch called V2. And so it's not looking at the current state. So we only have the segments page because this is this is showing the previous version which looks like this.
This is the live version right now.
Um and uh by the way, thank you to the subscriber that subscribed. Um and so it's reading this version. Uh, that's what we've basically linked here.
And I'm going to have to figure out what's going on. I just want to skim through for now.
All right. And this is where we've got the theme configuration.
It's a lot more detailed than the current version.
And this is showing too much code. I want it to be more UI focused. The database.
Okay. So, it's actually reading the database. I'm guessing this is reading from the type file that's generated from Superbase, which is a pretty good way to go.
Uh, but this is good. It's actually scaffolded now that we can authenticate and see what's going on. Um, that's a good starting point. I think that's where I'm going to leave it here today.
I'm pretty tired now and I'm coming up to 2 a.m., uh, which is my wrap-up time.
Thank you guys so much for watching. I don't know if he's still here. Uh no one here in Egg. Uh but I really appreciate you guys chatting. Um and uh yeah, thanks to Batman for jumping in the chat earlier as well. And uh you guys might see Batman's project on stream at some point in the future. And uh yeah, that's where I'll leave it for today. So uh my name is as anything and as always oh hang on uh no one here says blackbox is not prominent. I mean not that efficient to work with on large scale.
Uh it only works till 25 files uh reliable after that but it makes it worse. Uh reliable up to 25 f files after that it makes it worse. Um anyway I'm going to head off. Um, thanks for chatting, guys, and I'll see you in the next one. Bye.
Ähnliche Videos
She Lost Her Car... But We Still Helped Her!
RecoveryBoyz
129 views•2026-05-30
Deadly Got Talent Auditions You Should NEVER Try at Home!
gottalentglobal
5K views•2026-05-29
Cozy Cottage Jazz | Warm Morning Cafe Ambience 🌸
villagejazzhouse
846 views•2026-05-29
DeBoer Wants Alabama Tougher, Texas Tech Calls out the Texas Longhorns | TNR 5/29/26
NextRoundLive
2K views•2026-05-29
Smart Working Techniques for Faster and Safer Jobs Part 54✅ #construction #adamrose #workers
worksmart-98
2K views•2026-05-29
LIVE: Move Into Friday with Special Guest Ed O'Brien | Morning Becomes Eclectic
kcrw
778 views•2026-05-29
On Bended Knees - Jekalyn Carr (Official Live Worship)
halalafrika
7K views•2026-05-29
Black Hills To Badlands In A Nova Bought SIGHT UNSEEN-Going To Towns Tour with HUNDREDS of CLASSICS!
ViceGripGarage
52K views•2026-05-29
