I Gave GrokBot Claude Code, Codex, and Grok Build

0:00You can now run Claude Code, Codex, and Grok Build right inside of your Grokbot's own computer. You sign in once with the subscriptions that you already pay for. Grokbot hands the coding work to those coding agents, and you don't need any API keys. If this is your first time here, my name is Casper. I'm the founder of Deep Reddit AI. I use these tools to run my business every single day, and I build them out for paying clients. My goal for this video is simple. I'm going to set up all three coding agents inside of my Grokbot and have them build a simple working website for a cleaning business completely from

0:28scratch. By the end, you'll know exactly use each one, how I use Claude Code specifically with Grokbot, the usage and what each subscription actually pays for, and whether or not you should add them to your Grokbot stack. So, get comfortable, grab some coffee, and let's hop straight into the video. Really quickly, I want to walk you guys through my Grokbot chat because you will have to actually tell Grokbot to use these specific CLI. So, here's an example. You see, use Claude Code to build a one-page website for Sunrise Cleaning. That's the fictional website that we're building out today. And we're going to do all this live, but I just want to show you

0:57guys where we got to in the test runs that I did. is when I asked it to use Claude Code. Later, I installed Codex, and right here I said, "Use Codex to review the Sunrise site folder, find the three biggest problems for a customer on a phone, fix them, and then send me a before-and-after screenshot." And you guys can see the screenshots that it

1:12sent right here using the Codex CLI. What I love about this is that the only time we're using Grokbot usage is for the messages that we're getting inside of Grokbot alongside actually prompting the Claude Code, Codex, and Grok Build CLI. And then lastly, I used Grok Build to add some more functionality to the website, and this is what the website ultimately came out to look like. Now, it's super simple, and that's not the point of this video to make a very dynamic website. I totally understand that this might look like AI slop, but more importantly, what I'm trying to show you guys in today's video is how we

1:38can use Grokbot to orchestrate these CLIs. So, we have a super simple landing page. We have an image that was actually generated using the Codex CLI. We have the services here, request a free quote, which has full functionality and everything like that. So, let's go ahead and click on get a quote. It brings us to this page. I'm going to go ahead and fill this out. And once this is filled out, I can go go and click on send request. We're going to get sent to an unable to submit form because I haven't wired it up on the back end, but once this would be wired up and the whole

2:01submission form would work and then we have a full functioning website that GrokBot built with the other CLIs. Now, as we go throughout this video, I want you guys to look at this tree just so you guys understand everything that's actually going on. We have GrokBot being the manager, so I'm only prompting GrokBot. I'm never prompting Claude Code, I'm never prompting Codex, and I'm never prompting GrokBuild. GrokBot is just taking those prompts and putting them into the CLI, which is the only time you're actually using GrokBot usage. So, you're able to save a ton on it. And before I get any questions, you do not need all three subscriptions to

2:29do this. You can use whichever CLI you use from whichever platform that you're using, whether it's Claude, ChatGPT, or Grok. You just need one subscription to start doing this at all. And if you're wondering how any of this works, the first thing that I want to show you is how GrokBot actually codes by itself. Before I hand GrokBot anything, I want to give you guys a clear picture of what

2:46my weekly usage looks like right now. I've been absolutely ripping GrokBot for a project that I'm super excited to share with you guys very soon, but right now we're at 43% used with 6 days left. So, the GrokBot usage isn't being very friendly with me, but oh well. What I'm going to do right now is prompt GrokBot to actually edit the Sunrise Cleaning page. So, I'm going to say make the two orange buttons on the Sunrise homepage look different. So, get your free quote as the main one and match their capitalization. And I just want to show you guys that if you don't say use the

3:12Codex CLI, use Claude Code, or use GrokBuild, that it won't do that. It will just start coding on its own. So, let's go ahead and send this off. Obviously, a small change, so it handled it very quickly. This is what it looked like before and this is it after. Obviously, the buttons now stand out a little bit more. And when we look at my

