Grok Bot came out a month ago and I haven't stopped using it since.

Not because it does anything the other agents can't.

It's because it's the only one that doesn't make you configure it first.

You open it, and it's already working.

If you've never opened it, here's what you’ll be looking at:

• An app that looks like iMessage
• With a list of bots down the left you message like people
• And each one runs its own computer in the cloud, not on yours

There's a mobile app too, which Hermes doesn't have.

Now, let me show you how to set up Grok Bot from zero this afternoon, in 6 moves from 1 empty bot to a working team.

1. Buy the plan that actually gives you enough Grok Bot usage

I'm not going to pretend it’s cheap. The pricing sucks.

You technically can get in from $20 on Cursor's plan, or $30 on SuperGrok.

But below the top tiers the usage isn't optimized, so you'll hit the wall in a day.

The 2 plans that actually let you run a team are the $200 Cursor plan and the $300 Grok plan.

And for Grok Bot itself there's no difference between them. Same exact usage, so I'd take the $200 one.

What helps justify this pricing is thinking of that plan as an employee instead of a Netflix subscription.

So work out what an hour of your time is worth (I used $100). If you save 10 hours a month the $200 plan made you back $1,000.

2. Pin your first bot to the top and make it your Chief of Staff

When you open the app, you'll see 1 bot.

Right click it, pin it to the top, then go into edit profile.

Then give it a real human name, one you won't mind seeing every day. Not "CEO." Not "Chief of Staff." Mine's called Slate.

The job goes in the title field instead, so this one is "Chief of Staff."

And that field isn't decoration. It's how the bots work out who does what once you have more than 1.

Then there's the description, which is the bot's system prompt. It gets sent with every message you send that bot, so 1-2 lines is plenty to start.

And you don't have to get it right, because it learns everything about you in the next step anyway.

3. Tell it everything about you, then ask how to set it up

This is the first thing I do with every AI tool I get my hands on. Brain dump, then reverse prompt.

The brain dump is you telling it who you are:

• What you do
• What you're building
• And what you want off your plate

Then comes the reverse prompt, where you stop giving it orders and ask what it would do instead.

And the order matters. Most people open a new AI tool and start giving orders, so they only get the things they already knew to ask for.

But asking first gets you the stuff you didn't know was possible.

So use something along the lines of:

4. Pick 2-4 areas of your life and let it build a team for each

Your Chief of Staff will reply with a proposed team: a handful of bots, what each one does, and the routines they'd run.

Now, the mistake almost everyone makes here is saying yes to all of it. They build 40 bots on day 1 but end up using 4.

So cut it down first.

Pick 2-4 areas of your life you actually want managed. Mine are my app, my content, my community and my computers.

Then tell it to build 3 bots per team: a project manager, a developer and a researcher.

And it just does it. Names, titles, descriptions, no manual work from you.

5. File the bots into sections yourself

Your Chief of Staff will built the bots, but it won't file them anywhere. That part is manual.

And it's worth doing, because once they're filed your left panel becomes the areas of your life instead of a list you scroll.

So right click each bot, hit Move to, and create the section there. Tech team. Product. Research.

Then drag each bot into its area.

One last thing: check every bot has a description. Your Chief of Staff normally writes them, and an empty one means a bot with no system prompt.

6. Message the specialists directly, not your Chief of Staff

Everybody is telling you to funnel everything through your Chief of Staff and let it delegate the work.

I think that's a huge mistake.

99% of my own work doesn't go through mine. Your Chief of Staff manages the setup, so anything you want built or changed, you go there.

But the work itself goes straight to the bot that does it.

And this is where the title field pays off. When my developer bot has a question, it reads the titles, finds the project manager, and starts messaging her. I never told it to do that.

So if you gave every bot a real title above, they'll figure out who to talk to without you.

As you can see, setting up Grok Bot is one afternoon of work.

And at the end of it, you’ll have the most capable AI agent out there on your computer and even on your phone.

Btw, this email is just scratching the surface of what I cover inside the Vibe Coding Academy.

If you want to get my Grok Bot Masterclass with 9 lessons on setting your first bots up and getting them working together, plus 4 recordings of the live sessions I've run (including the one where I built my whole team on camera)…

​Join 800+ others inside the Vibe Coding Academy.​

Keep shipping,

Alex