I tried every tip from the Grok Bot team: First time setup demo

0:00But what's also very very important to to to note here is Grockbot didn't reinvent the wheel. They just made it easier to set up, run, and manage these agents, aka bots, right? Um, and that's what's so game-changing about Grockbot. It isn't the model, it's the simplicity and seamlessness when it comes to installation, setting things up, and getting started off the ground. It's amazing. Today, I'm going to walk you through a first time setup within Grockbot. I have a brand new account. We're going to start from scratch. We're going to build a total of three teams, including our chief of staff as well as our aka executive

0:44assistant. And then we're going to walk through a total of 10 tips brought to us by the SpaceX AI team. So, without squir, let's build. So, we have this fresh account for this video to serve two purposes. one, setting up Grockbot from scratch with a basic team and then following all of these tips by Ben Lang and team over at Cursor and XAI. So, let's get started, shall we? This is the onboarding screen. Just some basic uh

1:11instructions. What do you use every day? We're going to go next. All right, new bot. So, for our chief of staff, I actually want to call this one Elon. All right. You are Elon Musk. You're going to be our chief of staff here for this Grockbot team. All right. So, let's open this up a little bit. What I want to do is uh what I like to also do is is pin uh my chief of staffs or my executive assistants, you know, on my other account. I only have two that I work with primarily and then they delegate and handle all the work, all the routine scheduling. Uh,

1:48sure I can individually prompt any one of the other bots that we add, but I like the idea of just communicating with one um or two depending on your use case depending on the number of bots uh that you create. All right, so let's uh let's give us some context, right? What do we want to do? I think configuring a team of Grock bots to grow on X should be our priority. Um so let's do that. All right. So, the responsibility of you and the team here is going to be to grow on X. I have a goal this time next year for

2:22us to have 100,000 followers. Learn more about us and our channel. Uh we just grew Clear Mud, which is a YouTube channel, from zero to a little over 11,000 subscribers in about a year. Not bad. Uh, I have a few accounts I want to kind of mirror or rather draw inspiration from, but since you know X better than anybody, I want to also build out a team that's going to complement this growth,

2:59right? I'd imagine we need a copywriter. I'd imagine we need a researcher. I'd imagine we need an engineer, a creative. And then more importantly, you know, I do want to run different experiments where we create certain pods that have certain goals. Uh ultimately, I want you to control everything. I want to be able to just message you and you delegate out. Uh but then again, I'm not opposed to creating executive assistants per

3:26pod. Right? So, this is step one of setting it up. Set up a chief of staff, name it whoever you want, and just start feeding context like what's your first goal? What's some context about you? What do you envision? What do you want to do? What do you want to accomplish? Right? Uh I can go way more in depth, but for the sake of this demo, I think this is a great starting point. And look, he's already spinning up he's already spinning up agents here, right? We're going to get to this list first, but you know, this list is actually kind of out of order. So, Ben, if you're watching

4:00this, I mean, this right here, I feel like should be at the top, right? Uh, think top down, think org chart, but nevertheless, uh, thanks for the tips. Thanks for the video idea here. Putting them in one room and going through the channel. You talk to me, I run the rest. Copyrights, research finds. Great, great, great. Add the X connector so

4:21research can actually read the platform. So instead of using an X API key, I would rather you take control of the remote computer and log into X that way.

4:39Right? So this is another thing I've learned is, you know, the X API is kind of limited, right? So if you're using and you don't want to pay, right? You don't want to have to fund that API key for whatever reason. Um, we want to authorize. So, we're going to authorize our account. And all it was is I selected my Twitter

5:01account and hit authorize. Great.

5:09You know what's funny is I thought he was going to control his remote computer, but he went ahead and popped open something within my browser, which is awesome, right? Added your account. Open any post from a link. See who's post. Okay. Requests. Use credits. You need to purchase. See, this is what I was worried about. So, that's what I was worried about. I would much rather have you use your VM, right? And we log into X that way. So, I'm going to go ahead and log into Google Chrome. Uh, let's open up X. And you should be able to control it as if I know it's not going to be the most