3:26GrokBot usage, it didn't go up at all. Now, this was a very small task, so I didn't expect it to. If it did, I'd be a little bit worried. Just understand that GrokBot did all of that by itself, not using any CLI or any Cursor Cloud agents or anything like that. That all happened natively inside of GrokBot, which brings me to how this is billed against your actual usage. So, just understand that there's many plans right now. There's the Super Grok plan, there's the Cursor plan, and if you're confused on that at all after watching this video, go ahead and click on this video right here. To

3:52make this as simple as possible, whenever you're coding with Grokbot itself and there's no tool named, you'll notice that there's either a cursor agent cloud being spawned or you're seeing CLI tools being used and it will tell you that it's using that. If it does not, that means Grokbot's doing the entire job and that's coming out of your Grokbot weekly usage. Now, if you use cursor and you're on a paid cursor plan, this gives you the ability to spawn cursor cloud agents, which use cursor models and the cursor usage. And that can be extremely confusing for a lot of people and what I mean is here I am on

4:21my cursor spending dashboard. So, remember, it's a separate subscription than the super Grok subscriptions. Right now, I just upgraded recently to the ultra $200 a month plan and whenever you're using cursor cloud agents, you're using what's included in ultra. So, you're using cursor models and you're using other models. You're not actually using the Grokbot weekly usage pool, which you guys can see down here. Only when you use Grokbot is when this pool actually goes up and you start losing your usage. And that's why when I get asked questions on which plan people should be on, I say it's depending on your use case. If you're actually coding

4:50want Grokbot to code, I would 100% go with a cursor pro plus plan or a cursor ultra plan just because coding with Grokbot itself absolutely kills your usage. So, you want to make sure you're spreading that evenly throughout all your usage plans and just understand that when you're in ultra, these are the usage pools for the entire month. I don't really understand why they do that and then Grokbot is a weekly usage pool, which is just really, really weird. I think both of them should just be on weekly. It doesn't really make any sense to me. Then lastly, when you install one of these CLIs like Cloud Code, like

5:19Codex, like Grok build, you're actually using your own subscriptions from those platforms. So, they're using those platforms usage pools instead of Grokbot's. The only time you're using Grokbot's is to actually send off the prompts and get the requests back. If there's one thing I can be extremely clear about in this video is that if you don't tell Grokbot which tool to use, Grokbot will assume that it can just do the job itself. So, it won't call any of the tools that you just installed. Now, let's go ahead and equip Grokbot with a coding tool and we're going to start off with my favorite and my daily driver,

5:45Cloud Code. Now, I already had Claude Code installed on my Grok Bot computer, so what I did is I went ahead and uninstalled it and then reinstalled it just so I can show you guys how you're actually going to log in because remember, Grok Bot has its own computer with its own terminals and its own files. It can access the internet and everything like that, and all you need to do is log in to whatever subscription that you're actually using, and you can do that via the computer which allows all of this to happen. So, what I'm going to go ahead and do is click on

6:09takeover, and then from here I'm just going to authenticate into my Claude account, and it's really as easy as that. you've authenticated in, it's the same exact process if you were doing it on your own computer. I'm just going to go ahead and click on authorize, then you're going to have to do a little bit of a captcha thing, and then you'll be done. You'll come back to Grok Bot, you'll say, "I'm done." It's going to be completely finished. It'll go ahead and install the Claude Code CLI, authenticate your new account, and then from here I can use Claude Code. It also does a test for you whenever you sign

6:34in. So, as you can see right here, it says Claude Code was reinstalled and signed in to my email, which I'll have blurred out, and then as a test, it used a headless Claude to reply with the word ready, and it came back with the word ready, which means we are fully installed, and now we're going to get to building this website. Now that everything's authenticated, we're completely signed in, I'm just going to send off a prompt to build a one-page website from an invented mobile detailing company. Again, the most important part, I have to tell Grok Bot to use Claude Code to build a one-page

6:58website. So, I'm just going to go ahead and send this off, and now what's happening is Grok Bot is opening up the terminal on its computer. I don't actually know if we can see it, but it's going to go ahead and open up the terminal on its computer. It's going to log in to Claude Code, and then now it's going to send that prompt off and then save everything into its Grok Bot computer folder. That's a lot of steps there, so if you need to rewind and slow it down to understand everything that I just said, go ahead and do so. Now, I do like that Grok Bot gives me the

