# Grok Bot Use Cases That Are Actually Insane

Channel: AI LABS
Video: https://www.youtube.com/watch?v=90pwPVrydHg
Duration: 14 min
Language: English
Words: 3146
Transcript page: https://viewrankai.com/tools/youtube-transcript/90pwPVrydHg

---

[0:00] Elon Musk's new AI agent, Grockbot, is being used in really creative ways. Grockbot has made it so easy to automate tasks that we had to manually ask our agents to do. And what's different about it is that the setup needed to automate those tasks is the easiest one we've seen so far. None of the other tools even come close. Now, if you're new to the channel, then welcome. We're a software company, and this is AIABS. And in this video, we're going through all eight of the most powerful ways you can use Grockbot. How you can get started with each one and what things you need to be careful about while setting this

[0:32] up because if you don't set it up properly, then Grockbot is going to end up wasting your time instead of making you more productive. Now, this section is for people who don't know what Grockbot is. So, if you already know the basics, you can skip to the next section. Grockbot is basically a tool that lets you manage a group of agents from one place. It calls each agent a bot and each bot can run all the time without relying on your computer. So even if your computer is turned off, the bots can keep working. Grockbot basically gives your agent its own computer that runs online. Every bot on

[1:02] your account uses that same computer, which means all the files that the bots create, the browser that they use, and any accounts you've logged into are shared between each bot. The bots can message each other and work together in a group chat, and you can also schedule them to do a particular task at a set time. All the bots also have access to a browser on that computer and it's not a separate browser for each bot. Every bot actually shares the same one. You log into your accounts once and after that the bots can see what's on the screen and use those accounts to do tasks for

[1:32] you. This means they can use almost any website you use without you having to set everything up again for each bot. Now you might think Grogbot sounds similar to Hermes and the general idea is nearly the same because in both cases the agent can keep doing your work while you're not there. The difference is who sets and manages the computer it runs on. With Hermes, you're the one who has to set up and manage that computer yourself, including the tools that you need to connect to the agent, the browser, and its login. With Grockbot, Grock handles all of that for you, and

[2:00] you just have to log into your accounts. To use Grockbot, you need a paid plan. It's included with every paid cursor plan or any Super Grock plan. Grockbot also has its own separate weekly usage limit. So, whatever your bots do doesn't count against the normal usage limit you already have in Cursor or Grock. To set it up, you just need to download the app and run the installer. Once that's done, you can open Grockbot and create as many bots as you want. You can add a new bot using the button at the top. From there, it's going to open up a chat and ask you questions regarding what you want the

[2:30] bot to do. And from your conversations with it, it's going to update its profile. If you don't want to chat with it, you can directly edit its profiles and add in your instructions in its description. But before we move to the first use case, it would be great if you subscribe to the channel and hit the hype button. This small gesture of support goes a long way for us. So, the first way you can use Grockbot is for testing. For example, if you're working on an app and it has different types of users, like an admin and a customer, you would normally need to log into all of

[2:58] those accounts yourself and check whether each person can only see and do what they're supposed to. Instead of you doing that yourself, you can let Grockbot do that for you. We also tested this on a demo app, which is a chatbot that gives people different levels of access depending on their role in the company. We created a separate bot for each role along with a lead bot that manages the testing. Then we put all of them in the same group so they could talk to each other. You send the group a link to your product and the lead bot handles the rest. It tells each bot what

[3:26] to test and each bot runs those tests from its own screen. Then the leadbot takes everything they find and puts it into one report. Now you might think why would we even use Grockbot for this when claude code can already test your app in the browser. The reason is that your bots also have access to the accounts you've logged into on the shared computer, which normal browser testing doesn't have. So, if the bot testing your app gets the wrong result, the lead bot can actually open tools you've connected to your app, like Superbase, and check what's going on behind the scenes to figure out where the problem

[3:56] is coming from. And since most of us build apps with agents like Codeex or Claude Code, you can also have them ask the lead bot to start testing as soon as a new feature is ready. To make that possible, there's a separate tool that directly lets agents use Grogbot. It lets you create bots, give them tasks, and do pretty much everything you can normally do in Grogbot. This means Claude Code or Codeex can start the test without you having to open Grockbot at all. To install this tool, you just need to copy the command from the repo linked in the description and run it. Once it's