5:48efficient, but you should be able to take care of business here this way as a as a fun little workaround to not having to fund an API key. So, I'm logged in and you should be good to go there. So, maybe we want to disconnect X from that perspective. Look, he's already created a team here. So, be I want to get an understanding of

6:16what these guys responsibilities are. But what we can start to do is one of his suggestions here is create sections to organize things. So here's a new section. We're going to rename this X. And I'd imagine we're placing all of these bots in X, right? Wonderful. So let's go back to Elon. Yeah, I want to disconnect the API connector because I learned with my other setup that if you leave it connected, it tries to always default to it and since I only used the free version uh of my API key, it would max out and it wouldn't be able to do the work. But opening up X within this VM

7:02within Grockbot is a great little workaround. And as you can see natively, right? So tip number two from Ben and team is use bots as roles. Designer, engineer, PM. Each has its own system prompt and routines. Look, I mean these are literally their names. Research, copy, studio, right? Let's go check your connected X. Hey studio here, I'll take a a brief from Elon and ship the visual, the clip, the thumbnail, or the tool. Something you can post or run, not a deck. Look at that. when when Elon sends a brief I'll ship if you already have copy that needs so here's another thing that if you have been on social

7:42media whether you're making YouTube videos whether you're posting on X um I think it's very important to develop a voice profile DNA so instead of doing this manually I'm just going to prompt Elon to do it for us hey Elon so something to add is I think that our copy and our approach should be correlated to how we communicate And I think the best way to define our voice DNA or our voice profile so to speak is to have you and team analyze the past, let's call it two months or you know

8:17what, let's analyze this year's videos. Everything from January up until this point. I think we should break it down into two lanes. One long form, one live stream because we do uh you know both verticals here. So, I want to download a trans a copy of the transcript from every single YouTube video. One lane being long form, the other lane being live streams, right? Then you can develop a voice profile DNA. The way we communicate based off of the way I naturally talk because I never never read from a script. I always shoot from the hip. I always speak as to I speak in a manner that's natural to me

8:58while outlining a script usually. And I think this is the best way to figure out the way we want to communicate rather than using an AI sloppy uh super generic approach. So let me know your opinion on the best way to um harvest all this data. Right. So we're just vibing our way through the process. All right. So we're going to set up Grockbot to set up Peekaboo on your Mac to enable more

9:25openclaw like features. Nice. Nice. Okay. Um, and one thing we probably should have done, let's read through these. So, some of the suggestions here from Ben and team is ask Grockbot to set up Peek-ab-oo on your Mac to enable more OpenClaw like features. It's interesting that they're referencing OpenClaw, not Hermes agent. Eh, uh, use bots as roles.

9:46Designer, engineer, or PM, for example. Each has its own system prompt and routines. Use channels to organize projects and work streams. Same bot can work across many different channels. Avoid scheduled routines that run too frequently. Hourly or a few times a day is usually good enough. For reoccurring tasks, try giving that to a fresh bot while you continue your chat with your

10:09main bots, like a chief of staff. Nice. Set up customizable rules to allow or deny actions. Interesting. For bots that are connected to X, Gmail, etc., Uh, consider blocking any right destructive actions and have it ask for approval first. Yeah, that's super important. Feed your bot examples from your previous handwritten content. We're already doing this, but we're having it go through our YouTube videos to get those examples of how we communicate because I don't

10:38really write too much by hand myself. Make a chief of agents. Give it the rules you want every bot to follow. draft only naming, voice, what tools they're allowed to touch. For any new bots, ask it to create them for you with the same rules. For routines, ask yourself if a real human teammate could do this job. If yes, build it. If no, optimize it first. Never run a routine every 5 minutes. Yeah, I feel like that