7:20verification because it says Claude Code is building the site now. I'm just going to go ahead and show you guys my usage one more time so you guys can see. It's at 43% and I would imagine it goes up 1% maybe if that once this is all complete. And I also would like to see if it was working inside of the Grok Bot computer, but right now it's telling me that I could take control. I'm not going to go ahead and do that because I think it's already working on the terminal inside of its computer. So, I don't want to go ahead and interrupt anything, but I'm

7:45just going to let this finish and I'll get back to you guys once it's done. Looks like everything just finished up. I can see things moving on my GrokBot's computer. Hope it's 5.5 did this entire thing in about 4 minutes, which is expected. Now, it's going ahead and taking screenshots of the mobile versions. And from what I'm seeing right now, this Northshore one is actually looking pretty clean. I like the cars. I like the kind of typography. It's not done yet. It's doing a bunch of tests right now, but I wanted to give you guys a sneak peek. And just like that, everything is done. I kind of showed you

8:09guys the three screen shots that it took already. Here's the pricing section. I like the images that it used. I think that looks super super clean. I like the blue kind of style as well. Let's actually hop into the website itself. Over here to the homepage and we can see that this website now I'm in the GrokBot computer, so it's a little bit laggy, but you guys can see this looks actually super clean. Like it's not too AI slapish to the point where I would notice right away. Of course, there's some slight tells, but this is the first rendition. I'm actually kind of a fan of

8:34it. I think it looks really clean. Here's the before and after little slider. That's actually really really cool. And I think we're going to touch this up in the Codex version here, but this is a really cool feature and just overall a super simple website. Here's your book your slot. We pull up kind of

8:47how they work and overall pretty good. And this was all done with Claude Code being managed by GrokBot. We're going to get back to the website here in a second, but I want to pivot and show you guys how I actually use this from my phone because this is actually a really unique use case. You guys know that I have an AI operating system on my computer, the Deep Rooted AI OS, and it's actually a GitHub repo so that I can kind of clone it and use it wherever I need to or whatever the case may be, but actually can do that from GrokBot as well. So, I'm going to tell my GrokBot

9:11to clone my Deep Rooted AI OS GitHub repo into the Claude Code CLI on its computer and then I can manage my Claude Code operating system from my phone using GrokBot. So, I have a 24/7 access to my operating system from anywhere that I want and it's pretty cool. So, the first thing I'm going to do is I'm going to say clone my Deep Rooted AI OS

9:28repo from GitHub into your computer. Don't open anything in the people's folder. I'm going to go ahead and send that off. Now, it's going to go to GitHub, grab that, clone it, and put it into Claude Code. We then got the confirmation that our deeper data iOS repo is now on the computer, and then I'm going to say use Claude Code to read the context folder content thesis markdown file and tell me in three bullets what my YouTube channel is about. Then we're going to add a file called Grok Bot was here.md with today's date and a one-line note, commit it to a new branch, and then push it. So, I'm

9:55going to go ahead and send this off, and this is how I would be using it from my phone, right? I would say use Claude Code, get me this information, do this inside of this repo, and things like that, and then I would just push it to GitHub and then pull it in on my computer when I needed to. Here's the response. My channel's AI Made Simple, casual approachable AI teaching. The main topics are the Grok Bot series, Claude Code skills, and then new model launches, and then how I publish typically on Monday, Wednesday, Friday, or at least three videos a week, which is what I'm trying to do now. It also

10:20committed Grok Bot was here.md, so now let's go ahead to our desktop version of Claude and pull that in. I can open up a new chat, type in get fetch origin Grok Bot demo, and then send that off. And now it'll just pull that in straight from GitHub, straight from what Grok Bot did inside of that repo and pushed it. So, it's just pretty interesting how this all can connect together, and it makes it really easy to use Claude Code directly from my phone with a combination of Grok Bot. And just so I can show you guys the proof, it said I fetched Grok Bot demo, it's a new branch

10:45now tracked locally as origin/grokbotdemo. Your working tree and main are unchanged. Then I did a little stat pull as well, and the branch has one commit from today at 1:43, which is about 2 minutes after I recorded this video, and the message here is add Grok Bot was here.md demo note. So, this is kind of the connection. Just wanted to show you guys proof. And this is how I'm able to access my repo when I'm away from my computer, and it's much, much easier than using the Claude Code remote feature or something like that. And lastly, for cleanup and security purposes, just understand that if you