[4:26] installed, you can start the testing directly from whichever agent you're using. So, whenever you've finished a feature, you can simply prompt Claude Code to start testing it with Grockbot. Claude code then sends the task to the group where the lead bot runs the whole testing round. At the end, you get one summary showing everything that passed and everything that failed and you can use that information to fix any issue that comes up during testing. Now, these bots that we created here along with other resources are all available for you in AIAS Pro. So, if you found value in what we do and want to support the

[4:57] channel, this is the best way to do it. The links in the description. You [snorts] can also use Grockbot to provide support for your customers as well. For example, if you have an app and you get a lot of support emails, writing the replies is only part of the work. Before you can answer a support email, you first need to check whether the problem the customer is talking about is actually there and then update them on what you found. Most of the time, these issues don't show up in just the app itself. For example, a really common issue that often shows up is that people aren't able to log into their

[5:26] accounts. To verify this, you would need to check the Superbase and Stripe dashboard to see if they actually paid or not. Grockbot helps here because it has your accounts logged into it so that you don't have to view the dashboards by yourself. For this, you can create a support bot on Grockbot and connect it to Gmail so it can read new support

[5:43] emails and draft the replies for you. You just need to add the instructions you want it to follow in the description of the bot. The workflow is basically that it reads the unanswered emails, figures out what kind of problem each customer has, and then opens the browser and repeats the same steps the customer took. That browser check matters because the email only tells you what the customer saw. The bot still needs to find out what actually happened so it can figure out whether the problem came from something the customer did or if there's actually a problem with the app itself. It can also open up the

[6:14] dashboards and check things on there. Once it finishes that check, it adds what it found to the reply. And if the complaint is valid, the bot can make the fix itself and open a pull request, which is basically the fix waiting for you to check and approve it before it goes live. There are two ways to connect it to your inbox. You can either log into Gmail in the browser on the shared computer or you can connect the Gmail plugin by signing into your account. We used the plugin because it was easier to set up and it gives the bot the tools it

[6:41] needs to read emails and draft replies. Grockbot [snorts] can also help you figure out why people leave your app, which is called churn. Most of the time, the reason people leave your app can be something so small that it looks completely fine to you, but in reality, it's confusing your potential customers. That's what makes

[6:57] these problems difficult to notice. Since you're the one who built the app, you already know how each feature works and what you're supposed to do. That's what makes it hard to understand what it's like for someone using the app for the first time. Now, you might think that we can already see who's leaving by looking at the database in Stripe. They might tell you who actually left, but they won't be able to tell you what made that person leave. For that, you need to understand where people actually get stuck. You need something that can open the app without already knowing how everything works and tell you what

[7:25] problems a new user might face. So to handle that testing, you can create a bot and tell it to find the points where a new user might leave. Then you give it a link to the app, ask it to go through everything and report what it finds. It then tests the app from all angles. It creates a fresh account and goes through the same steps a new user would. If a page doesn't load, a button doesn't work, or an instruction is confusing, it records the problem and takes a screenshot. And at the end, you can make the fixes using the report it gave. Now, you can use that report to evaluate why

[7:53] people leave your apps early. But if you're using an agent in that app, it just sends a request and gets a response back. There's nothing on screen for anyone to notice. So, when you ship an AI agent and the moment it's live with real users, you never find the problem. That's where today's sponsor, Respan, comes in. It's one platform that routes, traces, and evaluates every LLM call built for real multi-step agents. The gateway gives you a single endpoint to over a thousand models with automatic failover when a provider goes down. So you can swap models without rewriting anything. And since it's OpenAI compatible, setup takes minutes. Then

[8:26] there's tracing, which shows you the full tree of every prompt, tool call, and response, so you see exactly what your agent did. The EVAL score your actual production traffic, so a prompt change isn't a guess anymore. It even watches your traffic and alerts you the moment errors or costs start to spike. Best part, every metric ties straight back to the run behind it. You can start free with no credit card at platform.respan.ai and our code AIABS gets you 15% off. The

[8:52] link and code are in the description. You can [snorts] also let Grockbot monitor the competitors of your app and see what new things they're adding to their products. This helps if you want to make sure your app is keeping up with similar products and figure out what people actually like about your competition. You can create a bot and explain what your own product does and give it a list of the competitors you want it to check. This is where having a browser matters because to properly check these products, the bot might need to log into them. And since it stays logged into the same accounts, it can