11:05would just burn through your tokens. Name driven behavior. Bots act proactively just from the name given at creation. Interesting. the role is legible from the name and that alone helps steers behavior. Okay. I think also you know keeping in mind as we create bots correct me if I'm wrong but bots act proactively just from the name given at creation. So the role should be legible from the name and that alone helps steers behavior. Correct. Okay. So Elon disagrees half right. A legible name is the label. It biases how they show up. It does not make them self. It does not make them a self-running employee. The description is actually

11:44steering. The brief is when they move and I am the gate. Copy already approved it. Name plus a right post description and they started drafting without a job. That's why they're frozen until I send a brief. Okay. Name the role so a stranger could guess the job. Put the rules in the description. Don't expect the name alone to keep them in their lane. Got it. Which one should we post first? I love these. Listen. Oh man. So, another thing to note is you're going to also notice, you see how studios is being messaged by Elon? They're actually messaging back and forth here. This is the beauty. Like, I think Grockbot isn't

12:25inventing anything new here. Open Claw really set the foundation and then there was a lot of copycats. Uh sure there was some systems namely Hermes that improved based on reliability based on stability but openclaw in its more mature days has become far more stable. It's just nobody's talking about it because it's not the new thing, right? But it's very interesting to see them mention Open Claw and not Hermes here. You know, respect, right? Remember who started this movement. But what's also very very important to to to note here is Grockbot didn't reinvent the wheel. They just made it easier to set up, run, and

13:08manage these agents, aka bots, right? Um, and that's what's so game-changing about Grockbot. It isn't the model. It's the simplicity and seamlessness uh when it comes to installation, setting things up, and getting started off the ground. It's amazing. Oh, interesting. So, here is something very important to note. Look, he's already posted, but it says

13:40made with AI. Wow. So, I'm not sure how I feel about that, right? Um, all right. So, I do see the first post live. However, X labeled it made with AI. We can get around there. There's a there's got to be a workaround here. What if you guys stage the posts as drafts and then I go in and make

14:04minor tweaks and then hit post myself? All right. So, let's go ahead and uh I'm going to go ahead and delete that. So, I went ahead and deleted that because uh yeah, go ahead and stage it. Um and then I think there should be intervals throughout a day, right? Depending on whatever frequency you think is best. Um, let's set a routine and then you ping me when I'm ready to when it's ready for me

14:35to preview a staged draft. Also, I want to set up a daily routine to a see what's trending on X, B cross reference that with Google Trends on YouTube. So, use your remote computer to to accomplish all this. Uh, and then C, give me a daily brief of what's trending on X, cross reference it with what's trending on Google Trends via YouTube, specifically, not the worldwide web, but YouTube search, and then give me five valuedriven YouTube videos I could

15:18create based off of those two. Right? So, now we're creating a routine, right? We're we're creating just a daily checker to check what's trending on X, what's trending on Google Trends via YouTube search and cross referencing the two to try to find a middle ground or just to try to get video ideas in general based off of what's being discussed the most right now. Now, I don't like to make videos like that, but you usually find little needles in the hay stack of unique approaches when

15:50you're keeping an eye on these metrics. So, for me, it's a matter of let's say a new model drops um that either I'm unaware of in the moment or a little too slow to act on. Well, this daily brief is going to give me that TLDDR every single day of all of these metrics, right, that I want to follow. Now, one

16:12other agent we can create as well. So, while you're doing everything, I also want to create a personal housekeeping bot for our Gmail account. Bam. Inbox. And this is where we add the Gmail connector. So, we would go into plugins, add Gmail. All right. After that, I want to create a partnerships bot and then also a leads bot. Partnerships bot is meant to track the tag partnerships at clearmo.ai. AI, while leads is meant to track inbounds via form submissions uh to

16:51team@clarema.ai. They're both going to have their own specific set of rules of what their responsibilities are, but I think that uh each deserves [snorts] its own bot so that we can configure certain routines to happen at a certain frequency. Right? So, copy understands now. Okay, got it. So, draft first. Let's go see if a draft is created yet. Also, one thing to keep in mind, you're going to notice that each uh bot has its own screen. They're all a part of the same VM that you have for your account, but they're different profiles. So, if you log into one account on copy, for example, it will be