11:13download this repo onto your computer, all your bots have access to it. So, if you don't have very good guardrails set up, this could affect you negatively. So, all I would do here if that's kind of what you're worried about and you're doing it for a very specific reason and that you were just you knew you were going away or something, when you get back or when you're in Grok Bot, you can just say delete the deeper rooted iOS folder from your computer or whatever folder that you guys are using. I can go ahead and send this off. It'll clean up, and then I can go back inside Cloud Code

11:36and delete anything else that I did, or fix it, or merge it, or whatever the case may be. And at this point, we have a website that Cloud Code fully built on Grok Bot's computer with Grok Bot managing it. I also showed you how to clone one of your GitHub repos and have access to it 24/7 when you're using your Grok Bot away from your computer. But, there is one more way, and it's really unique that I want to show you guys because it allows you to communicate with Grok Bot directly from Cloud Code if that's what you're using all the time. Now, there are two ways to use

12:01Cloud Code and Grok Bot together. You guys just watched the first way where Grok Bot is the boss, and Cloud Code does all the coding work on the Grok Bot computer. Now, the second way is when we have Cloud Code actually being the boss, and it hands work over to Grok Bot and all the team of bots that you have. In this case, we're going to be actually giving it some eyes on X and having it pull in research things and kind of creating HTMLs for us. So, a super simple use case, but to keep it simple, way one, you're going to code from your phone, code from wherever using Grok Bot

12:28and having Cloud Code on that terminal. And way two is specifically handing over jobs that Grok Bot would just be better at. I actually got this entire idea from Riley Brown over on X. He posted a whole article about it. I'll make sure to link that down in the description. But, essentially, how this works is you have a webhook trigger routine set up inside of Grok Bot. Cloud Code will then send a task over to that webhook. Grok Bot then gets that task and figures out who to hand it off to. In my case, it'll be my X research bot. Then, from there, it completes the task and gives it right

12:56back to Cloud Code as the output. You will be using a webhook here, so make sure you always keep that webhook key private and let nobody get access to it that doesn't need it. Again, I did not create this. When you click the link down below, you'll get sent to a page like this. Literally, all you have to do is hand it over to your Cloud Code agent, your Codex agent. It works with any single agent harness, and just have it install this. All it is is a skill that hits that Grok Bot webhook anytime you have a request, and then it's a very easy process from there. The best way

13:21for me to show you guys this working all the way through is by having my Cloud Code terminal on the left-hand side here, and then my Grok Bot little sliver on the right-hand side here, and all I'm going to do is say ask GrokBot to have my X research bot find the top trending news in AI this week. When it answers, turn it into a page I can scroll through. So, all I'm going to do is go ahead and send that off, and what you should see is a little skill get kicked off called the GrokBot webhook, as you guys can see right over here. That skill

13:46successfully loaded, and now it's sending a message over to my GrokBot with a webhook trigger routine. So, if I go ahead and open up GrokBot right here, we'll go to details, and you can see Claude code webhook. Now, this will fire off anytime this webhook gets hit, and as you guys can see, it's sending off all these messages. A few runs are happening on the left-hand side here, and you can see that my GrokBot is working without any messages being sent from previously. So, it's sending off that query. Let's go ahead and see if I open this up and I go over to research down here and go to X research bot. I

14:13haven't seen it get a message or anything like that just yet, but I do know that it's working cuz this guy's moving, and we'll see what happens. I will say this isn't a very fast process. The first two or three times I ran it, they took about 8 to 10 minutes each. So, just know that going into it. I'm sure there's ways of optimizing the speed. I haven't found a way of doing that quite yet, and once this is done, we'll go over the results. Now, the research came in, but I had to prompt it and actually ask it, "Hey, are you

14:36finished with that request from Claude?" because I saw that it stopped working, but nothing was going on here. So, then it finally said, "Yeah, it was finished," but it finished like 4 minutes before I asked. Now, this is a little bit of a bug because this was initially created for Mac and the Mac operating system. I actually took this skill off the internet and tuned it for the Windows version, so my version's a little bit buggy. Just know that there might be some workarounds if you're using Windows as opposed to Mac, but now on the left-hand side here, it's creating that artifact. We're going to get it pulled up on the screen right

