# How To Use Grok Bot For Beginners

Channel: AI Bureau
Video: https://www.youtube.com/watch?v=E2VdYiAVG9M
Duration: 14 min
Language: English
Words: 2508
Transcript page: https://viewrankai.com/tools/youtube-transcript/E2VdYiAVG9M

---

[0:00] If you haven't used Grokbot yet, well, let me tell you something. You are in for [music] a ride because unlike most AI chatbots that can tell you how to do something, Grok can actually sit down at a computer and virtually work like a person across multiple platforms. For instance, it can jump between apps, handle files, fill things in, build reports, and it can even use browser tools while also having access to a terminal. However, this insane capability also carries some serious risks. Because if you give an AI bot access to your browser, your files, and your accounts, just how much freedom would you actually want to give it? My

[0:39] name is Lewis, and this is the AI Bureau. In this video, I'll tell you how to set up your first Grokbot, give it useful work, teach it repeatable tasks, and basically keep the risky stuff under your control. So, before we hand this thing the keys to anything, let's get a very important fact out of the way. You see, Grok and Grokbot are not the same product. Regular Grok is the AI assistant most people will already recognize. You open a conversation, ask it questions, upload files, get it to

[1:14] research something, or create content. Then, it gives you the result inside that conversation. Grokbot takes that relationship quite a bit further because it has access to a persistent computer in the cloud complete with a browser, files, and a terminal. So, instead of only producing an answer, it can actually go into the tools where the work needs to happen. If I were to compare, I'd say that regular Grok is like calling a very smart colleague, for instance, and asking, "How should I do this?" But Grokbot is giving that colleague a desk, a computer, and basically the job itself. And unlike a normal chat session, Grokbot doesn't disappear the moment you close your

[1:58] laptop. The bot could keep working in the background, hold on to useful working context, and even stay signed in to tools that you've approved. You can also create several bots for different jobs, instead of forcing one AI assistant to handle every other thing. So, you might have one bot for research, another for admin maybe, and another that handles a specific content workflow. Although, you'll need an eligible paid Supergrok or Cursor plan to use it. I mean, with all that

[2:26] capability, free would be pushing it. Once you have access, though, the first decision is pretty straightforward. What job are you actually going to give this bot? And that brings us to setting up your first bot. The idea behind setting up your first bot is to understand if that Grok bot can do very specific tasks for you. Like, I wouldn't start by creating something called my AI assistant, because I wouldn't want to throw every random task at it. Giving it one clear job makes it easier to establish what you expect and build useful context over time. I mean, imagine hiring somebody new, only to

[3:01] point at a laptop and say, "Good luck." You know, it's like, "Good luck with what, bro?" You'd actually have to explain the scope of work and what they're responsible for. And of course, what's restricted without permission. So, give the bot one area to own. Rather than saying something like, "Make a report." It's always better to say something like, "You're my research assistant. Find reliable sources, compare the information, and prepare reports for me to review." Now, this may be a cliché example, but the idea is that it gives the bot some permanent rules to work with. You could tell it what its job is, which sources it should

[3:36] use, what a finished result should look like, and yes, where it needs to stop and ask you first. Next, give the bot access to tools that it would require to complete the task. For supported services, you can even connect them through plugins. And if there isn't a connector, well, GrokBot can often use the website through its browser instead. Now, when it hits a login, this is an example of where you take over. You enter the password, the passkey,

[4:03] two-factor code, or CAPTCHA yourself. Then hand the computer back. Don't just paste sensitive login detail into the chat. And once you've logged into a service, that browser session can stay active on GrokBot's cloud computer. We'll come back to why this is important later, because that's a catch here that beginners really need to be aware of. But for now, keep the first job harmless so that you can learn and understand how it works. Maybe just ask it to research something, inspect some data, or prepare reports. You know, just standard getting to know a bot stuff. Because before you let it do things on your behalf, just see how well it understands what done

[4:40] means to you. Now, before we move on, one thing worth keeping in mind is that tools such as GrokBot change and evolve insanely fast. New models, agents, features, these keep on showing up, and it could be pretty hard to keep up with which ones are actually useful. And that's why the easiest way to stay on top of things is to subscribe to the AI Bureau newsletter. We cut through the noise, explain the biggest AI stories, point out the tools worth knowing about, and show you how to actually use them in everyday life. So, be sure to subscribe to the AI Bureau newsletter using the link in the description, or scan the QR

[5:17] code that's on the screen. Now, let's go back to understanding GrokBot and see how we could give it tasks properly instead of using it like some regular chatbot. Also, basic AI rules still apply. So, don't type something super vague like research Nvidia. I mean, how can you then expect a bot to know what you really want? Do you want a company overview, information about competitors, financials, recent news, a two-page report, 20 bullet points? I mean, leave all that unspecified, and the bot has to guess what you want. A much better instruction would be something like research Nvidia, compare it with three competitors, use current company and

[5:57] market sources, create a short report with links, and flag anything you can verify, and also leave the finished report for me to review. Do not send or publish anything. See how this changes things? You technically didn't tell the bot which button to click first. In fact, you just told it where the finish line was, what information it could use, and where you hold authority. So, it's more like handing work to a person rather than writing a traditional prompt. And honestly, you would do the same with a person. You wouldn't say, "Open Excel," right? You'd say, "Prepare the weekly sales report, check these figures, use this format, and run it by

[6:35] me before sending anything." And for the things that can change over time, always tell it to go back to the actual source and verify the information for any changes from the last time. Because even though a bot can remember useful context, XAI itself warns that memory should not replace the source. And once you start giving it jobs this way, you start getting useful outcomes. So, with all of this in mind, what can you