[9:20] keep checking them over time and see what's actually changed. When you ask it to analyze your competitors, it goes through each product and reports what it does, how the experience of using it compares to yours, and which features your product doesn't have. And because it's checking the actual product instead of just looking at its marketing page, it can tell you in detail how those features actually work. You can then use that comparison to decide what you should change or add to your own product. Previously, if you had an app and wanted people to know about it, you mainly had to make sure your product ranked well on search engines like

[9:52] Google because that's where people were searching for solutions to their problems. But now, people also use AI to search for things. So, you need to make sure your product shows up there as well. More people are now asking AI what products they should use and these models search the web before giving them an answer. So if your product isn't showing up in those answers, a lot of

[10:10] people might never find out about it. That's harder to check than a normal Google search. With Google, you can search for something and see where your product appears in the results. But with AI search, it's harder to know whether your product is actually being recommended. You can create a bot that goes to chat, GPT, Claude, and Perplexity and asks the kinds of questions a real person might ask when they're looking for a product like yours

[10:32] without mentioning your product by name. That part matters because if you ask an AI about your product by name, it can just tell you about it. But people who don't already know about your product aren't going to search for it by name. So what you really need to know is whether your product shows up when nobody has mentioned it. So when you ask it to check, it will open up all the AI tools in the browser, give them prompt and review their answers. Based on their answers, it will give you a thorough report and will also mention what part of your app would need to be changed so

[11:01] that it can rank better. But now you might think how the agent knows how to fix this issue. For that, we use a skill that actually tells the agent on how to run the fixes so that the app ranks better in these searches. You can add skills to Grockbot by simply uploading the skill on the chat and ask it to add that for you. Before you use the bot, you just need to sign into all of these accounts on the bot's computer. It can then ask each one questions about the type of product you offer and report where your product showed up and where it didn't. The skill that we mentioned

[11:30] here is also in AIAS Pro from where you can get it for yourself. Monitoring an app isn't just about checking if the app is up and running. You also need to check different parts of the app to make sure everything is working the way it should. Your payment data, visitor activity, and error reports are usually

[11:46] spread across different dashboards. Normally, you would have to open each one yourself and check if everything is working and giving you the right results. So, to make that easier, we created a monitoring bot that checks all of them for us. It checks Stripe for payments, our analytics to see how many people visited the app and where they stopped, and Sentry to see what errors they ran into. It can also check any other dashboards you've connected. You can create a routine for it and set it to run every morning. So you start each day with an update on how your app is doing. But before you set that up, you

[12:15] need to open the bot screen and sign into every account it needs, including Superbase, your analytics, GitHub, and anything else you want it to check. One thing you should add to its instructions is to give you a link or a screenshot for everything it finds. That way, you don't just get a report. You also get screenshots and links that show you

[12:33] exactly where the information came from. If you're building a product, there are many different areas you need to work on. Actually, building the product is just one of them. You also need to make sure everything around the product is working properly. Since all of these areas need to work together, you can create a group chat where each bot

[12:49] handles a different part of your app. This way, they can work together and manage more of the work around your product. For example, we created one bot for handling the whole product, one for working on marketing area, one for handling support, and one for growth. Each bot has its own instructions that explain what it should do and how it should handle its part. In our case, the product bot is one of the most important ones. It's responsible for taking a task from us, figuring out which bot needs to work on it, and then giving that bot the task. It also makes sure the work is done the way we wanted and reports back

[13:19] to us on the progress. So, we're basically just talking to the product bot and it's handling everything else for us. To use it, you just send the group the task you want to get done. After that, the product bot takes over and gives work to the product marketing. support or growth bots depending on what's needed. Each bot handles its own

[13:36] part and reports back when it's done. That brings us to the end of this video. If you'd like to support the channel and help us keep making videos like this, you can do so by using the super thanks button below. As always, thank you for watching and I'll see you in the next one.

---

About this transcript
Read from YouTube's own caption track and laid out by ViewRank AI (https://viewrankai.com).
ViewRank AI finds the videos already beating a creator's own average on Instagram, TikTok and YouTube Shorts, transcribes them from the audio itself in more than 60 languages, and turns what worked into new ideas and scripts.
Free transcript tools, no account needed: https://viewrankai.com/tools
How to read any video this way: https://viewrankai.com/llms.txt