15:01here, and these are the top AI news on X from October 5th to the 12th, and it gives me a very nice just kind of HTML that I already had preset. This is OpenAI, Anthropic, Google, and Meta. We can scroll down here. OpenAI drops 772 AI-generated math papers, which is a big deal. Opus 5.5 dominates, then Nerf complaints hit, which those are all garbage. ChatGPT gets GPT-6 with intelligent UI, and there's [clears throat] just a ton of other news

15:26here that I can quickly scroll through. But, in all honesty, this isn't really a crazy use case here. It's just getting news and putting it into one spot. But, more importantly, I wanted to show you guys how you can have Claude Code be the boss and Grok Bot actually be the worker now. Back in Grok Bot, this is actually how I set it up. All you have to do, and again, this entire skill that I linked

15:41down below walks you through everything. Just understand that you're setting up webhook URLs, webhook keys, and authorization headers. Please keep all of those in a safe place. Don't let anybody get access to them, because if they do, then they could do whatever they want with your Grok Bot. And yes, we spent a lot of time in the Claude Code part, but do understand that you can do this with any single CLI. You can set up this skill and set up the webhook and everything like that with Code X, with Grok Build. It doesn't really matter which harness you actually use, but I use Claude Code the most, which is

16:07why I spent majority of the video with Claude Code and explaining it to you that way. But, we still have two harnesses to install with Code X and Grok Build. Let's go ahead with Code X and see what it can find in any mistakes inside of Claude Code's original one-page website. Now, the rest of the

16:20video is going to be extremely simple. We're going to install the Code X and the Grok Build CLI in the same exact way. Starting off with the Code X CLI, all you'll need to do is prompt your Grok Bot. Go ahead and install the official Open AI Code X CLI in your terminal. It'll go ahead and install it, and then start by signing you in. Now, there's one kind of caveat with signing you in on Code X, and that requires you to go to the ChatGPT app on the website version, go to security and login inside of your settings, and enable device code sign-in for Code X, Excel, PowerPoint,

16:47and Word, because you'll need to authenticate through the Grok Bot terminal. And once you do that, the exact process that you guys saw with Claude Code is the exact same way it happens with ChatGPT. It also gives you a device code that you just log in, and it automatically puts it in there. And then, once you're authenticated, running a headless version, get the confirmation that it's working, and then we're going to pick up from there. The first thing we're going to do is find any problems inside of the existing website that we

17:09created. So, we're going to use Code X. Remember, you have to say the tool that you're actually using to review the North Shore site folder like a picky customer on an iPhone. Find the three biggest problems that would stop someone from booking a detail. So, I'm going to go ahead and send that off. It's now going to open the Codex CLI, find everything, give me a report back. We're going to do an iteration. We're going to walk the fixes that it found from the Claude code version, and then we're going to go ahead because it's Codex, we're going to use GPT image two to actually add some images into the

17:34website. And again, you'll know this is working because every single time you call on a tool, Grok Bot will repeat that back to you with Codex is reviewing this site now or Claude code is building this now or Grok build is building this now. It just gives you that confirmation so you understand that it's actually working as opposed to Grok Bot doing all the work. And if we hop into our usage here, this hasn't really moved since the beginning of this video. It's still at 44% and I'm doing this all sequentially in order so that there's no ambiguity in any of the usage or anything like that

18:02because I do understand that Grok Bot and the usage is still a huge problem for a lot of people. So, I want to make sure I'm very transparent about where my usage is going. Not only that, but you won't see that usage go up because we're using other subscriptions. So, if you have a Claude subscription, you're going to want to be looking at your Claude

18:17usage, same with Codex, same with Grok. And these CLIs work extremely fast. Codex found and fixed the three problems in about a minute. Now, I'm taking the before and after phone screenshots of the booking section. I love how Grok Bot has its like verification loop built inside of it because now I'll be able to see it, it will be able to see it, and

