OPENCLAW Full Tutorial From Scratch | Set up, Security & Use Cases

It's been about a month now since I started playing around with OpenClaw, and I haven't had this much fun in a minute. So, I wanted to make this episode to pretty much share with you everything I learned so far, from properly setting it up to all the security measures that you might need to be aware of. Cuz even though it's easy to install, there's a lot of information that you actually need to be aware of and also fun use cases for it. I personally hooked it up to Blender so it can like take screenshots and it can like export me GBs. Uh I also hooked it up so it can also send you PRs to your own project where you can review and merge it yourself whilst also keeping everything secure. So if you're interested in that, I think you will. It's it's a lot of fun. Trust me. Let's get into it. So what is Open Claw? I get this question a lot. Isn't this just like Chad GPT or cloud code? But there's quite a quite some big differences here. So when you use Chad GPT, right, you open up the browser, you go over to chatgpt.com and you send some sort of request, right, text form usually or audio message and it's pretty much just you send a request, you get a response back and that's pretty much as far as it goes. And that response can be either text back, right, video or or images with GPT image. But that's as far as chat GPT goes. potentially it could also reach out and do some tool calls like maybe crawling the web to give you better accurate uh responses but that's pretty much it. Now when you go over to an agent like cloud code that can now run stuff in your terminal it can boot up you know and run mpm rundev boot up a node application or move files and delete files but you are in control. Now where open claw takes this further is that this runs 24/7 now this runs on a different computer that has full access if you want right you can give it full access to do whatever to create a GitHub account for itself to connect to the internet download images run blender so you're pretty much giving the LLM full control over that machine to see kind of what benefits you can get out of it now we are going to talk about security throughout this whole episode because there's a A lot of things to keep in mind. The funny thing is this post came out recently where the AI safety director accident accidentally allowed OpenClaw to delete her entire inbox, which is hilarious coming from an AI safety director. So, we'll kind of go in with an approach of of not really giving it any of your personal information. I think that's kind of the big no no that a lot of people end up doing. and it's like I'll just connect my Gmail to it. So, where should we run Open Claw then? Well, our first option is to run it locally on our computer. And please, please, please don't ever do this cuz you're probably signed into your all your important stuff from Gmail to having, you know, really important files on your computer that could potentially get all wiped out. So, please don't use this on your local uh machine. Now, the other option that you have or you probably see a lot of people do is use something like a Mac Mini. And that's really good because now it's a separate device. It can run there. The downside is that you'd have to keep it running 24/7 and it's quite a big initial investment uh just just for this, right? Just to try this out. So, this is something that you can look into in the future if you want. But what I really recommend for you guys is to just do a VPS. You can get a cheap VPS. you can just install it there, mess around with it. Even if the thing blows up, whatever, you can just close it down and then initiate a new VPS. So, it's the most contained way you can run this. Now, and I'm also thankful that I've been partnered up here with Hostinger to give you a really, really good deal on their uh KVM2 and KVM4 deals here. And they also have a one-click open claw setup which is super super cool. So I'll leave a link in the description for this if you go to Hostinger/develop by Ed. And this will work on the KVM2, KVM4, and KVM8 plan. So for this one, it will be enough with this one for me. The KVM2 that'll be plenty. It has two vCPU cores, 8 gigs of RAM, 100 gigs of MVME. That's plenty for this case. So, if we go here, as you can see, it auto deploys to your VPS. Now, I will actually show you how we can add it after the fact as well. Uh, even if you don't add it here through this link, and you can do the 12 or 24 month plan. The coupon code that I will give will work on both. So, that's developed by ads. There's already a coupon applied here, but I have a special coupon on top of it that you can add, which is developed by Ed that gives you an additional 10% off. So, check this out. That's for 24 month month months. Uh, that's 180 there. Uh, that's pretty crazy. If you want to do 12 months, let's see how much that would be. Like just 95. So, super duper cheap. And that's with the ready to use AI here, which gives you credits and they automatically work. Well, I will actually take this off because I'll show you how we can set it up with um our chat GPD key, our subscription. Uh so, you don't actually need this. You also have something like daily auto backup if if you know things do go really wrong and you want to have the ability to revert. This is an option too. And then you want to pick your uh basically your closest location here for the server. And then you are ready to go. Whilst we wait for this, you can also head over to the settings tab here and go over to SSH keys. And I added one here. Uh this is actually my laptop, so I'll need to add a new one. And to simply get this, you can head over to your terminal. You're going to say cd into your ssh. Let's do an ls there. And we want this ided pub.pub. Okay. So, we want to copy the contents of that. So, you can do something like cat uh id ed25519.pub. And that's going to give you that. So, I'll make sure to copy that over. I'm going to paste in my SSH key there and say main PC here for the name. Uh if you don't have it, you can generate one using SSH key genen like that. And then you just simply pass in your email address and you are good to go. So I'm going to hit save. And now with that key added, we should simply be able to copy this IP address. Let me clear that and zoom in. And I'm going to say SSH into the root at that specific IP address. So let's hit enter. It's going to ask for the fingerprint confirmation. here. We're going to say yes. It's going to add it to the list and we are good to go. We are inside our server ready to party. Okay. So, we're going to run into a couple of security problems straight from the bat, right? We can SSH uh into the root, right? That's something that we don't want to do. It would be nice to just disable SSH altogether to be honest and any inbound traffic from the firewall which we're going to do because we're going to set up with tail scale which creates a private mesh kind of like a VPN. So we won't have any ports open. So this is a big problem but for now what's really simple that we can do is simply disable root login and we can also create a new user u and just you know let the SSH key do its thing. So other than that because even like if you go here to the docker manager dashboard as you can see we have that one container running. I can open access here and look at that you can just access this locally. Uh sorry like through the internet uh which is no bueno at all. But let's just simply add the gateway token here. Let's just copy it for now and add it to it just so we're logged in. And look at that. We are like straight up and running it in like two three seconds which is super cool. Uh, so we can chat with it. We can interact with it. Uh, but we'll get back to this a bit later on. So, let's set up the new user. Okay. So, we're just going to go here to our server and say add user like this. I'm going to call this develop by Ed. There we go. It's going to ask me for a password. So, I'll just add one and retype it. Cool. Okay. I I'm going to skip all this. The workphone blah blah blah. That doesn't matter. And hit yes. Okay. So, there we go. We added develop by ad. Cool. So now what I want to do is give it pseudo privileges as well. So you can do user mod and you do ag p sudo and then the username that you picked. So develop by ed in my case and that should be nice and working. Let's clear that to make more space. I'm going to say su here and then develop by ed like this. There we go. And it says to run a command as administrator user root use pseudo instead. Okay, so let's do pseudo. Who am I? And we'll type in the password. And there we go. It says root. Okay, perfect. So now let's try to log in as this user instead. So I'll just kill my terminal and reopen it. There we go. Make it a bit bigger. I'm on WSL, so I'll just go in that. Clear this out. And now I'm going to say instead SSH developed by add at that specific IP address. So let's pop this open. Let's go here to uh home. We'll copy the ID again. Go back here. Paste it. Hit enter. It's going to ask me for my password. Hit enter. And we are in. Now I don't want the password. As you can see, it did ask me that because we added the key, the SSH key to the root, but not here. So, a couple ways you can approach it. I'm fine here, honestly, just having that same key on this user and then just disabling root login. So, let's copy that over. So, now here, LSA, right? We don't have a SSH folder. So, if you do cd. SSH, right? Nothing. So, it's automatically going to fall back on the password authentification. So, what we're going to do is say make directory. SSH like that. Okay, cool. And then we can cd into it. cd. SSH. That should work. Great. And now I simply want to move my key over from root to this user. So, I'm going to say copy cp like that. I'm going to say slashroot slash.ssh. ssh slash authorized keys and I'm going to move it over to slash usssh authorized keys. There we go. Uh it says permission denied. So we're going to actually need to run this as p sudo. There we go. It's going to ask you for the password and we should be good to go. So we should be able to cd into SSH ls. There we go. We got our authorized keys. Another nice thing to have is mim to open stuff up. So if we do pseudo app install neoim. Let's add that. There we go. And we should just be able to open up everything with neovim. So envim. There we go. We're up and running. And then before we can test if this works, what we need to do is do uh chmod 600 for the authorized keys just so it has ability to read and write. So we're going to say here uh slashsshautoized There we go. We need to run this as pseudo as well. So let's go here at the beginning. P sudo chmod. There we go. Type our password in and we should be good to go. Okay, now that that's done, let's CD back over to root here and we're going to run sudo neovim like that. I'm going to say slashetc sshd config. This is going to be uh where we do all of our SSH configuration. So, if we head over here, let's see what we need to find. There's two really important ones. I know one's at the bottom here. permit root login. We're going to disable this and say no. So, let's do that. Uh, you can do, if you're unfamiliar, it's shift colon uh W to save and write to it. So, there we go. And we're going to search for password authentification. Password. Uh, might need to uppercase this password. There it is. It's commented out as you can see on this line. So, make sure you go to the beginning of the line and take out that slash. You can do that with X by the way. And then you navigate with JKL. Uh but we can go here and put this to no as well. There we go. Let's save that. So in the new terminal now, let's try to SSH into the root at that specific IP address. And it shouldn't work. And it worked. If it worked, we might need to actually restart uh the SSH uh process here. So let's go back here. Leave. And then we'll run the pseudo system uh ctl and we'll run a restart of the SSH. So run that. Let's try it again. Okay, let's leave here. Open up electricity again. And I'm going to say cd ssh into devel uh root at that specific IP address. And it still asks me for a password for some reason. Let's try to log in. Now, you might have this problem where you disable a password off. Uh, but it still says yes. So, something is overriding it. I just grabbed it where password authentification was and I want it to output it for me. H. So, you can run this grab command here with the line number of password authentification. And I saw that actually there's a file here that overwrites that setting for me. So even though here as you can see in the SSH config we set password authentification to no, I have this cloud image setting here that sets it to yes. Sorry, the cloudinit conf here. So let's make sure we go there and also modify that. I'm going to say slash50 cloudinit. And there we go. We have password authentification set to yes there for some reason. So I'm just going to remove that line all together and clear. Okay. So if we try to look at this again, it should be set to no. Uh I'll just grab this out quickly. It says no. Okay. So now we should all we need to do is simply restart uh the SSH process basically. So we can do that with pseudo system restart SSH. There we go. Okay. So let's try this. Let's open up a new terminal. I'll do WSL. Make this a little bit bigger just before we, you know, we don't want to leave here before everything works properly because then you're locked out. So, I'll simply do SSH. Make this a little bit bigger. H I'll try and root first. So, at uh root and we'll need the IP at that specific IP address. And there we go. Permission denied. So, that's not going to work anymore, which is great. And now we should only be able to go in with our key and that specific user. So SSH uh develop by add at that specific IP address. Now if you still have issues doing SSH and going in as you can see we have permission denied. So at least we know the password's not working is when we copied over the authorized keys. Uh the file is still owned by root and not developed by Ed. So what we can do is run this command here. pseudo show and developed by Ed developed by Ed and point it to that authorized keys like that. And if I run the command pseudo name L and show the permissions here, as you can see now authorized keys is on developed by Ed and not on root anymore. So now this should work. If we head over here and try this SSH command again and we are officially in. Okay, so now we don't need these two anymore. Uh we can just focus on having this one. Okay, next up, all of our ports are still open. So, I can click here and access it. As you can see, if I provided the gateway token. So, uh even though we need the token, it's still an open exposed endpoint that people can hit. And we don't want to do any of that. So, we want to make sure that any traffic that's inbound is all blocked and any traffic that's outbound is allowed because that's fine. We can allow the bot to look something up the internet. Uh, but we don't want people to ping this server at all, either through SSH, HTTP, HTTPS, none of that. So, we're going to do this with UFV, which is our firewall. So, let's check its status by saying pseudo uh UFV status like that. We're going to need to add our password. And it says inactive. So, let's just enable it. Pseudo UFV enable. Okay, we're going to say yes here. It's going to disrupt any SSH connections. That's fine. Okay. So, it's active now. So, we can check the status and we can also pass in verbose here uh to see all the open connections. So, by default, it's going to deny any incoming and allow any outgoing. So, that is perfect. So, now with this setting, nothing is going to be allowed in anymore. So even if we try to do an SSH uh into it like that with our username, it's just going to hang because we blocked it. So what we're going to do is expose back the SSH for now and we are going to connect tail scale to it. So only the authorized networks can access this. So we're creating a really close binding between just our IP address here on our our network here. So on this house, right, uh and this server. So only those two can interact with each other and nothing else on the internet. So let's open this back up. So I'm going to say pseudo UFV allow on 22 TCP like that. So the rule has been added. So if we check this back again, as you can see now it's allowed in. So if we again want to experiment and try this uh to see if it works. If I run develop by Ed. There we go. So it's back open. Cool. To add tail scale, we'll simply run this command. curl fssl at tail scale. There we go. Let's install this. There we go. It's done. Now, we can simply run pseudo tail scale up as it says there. There we go. It's going to ask us to authenticate. So, I'm going to copy that over and paste it in. And I'm going to do it through Google here. There we go. And I'm just going to hit connect device here. It's going to say successful. So there we go. We can close out of this. And it says success there as well. Cool. So now all I need to do is get this on my local machine. So you can head over to tailscale.com/d download. I'm going to get this for Windows here. It's a download onverified file. We're going to open this up. I'm going to hit yes and install. I'm going to hit get started. I'm going to hit sign into your network. and I'm going to simply hit connect. Okay, so those two should just connect uh these two IP addresses together. Now I'm just going to simply close and minimize this. And if you head over to login tail scale, as you can see, we have our desktop and our SRV, which is our our VPS here connected with each other. Now what I'm going to do is actually head back here and update our SSH config. So it only allows tail scale to SSH into this. Now let's run this command pseudo UFV allow in on tail scale to any port on 22 and that adds a rule. So if we check the status now it should be accessible through tail scale as well. So let's try to do that and logging in through SSH with that specific um IP address instead of what we had before. So if we head here, you're going to see that there's a new IP address that we can try. So let's copy this over. I'm just going to open a new terminal here and try this. I'm going to say SSH as developed by add at this tail scale IP address not our VPS one and see if that works. So I'm going to say yes here. Adds it to permanent host and we are in. Okay. So now we can just block all access publicly through SSH by removing the other command. So now it's all through tail scale. So if we check the UFV status as well with numbered we have one, two, three and four. We want to keep uh four here and two, but we want to get rid of one and three, which allows us to just hit this IP. So, let's say sudo UFV delete. And I'm going to say one. I'm going to say yes. So, now if we check pseudo UFV status again, we'll only have the two tail scale options. Okay. So, let's let's experiment and try this out. So, let's get the VPS IP address here. And I'm going to say uh SSH as root at this IP. So, that shouldn't work anymore. There we go. It just stops all incoming connections and even to developed by ED. That shouldn't work either. Great. So, we cannot hit uh our VPS address anymore only through tail scale. Now one thing to note is we need to keep this running if we want to be able to connect it through tail scale. As you can see it says connected there. Uh but if we unconnect disconnect it see I disconnected it now and try to SSH as developed by add at the tail scale IP address uh it's still not going to work right. So this has to be running. So let's turn it back on. Have it running. And if I run it again boom we are in. Okay. So we are all done. This is nobody's going to hit this anymore. Okay, let's finally access openclaw now. So if you run openclaw on its own, it's not going to be available again because this runs exclusively inside a docker container. So you can view that if you run pseudo docker ps like this. And there it is. We have our container. Now do note really really important even though we blocked everything through uh UFVW sorry uh so all the SSH connections right and we even the tail scale so only this specific network can access it docker overrides IP table so even though we added all that security as you can see it opened up a port for us here on 55382 so if you try to access the original VPN PS IP address, it's still going to work. See, on port 55382 here, uh, on this original IP address, it's still viewable, which sucks. So, that's not what we want. We want to make sure, uh, that this only runs on local host. So, to fix that, what we're going to do is from here, we're going to head back over all the way to the root directory. And from here, we're going to cd into docker. And if you ls, there it is. open claw hhq3. So let's go into it and you're going to see there's a docker compose yaml file. So we're going to say p sudo nvim docker compose yaml. There we go. So there we go. They have variables here set up but let's remove it. What it actually shows here is something like this 55382 to 55382. So it binds it and it's accessible anywhere. But what we want to do is take this and append here at the beginning we're going to say 127 1. And there we go. And then here we're going to add the colons like that. And this is only going to work on local host now. So make sure you save this. And after we do it, we need to rerun docker. So we can say sudo docker. We're going to say compose down. There we go. It's stopping that container. And then we are going to say up slashd. And there we go. It's back up and running. So now if we go back here and try to run it in the browser again, as you can see, it doesn't work anymore. So it cannot hit that. That port is now not exposed at all and it will only work through local host. Okay, cool. So now let's actually start this up, right? So now let's simply list out all the containers saying p sudo docker ps like that. And there we go. There it is. Openclaw hhq3 openclaw 1. Awesome. So we can copy over this name from here. Let's hit copy. And then I'm going to say p sudo docker exec it. And then we're going to put the name in that we picked slashbin slashbash. And there we go. If you see this that's great. Now we are in as root in the container. Okay, this is going inception levels deep. But from here we can say openclaw TUI. So you can actually run the open claw command. So now let's simply run openclaw on board. And there we go. We are in. That's a good sign. Here we go. We are going to say yes here for the installation. Let's do a quick start. And I'm going to use I'm going to update the values here because it defaulted over to Nexus GPT. So I'm going to say update values and I'm going to actually use Open AI. Now you can there's a bunch of other ones if you want to do you know GLM or something like that. Uh but OpenAI worked the best for me and I'm using the subscription and it's actually been really fine. And Tropic I know they're quite finicky about it. Uh so might go against their toos. GPT is fine with it. So, I'm going to go with that option and I'm going to do the OOTH here. So, that's going to give you the uh URL here that you're going to need to copy over. So, let's copy that over, open it up in the browser. We're going to head over here and paste it. And we're going to log in. And after we do that, we'll hit allow. And this is going to redirect you over to localhost. So, we're going to need to give it this code. So, let's head back here and paste that redirect URL. And here for the channels, we're going to skip this for now. We're going to set up Telegram after. Uh, we can also add skills to this. So, let's hit yes here. Uh, it's just basically an MD file that gives a open claw better idea of what you want to do. I like this one, which is a local speech to text with whisper. So I'm going to select this and install it. This uses a really tiny model. Uh so you can actually leave voice notes through telegram and it can process that. So I'm going to select that and I'm going to hit enter. Now do note when you are installing skills, this is another big security problem where the actual skill itself could have potentially dangerous text in it. Right? All the skill is is it just gets added to the context. So if that skill has dangerous commands like delete all files or do this, do that, that's when you're going to run into problems as well. So keep an eye of what you install. Okay. And then we have the option to pick a a hook as well. I'm going to skip this. There we go. And then we should hit space actually and enter. And then how do we want to interact with the bot? We'll just do it through the TUI. And there we go. We are in. So the first thing I like to do is set the default model. So I just I'll just ask it. Set the default model to GPT 5.3 codeex on launch. Okay, there we go. So we are up and running. So I'm going to give it a name. You are called Clankers and I am Ed. Keep it straightforward. fill responses no fluff. So I'll give it that uh and hit enter. Okay, great. So that's going to save everything over to the user MD and the identity MD for himself. Uh now the next step you can pretty much interact with it here. You can also do slash and kind of see all the commands you have. So you can switch between models, whatever. Uh but let's connect it to Telegram. So we can just simply ask it. Let's connect you to Telegram. Now I have it here on desktop. You can get on your phone as well. The first thing that we need to do is find bot fodder. So head over and look him up. You are going to say slash newbot. So let's give it a new bot. And we'll have to pick a name for it. So it's going to be Clankers. There we go. And it's also going to ask you to pick a username which has to end with bot. So, Clankers bot like that. That username is taken. So, let's try a different one. I'll say Clankers 94bot. And there we go. We're done. We're going to give uh it's going to give us an access key here. Now, make sure you store this safely and don't show it to anyone else because then they'll be able to basically go into Telegram and then communicate with the bot. So, get that token key. Now, what's kind of nice is that it actually doesn't let you update uh the open clock config file here. That's kind of the advantage of running this inside docker. It just won't have permissions to to do anything in host. So, what we need to do is actually open up a new terminal and kind of head over to the openclaw JSON and uh add it ourselves rather than posting the key here and then letting the llm kind of configure that for you. So now I'm simply going to run pseudo vim and go into the docker openclaw openclaw openclaw json. Okay, that's the file we want to go into there. And here we have the off set up for us as you can see. Uh but what we want to do is actually post our uh telegram key. So let's look for that. So let's search for channels here. As you can see it says that we should have one for telegram. And as you can see, it says enabled. Uh it's set to pairing here. And streaming partial is fine. This is so it just the whole response doesn't come in one block, but actually gets streamed in. So make sure you have that in. And finally here, we'll need to add our bot token. So let's say bot token and simply paste that in. Okay. Okay. And now let's simply DM the bot through Telegram. So we can search at clankers 94bot. And there it is. We can click on it. We can say start. Okay. And then let's simply copy over the pairing code that it gives us and paste it in. And again, since it doesn't have access to that file, we can simply copy over the command that it gives us. So, open cloud pairing approve telegram. So, let's exit out of the TUI and paste that in. Open cloud pairing approve. And it said it got approved. So, that should be all working fine. Okay. So, that's all it takes to get Telegram up and running. Let's actually do something useful. So, what I'm going to do is hook up GitHub to this. So, there's actually a skill for that that I'm going to install. So, I'm just going to ask it install the GitHub skill. So, there we go. It installed it. So, now let's say connect to GitHub. And do note this is now running on my own GitHub. I set up a new GitHub specifically for this bot where I can create new repositories, push changes, and then through GitHub here on my main account, what I can do is add it as a collaborator. So, it can push up PR changes for me on any project that I want essentially. There we go. It's going to prompt us up with this uh URL here, which I'm going to copy over. And then I'm going to say continue. There we go. And I'm going to give it this authorization code. So completes and I'm going to authorize. Cool. So that should work. I approved it. Okay. So let's give this a shot. Create me a new Nex.js JS project that showcases um a cool 3D object floating with 3JS and React Fiber. After you do that, create a repo and push it up for me. Okay, there we go. Look at that. It give us a name. I'll say name is fine and keep it private. Uh let's do it uh public. It's fine. It's just a little test project here. So let's do that. And look at that. There we go. It's done. We have a live repo here that we can check out. So if I open up the browser, you can be on your phone. You can see that. Look at that. We got the new repo up. And you can actually use Cloudflare tunnels to temporarily expose this which is super cool because then you can just view it on your phone and kind of vibe code while whilst you're on Telegram. So what you can do is uh show me run mpm rundev and let's do a cloudflared tunnel for this for free. Now again, we can run all of these commands through Telegram, but it's just a bit easier here for me now rather than typing it out there. And the UI is a bit easier to see. But again, as long as your computer is on and tail scale is running, then as long as you're on the same network, uh you can use it through Telegram. Now, if you're on a different network, you'll need to do the whole tail scale process up again. And look at that. It gave us a link here to test this out. So, let's see what it did. I'm just going to open up a new browser here and paste it in. And let's see if the project is up and running. And it is. Let's go. Look at that. Let's do a refresh here. We got Taurus. Something broke. It didn't do it properly, but actually works. And we get to see we get to see it live. So there we go. That's a pretty cool use case for it. And again, you can add this bot on GitHub now. Uh you can give it permission to read and to do um you know, pull request. And then you can just simply talk to it here and approve it if the code is good. But let's quickly go into Telegram for now. So by the way, if it didn't work when you did the pairing step, if it didn't work, make sure you rerun and restart the Docker container. So you simply do pseudo docker restart and then the name of the container. And once you do that, as you can see, it should be working just fine. Also, another tip is if you do slash new, that's going to clear the context. By default, open claw always tries to compress it. H there's a bunch of settings that you can change about that, but you can also ask it. Uh so, okay. So, make sure you run new every time. You can also set up a what's it called? Little groups here for if you want to kind of, you know, have maybe talk about health in this one, you want to talk about coding in this one, you can kind of separate that. Now you can also chat to it with the microphone if you haven't added that skill on the onboarding. Um so we can just ask it hey install whisper tiny to run locally. So there we go. I just said can you hear this message? It installed it automatically for me and it responded properly. Let's go. So again there's a bunch of things you can do with it. One thing I like to do is this. set up a cron job that gives me a message every morning at 8:00 a.m. about the latest news on X or if you search up on Google on the news uh regarding AI tech, openclaw updates, any any of that sort. Keep it quite concise and also provide the links to uh where you searched and after you set that up, let's do a test run of it. So when I type in test, uh you should do it. And there we go. Look at that. It gives us a nice morning brief. Look at that. Open cloud ship the new release immutable all the different news here and also gives the link and the sources to this. So that's it. You are up and running. It's up to you now to kind of go and find what you want to do. Again, you can do Blender and then you can make it send you screenshots of its progress. Uh a bunch of different stuff. So hope you enjoyed this episode. Let me know if you want to follow up on this so we can go a bit deeper in it. H thanks Hostinger again for sponsoring this episode. Check out the link in the description. Again, make sure you use develop by Ed. That'll give you an extra 10% off. And yeah, let me know how it goes. And I'll catch you guys in the next one.