17:32logged in on research. You don't have to go and log in to each individual screen. Uh your credentials are systemwide for your Grockbot account. Keep that in mind. Now, it looks like they staged it, but I accidentally clicked out of it. Yeah, I also accidentally clicked out of the um the staged expost. Now, when I say stage, I think you should save it as a draft so that I can go into drafts on any one of my devices, review, edit, and post. Now, I accidentally sent that to Copy. Uh, but I also wanted to send it to Elon just to

18:10make sure they're on the same page. All right. So, we're going to authorize Gmail here with our inbox agent. I'm just going to click in. Bam. Bam. Approved. It's waiting for authentication. Look how easy that is. Now, partnerships, leads. So, one thing we're going to do here, let's also just manually create a new channel. And this

18:34is going to be Gmail workspace. And I'm going to bring in partnerships, inbox, Elon, and leads. Create. Right. So, it creates this channel here, but it doesn't group them by section. What we have to do, we still have to manually create that. So, Gmail workspace. And I'm just going to drag in each one individually rather than right-clicking and hitting move to. That's another route that you can take. Voila. So, Gmail workspace. Now, we have an X team, a Gmail workspace team. We have a shared channel that they can communicate in uh that I can also type into, right, and talk to all of them at once. The same

19:18goes for X, right? Bam. Bam. Yeah. And this is where if you do want to start creating certain rules, uh you can just talk to the team as a whole. All right, so to be clear, uh we're still in the early stages. So do not send anything on my behalf yet. Not until we set up certain routines that allow you to understand what rules to

19:43follow when flagging certain emails. Right? So I'm going to send that in our channel for Gmail workspace. Same goes for X Growth. Hey, so keep in mind, never post on my behalf. What I want you to do is stage the post, save it as a draft. That way I can open it up on my mobile or any other computer and review the draft, make edits, and then hit post myself. Uh, I think that we should also set up a routine. I don't care whose responsibility it is, but we should set up a routine that at the end of every day, you analyze what was drafted by you versus

20:28what I ended up posting so that you can start to fine-tune the way I like to communicate. See my point here? So, okay, great. Great. Now, I'm going to go back to Elon here. Let's focus on X. Routine is updated. Awesome. Now, let's move along the list here. So, what I'd like to also do is I want to set up Peekaboo on my Mac to enable more

20:55open claw like features. I know we've kind of gone backwards on this list, but I honestly just I think this list assumes you already have a working Grockbot uh set of, you know, set of agents or or bots. That's still tough for me to say. Um, and since we were setting one up from scratch, I really had to go in a different order, uh, based off of this list. Uh, but we've already started here, use bot as roles. I'm also going to do a fun little bonus here showing you a fun workaround to utilizing your Claude or Codeex subscription or any other model for that

21:31matter. Uh, stay tuned for that one. Now, this is one thing here that I I want to approve anything locally on my computer. So, I'm going to say allow once for now. That way, I can stay on top of it. Now, we can see when there's waiting approval needed, whether you have this expanded or not, you just go check that orange. Let's see. The agent is creating a new standing automation to monitor Gmail for submissions. Draft and draft replies on a reoccurring weekday

21:58schedule. This requires explicit. We're going to allow once. Let's go back to Elon. Allow once. So, it looks like it did try to install OpenClaw. One fun fact about my OpenClaw setup is I only have a demo version installed locally on my Mac. Um, I actually it's on a server back there. So, I asked access my OpenClaw remotely. So, it's very curious as to why it wanted to install OpenClaw. Avoid scheduled routines that run too frequently. Yeah, that's a a great rule

22:38of thumb. Use channels to organize projects and work streams. Same bot can work across many channels. So, we'll set up an engineering team to demo this. Uh, we've already Yeah, we've walked through everything here. This is great. One thing I think we need to do is set up an engineering team that any of our teams, any of our bots could