18:33then we can continue moving forward. This is also an important time for me to mention that having other models verify and review other models' work is extremely important. I would probably mostly use it this way with Claude code being the main builder using Opus 5.5 and then the Codex CLI using a review model to kind of review it exactly how I'm doing throughout this workflow right now. Here are the three problems that it found that would stop someone from booking and fixed all of them. The booking form didn't send anywhere, so now it goes to my email and the button says send booking request. The only way

19:00to contact the business was a fake phone number, so it actually said email us with my email address, so it fixed that. And then the logo, nav links, and the top book button were too small to tap easily. They're now all 44 pixels tall, so I'll hop into here. Here are the images of the mobile version and all that. So, nothing crazy, but a few very nice fixes that will optimize this website for us, and now we can continue. Now, because Codex has a native image generation tool with GPT image 2, it's not GPT image 2.5. I don't understand why the Codex CLI hasn't upgraded that yet. Maybe I'm in an

19:30outdated version, but if it does upgrade, then you could use GPT image 2.5, but I'm using GPT image 2. And what we're going to do here is replace every stock photo on the Northshore website with custom images, and then we're also going to use that sliding feature that we saw earlier on the website and optimize that a little bit better so we can actually see a clear before and after. So, I'm going to go ahead and send this off, and again, keeping in mind 44% usage here. Once this is done, it's probably still going to be at 44% because again, Grok Bot is just being the middleman. It's taking the prompt,

19:58sending it to Codex, Codex is sending it back to Grok Bot, and Grok Bot's giving us the output. And as easy as that, we can open up the website now. I'll go ahead and take control here. We'll go to the Northshore website. We have a new image here with a black car here. Looks very clean. We got other stock images

20:14from GPT image 2, which look very clean. And then this is the part I was most excited for. So, drag when you see the difference. You can see it's very dirty on the left-hand side here. And if I drag it over to the left, it's very clean. That's probably my favorite feature. Let's go ahead and scroll up the other way and look at that. So dirty, so nasty. And just like that,

20:33that slider, that's such a cool feature. Our website is slowly coming along together. Now, we have one more CLI to cover, and that's Grok Build. I put it last because Grok Build, Grok Bot, and Grok get people really confused. First things first, I want everyone to understand that Grok Bot and Grok Build are not the same thing at all. Grok Bot is your 24/7 personal AI assistant that runs on the cloud. It has its own computer in the cloud. And Grok Build is SpaceX AI or SpaceX SI, their coding tool. So, this writes code in the terminal, and it's only accessed usually through a cloud environment or when

21:06you're directly on your computer inside of the terminal. To keep it simple, GrokBot is your assistant, GrokBuild is the tool that it's using ever since we gave it access to it. And at this point of the video, I'm sure you know exactly how to install this CLI into your GrokBot computer, but if you don't yet,

21:20all you need to do is literally ask it. Install the official GrokBuild CLI from xAI in your terminal. It'll install it. It'll have you authenticate through its computer. You'll sign in. You can literally just authenticate with Google, and then from there you'll be all signed in. Just make sure you're on the right account that's connected to a super Grok plan. I jumped ahead a little bit here, so GrokBot's already at work, but essentially what I'm doing is adding a feature to the website that's an instant price estimator. So, all you need to do is hand over the package that you want, the size of your vehicle, any additional

21:49add-ons, and you'll get spit out a direct price. You guys can see that GrokBot said I didn't give any add-on prices, so I'm using placeholders for now, pet hair removal, et cetera. I'm not going to even dive deep into that. That's not the point of this video, but just understand that that's what we're adding on, and then we're going to also wire it in. After a few minutes, GrokBuild the entire estimator and connected it to the homepage. It then went and used its computer, clicked around, and made sure everything was working. Then it claims the estimator works end to end. I tested an SUV with full interior and pet hair removal. It

22:18shows $209 and booked this detail opened, and then it gave me some screenshots of that testing as well, so I can verify that all of that is great and is working. So, that's pretty freaking cool. Now, I will point out that the estimator portion and getting that wired in was probably the bulkiest code that we did throughout this entire at 44% of my weekly usage. So, the only time we're using GrokBot is to actually manage the CLIs and give them the prompts, and then take the output and do the screenshots and testing. So, that's all three different CLIs all inside of