[7:00] actually hand over to Grok Bot today? Well, there are five good places to start. Now, the first obvious use is research, of course. You could give Grok Bot a company, product, or market to investigate, have it check several sources, compare what it finds, and then return a proper report with links for you to review. And this is probably one of the safer places to begin, to be honest, because the bot is mostly gathering and organizing information rather than changing anything. You can even ask it to include screenshots, timestamp, and basically anything it couldn't verify, which makes it easier to check the final result. The second use is inbox and admin work. For

[7:40] example, it could go through approved emails and other work sources, pull out what actually needs your attention, organize it into a digest, and even prepare responses for you. That means less time sorting through your inbox and more time dealing with the messages that actually need your attention. Third, you could use it for recurring reports. Maybe you have to open three separate dashboards every week, then copy data across spreadsheets, and then write report summaries yourself. With Grockit, you could just get it to collect that information, follow your steps, and prepare the report in the format you normally use. Voila. Number four is content workflows. Now, you might ask it

[8:21] to research a topic, maybe gather useful sources, organize those findings, prepare a brief, and then save everything in the right place for whoever handles the next step. So, instead of just giving you text to copy and paste, the bot can gather the research, prepare the brief, and save it where your team needs it. And Grockit being able to do that, I mean, that's pretty cool. And fifth, it could collect information from websites that don't necessarily have a neat connector or an API. Say, for example, you regularly need prices, listings, or maybe other public information from a handful of websites. Grockit can use the browser to gather it all and put everything into

[9:00] one table or file. Now, these jobs are not flashy on their own, but I mean, that's kind of the point, right? The sweet spot here is work you already do again and again, which takes several steps, but still has a clear result at the end. And once you identify one of those jobs, you can finally stop manually asking the bot every single time to repeat it. Yes, you can actually teach Grockit the process itself. Let's see how that works. Let's say Grockit handles one of those jobs exactly the way you wanted, and you probably don't want to explain the whole process again next week. Well, that's where you teach

[9:36] GrokBot your workflows and also create routines so that it could take over the repetitive tasks. And this teaching is basically the bot developing skills. A skill is basically the bot's recipe for doing a job. You could save the steps, the rules you normally follow, what the finished result should look like, and of course, which actions depend on your approval. And you don't really have to build that recipe from scratch. You could ask the bot to do the task once

[10:04] and then correct anything it got wrong. And then simply ask it to save the process you just used as a skill. Now, GrokBot also has a feature called teach a task, although XAI says it's still being rolled out gradually. And yes, availability can vary. So, instead of describing every single step, you can use this feature to actually perform a browser workflow once while GrokBot watches. And it then turns what you did into a draft skill. But I'd pay attention to the word draft there. One demonstration won't teach the bot every odd situation you might run into. So, test the skill first and add rules for what it should do when something goes

[10:47] wrong. Setting rules for possible scenarios could really save you a headache. Once that process works reliably, you can finally turn it into a routine. The easiest way to remember the difference is a skill tells the bot how to do the job. A routine tells it when to do it. So, for example, you could

[11:05] tell it, "Every weekday at 8:00 a.m. collect yesterday's numbers, run my reporting skill, leave the report here for me, and tell me if any data is missing." And because the bot works in the cloud, that routine can run even while your laptop is closed. But remember, the order of things can make or break the process. So, do the job once, get it working properly, save the reliable process, and only then automate it. Otherwise, you're basically putting a mistake on a timetable. And that brings us to the part I'd be most careful with. Because once a bot can run jobs in your absence, you need to decide

[11:46] very clearly what it should never be allowed to do on its own. So, what should you not let Grok Bot do on its own? Well, one good rule is to let prepare anything risky first, but keep yourself in control of the final action. So, for example, drafting an email is one thing, but sending it is another. The same goes for publishing content, buying something, deleting files, or changing anything important in a production system. For those types of actions, always keep an approval step in the middle, and actually read what you're approving. XAI specifically says not to approve an action if you can't

[12:25] clearly identify what it will affect. Same caution applies to passwords and verification codes. Never paste such information into a normal conversation. When Grok Bot reaches a sensitive login step, take control of the computer, enter the details yourself, then just hand it back. And a beginner's trap here is not knowing that all of your bots share the same cloud computer. Their conversations and roles may be separate, but files, browser sessions, and command line credentials on that computer could be available across your whole bot roster. So, don't think of separate bots as separate locked rooms, because it's more like several employees having access to the same company system. If

[13:09] one account is left signed in, that access may still be there for another bot. So, only connect with the job needs, sign out when that access should end, remove sensitive temporary files, and revoke connectors you're no longer using. Basically, give Grok Bot freedom over work that's easy to check and easy to undo. For anything involving spending money, publishing something publicly, or wiping important data, always keep yourself in the loop. So, the main thing to remember is that GrokBot becomes a lot more useful once you stop treating it like a chatbot and start giving it some proper jobs. Like, give it a clear role. Tell it what the finished result

[13:51] should look like. Test the process yourself first and only automate it once you know that it works. But, just keep the order of things right during the teaching or demo process. And when money, publishing sensitive accounts, or deleting data are involved, keep yourself in the loop, always. So, what's the first job that you would hand over to GrokBot? Tell us in the comments down

[14:13] below. And if you want to learn more about ways how to use AI, then subscribe to the AI Bureau and turn on notifications. Thanks again 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