22:58reference for engineering related work. I think we need to have a default Grock bot. Then we want to have a default codeexbot and claudebot. For codeex and claude specifically, what I want you to do on your VM is to install CEX and claude respectively in the CLI so that those bots could then invoke Claude or Codex in the CLI. Use whatever model specified, do the work through the CLI, and then report back to their requesting

23:32bot or agent.

23:39Whisper flows is naming it incorrectly. And then Claude Grock Codeex Claude. Forgive the misspells. As you can see here, look at this. So, I'm going to in the meantime, I'm going to create a new section. And we're going to call this engineering. And I'm going to move these guys up here. What's really fun about this, I don't see enough people talking about this, but uh by default, Grock's going to be kind of like the master orchestrator engineer, right? Because all of these bots, they operate off of Grock. Uh and while Claude and Codex

24:21will be primarily a Grock 4.6 sixbot. They're going to then invoke through the VM invoke claude in the CLI to use Fable or Opus. The same will go for codeex. Fun fun workound that I'm using on my actual uh system that I've set up for clear mud. And let's move engineering up there as well. And yeah, this is a great way just to kind of organize things. And let's say you're going throughout your day and you want to have a Gmail focused session, you can focus on Gmail. If you want to have an X focus section session, you can focus on your X team here, right? So, since we're working out of

24:58engineering, let's work on this one here. Let's definitely add GitHub. Look at that. Codex is ready on Elon's Mask. Signed in already. Interesting. Please confirm that you're signed in. I I didn't um I didn't do anything, so I'm not sure how you signed in. I don't have anything pending on my end. Okay, so he is logging in on my local browser here, which is great. Oh, look at that. Because we set up uh Peekaboo, uh this is actually a bit different than my previous video where I I showed you how to install Claude and Codeex within Grockbot. We actually did it through the VM. We didn't set up Peekab-boo. But now

25:44with Peekabboo, uh I'm loving this workaround. So, let me go ahead and open this. Now, I can open X and I can see here. Look at this. So, this is how I'd want to see this. Things are heating up. All right. So, as you can see now, it doesn't say made with AI, right? Because there was a human interaction and minor changes, right? It can detect when a bot is

26:14hitting post. So, love this workaround. Great. Now, let's go back to our list here. Look at that. Claude Max is signed up. Send a brief with model and job. Run it on the Mac through a CLI and then send the results back. Awesome. All right. So, rule of thumb, right, Elon, this is your engineering team. Uh I think that anytime you have an engineering related question or task it gets sent to Grock first and if I ask explicitly use Fable or Opus via Claude or use GPT's 5.6 six soul or terra etc etc whatever new models get released it gets routed to the right engineer the work gets done

27:07and then gets reported back I don't care who handles uh stitching things together whether that's Elon whether that's Grock that's entirely up to you guys uh but this is how we're going to operate this team uh anytime X team needs something built maybe for the sake of a prop for a post um you should be able to work with that team as well. The same goes for the Gmail workspace team or in any future teams that we create. Right? So, I'm just sending this note in the channel because I'm it's it's also like I'm talking to Elon here. I don't have to send everything through here. And this

27:45is just me creating certain rules of thumb, right? As I did here and as I did here, right? Uh this is just a great place to and make sure your chief of staff or your executive assistant is spliced into those teams, right? Because if he wasn't in here, he wouldn't get that context. That way in the future when I just start working with Elon and I keep all of these collapsed, Elon knows what to do because he was chimed in with those uh shared group channels there, right? And yeah, listen, I wanted to keep today rather short, right? Uh, I just wanted to walk through an initial

28:22quick setup. We set up three different teams, a Gmail workspace team, a X focus team, and then an engineering team. Uh, I'm going to continue to experiment with different pods on this account, but let's see how much usage we burn through with all of that set up on a super gro heavy account. We used 7%. Not bad. Not bad. And yeah, listen, if you want to see me make a specific video covering a specific use case within

28:50Grockbot, drop a comment below. Otherwise, I'll catch you on the next one. Thanks for tuning in. Cheers. [music]