22:49one folder providing us one website. There is one thing that can bite you if you're installing and signing in to all of these accounts, so let's cover that really quick. There's a common misconception that every single one of your GrokBots has its own computer, and that is not the case. All your Grokbots actually share one main computer, and that includes all the logins and anything that you've authenticated with your main Grokbot. So, if you've been following along with me this entire video, and you've installed all three CLIs, that means every single bot now has access to all of those CLIs as well, not just your main bot. Make sure if

23:20you're using the GitHub tactic that I showed you earlier, that you're only cloning what you need, and that if it's a specific use case that you need to push. This is where I would be extremely careful. What's also cool is that these survive any updates. So, if you go and update your Grokbot computer, these won't get uninstalled, and you won't have to reinstall them. I tested this myself, and all the packages stayed on the computer. One way to really protect yourself whenever you install these CLIs is to hop into your general settings of your Grokbot and scroll down to the custom rules. So, whenever your Grokbot

23:48wants to do something, you can add that rule in there, and then tell it to always ask first. Now, if you have CLIs installed and you have these tools installed, I would automatically do this, and let me show you what my updated rules look like. And now I added three quick rules where use Claude code, use Grok build, or use Codex all require an ask first behavior. Let's test it out. What I'll do is I'll say use Claude code to examine the code and see if there's any issues. I'll send this off, and I should get a permission request now. And there we go. It says Claude

24:16code read only review on Grokbot's computer paused by your ask first rule, use Claude code. I'm just going to go ahead and allow once, and now it'll go examine that code and give me a review. This is just an early guardrail that you can use just in case you're doing any autonomous work, and your agents might decide they want to use a tool, it's going to have to ask you first to get that approval. Which brings me to a few rules that I want you guys to kind of follow if you guys are going to go this path and install these tools in your Grokbot. Make sure you're installing the

24:41official tool. Go get the links from the official pages, the official OpenAI page, official SpaceX SI page, and the Claude code page. Make sure you're signing in yourself and doing all the authentication in your Grokbot's computer yourself. Don't have it click around and do anything on your behalf. If you're building for other people or running it non-stop, that's what API keys are for, so make sure you understand the difference there. And just so we're all on the same page, this doesn't replace any of these CLIs. All of these CLIs are extremely powerful tools. What we're doing is just giving these CLIs a home on a cloud computer

25:10that's always on and usable by Grokbot. And if you're asking me on which one you should install and which one you should use alongside Grokbot, I would point you to Claude Code. I believe Opus 5.5 is the best model on the planet, and now Grokbot is powered by Opus 5.5. So, this combination is very smooth. It knows exactly how to use Claude Code, how to prompt it properly, so that's what I would do. And another reason for that is because I use all three of these CLIs pretty much every day, but Claude Code is where the majority of my tokens go

25:37every single day. I love Claude Code. I've been using it for over a year now, and I'm so glad that I can use it inside of Grokbot as well. Now, for you, it comes down to which one you're already paying for. Some of you might have a Grok subscription, some of you might have an OpenAI subscription, some of you might have a Claude subscription. What I would do right now is just test this out with the subscription that you have, and then figure out the rest from there. And if you want to switch to Claude Code, or if you want to switch to Grok Build, or

25:59if you want to switch to Codex. But if you stuck with me this far, you now know how to install all three of these CLIs inside of your Grokbot computer. You saw a workflow on how I use Claude Code, Codex, and Grok Build to build an entire website along with some integrations. And if you followed along, you just supercharged your Grokbot to make it even better than it already is. This was a super fun video to make, and I know I threw a ton at you guys. So, if you got lost at any point of the video, don't worry at all. I'm going to be dropping a

26:22full free resource guide that walks you through every install, that walks you through all the use cases and things that I did in today's video. So, you guys can follow along and make a decision for yourselves. All you guys need to do is click the link down below, enter in your email, join my free school community AI Made Simple. There you'll get access to all the Grokbot resource guides I've ever created, including the one from today's video. So, I hope to see some of you guys in there soon. As always, if you've got any value from this video, drop a like, hit that subscribe button. It definitely helps me

26:48out a ton. We're almost at 10,000 subscribers, which I can't believe at all. Turn that notification bell on so you never miss one of my videos, and leave a comment down below on which CLI you're going to hand rock bot first. If you've made it this far in the video, thank you so much, and I'll see you guys

27:02in the next one. God bless, guys. Hey there. If you're still here, that means you've made it to the end of the video. First of all, thank you so much. If you're new here, something I like to do at the end of all my videos is pray for you guys, my audience. I do this because I genuinely love you guys. I care about you guys a lot. I'm really appreciative of the time and attention and your willingness to learn from my videos, and I mean, we're almost at 10,000 subscribers. Back in January, if you were to ask me, you know, do you

27:29think you're going to hit it that fast? I'd probably say no, but that's all kudos to you guys and your constant support and your love that you guys show me in the comments, and I really do appreciate it. And uh I also want I do this because I want to see if you guys live fulfilled lives. I want to see you guys live good lives, be good people, spread the good word of the Lord, and just care for other people and be positive because uh it's a very negative world that we live in right now, and I think uh positivity can always help that. Most importantly, I do

27:52this because there's people out there that just need to hear a prayer. There's brothers and sisters of Christ who are just struggling right now, whether that's financially, mentally, um whatever the case may be, grieving deaths, whatever. Uh people are struggling out there, and I I don't want to ignore that, and I want those people

28:06to know I'm speaking directly to you. There's help. There's people out there that are praying for you, that there's people that out there who are willing to help you. Um and we're going to be praying for you guys today and just making sure that this message gets across to you guys. Um But if this makes you uncomfortable at all, please feel free to click off the video. I'm not here to force anything upon you. Just know that if you do leave, Jesus loves you. I'm going to go ahead and send you guys off with a

28:28prayer. Heavenly Father, Spirit of the Living God, Holy Ghost, thank you so much for this day, Lord. Thank you so much for the breath of life that you've blessed us with. Thank you so much for allowing us to see another day and praise and honor your name. Lord, I just want to take this time to thank you for this platform. Thank you for all these people, the audience on the other side of the screen who take their precious time and attention and and spend it on me to learn from my videos and hopefully a apply AI in a positive way to businesses, their personal life, whatever gives them more time to spend

28:59with their families and spend with you, Lord. Lord, I want to take this time to pray for that audience. Pray a blessing of just strength, Lord. Continue to give us the strength to stand firm in our faith. Continue allowing us to stay step be steadfast in your word and just be able to defend our faith in a time where our faith

29:16continues to get attacked. Lord, just continue to give us the strength to stay strong in the moments where, you know, everything feels like it's turned against us and and there's just a lot of overwhelm and things like that. Lord, I just pray for strength in those moments and I pray that we can come to you and just pour our hearts out and just let you just listen to it and then guide us in the rest of the way. Lord, I just pray for our brothers and sisters of Christ who are struggling right now in the world. Lord, unfortunately, some brothers and sisters are homeless, some struggle with anxiety and depression,

29:47some struggle with financial responsibilities and and things just didn't go their way. Lord, I just pray that you reveal yourself to them. I pray that you are there for them. I pray that if they ask you that you carry that burden for them and that you just put people in their lives that are willing to help them. Lord, I pray for myself that if I see one of our brothers and sisters of Christ struggling, Lord, put it in my heart and put it in my brain to go and help them in whatever, even if it's uncomfortable, even if it's might not be the right call, just help me make

30:13that call and help me help those people. Lord, I just want to take this time to thank you for your grace. I want to thank you for your love. I want to thank you for all the opportunities that you've blessed me with, all the opportunities that you may continue to bless me with, and Lord, just continue to make sure that my faith and my conversations with you are the number one thing and the number one priority in my life. Lord, I want to thank you for your son, Jesus, and the sacrifice on the cross. Because of that sacrifice, I can have this conversation with you. I

30:38can have this conversation with you. I can one day meet you in heaven and that's something we as man do not deserve. We don't deserve that, but because of Jesus and his death for our sins, we now can. So, thank you again, Lord, for your grace, your love, your abundance, and I pray all these

30:52things in the name of Jesus Christ. Amen. Now, go have a blessed day, guys, and I'll see you in the next one.