Keep exploring · more guides
This is the full Grok Bot course, step by step.
By the end you will have your own team of AI bots that work while you sleep.
They text you like teammates, they hand work to each other, and they never clock off.
No terminal. No setup. You download an app and start talking.
I built every single thing on this page on my own machine, and you are about to watch it happen.
Set it up, build a team of bots, connect them, and let them hand work to each other.
Real builds — not theory.
Grok Bot comes from xAI.
It launched on August 11th, 2026.
It looks like a messaging app — iMessage, WhatsApp.
But every chat in the sidebar is a bot with a name and a job.
What you're watching: the real Grok Bot app on my machine. Every row in the sidebar is a different bot with its own job — and the last one is a group chat with two of them in it.
Behind all of them sits one real machine that belongs to your account.
A browser, files, a terminal, and connected tools.
It runs in a data center, always on.
Your laptop can be shut. Your phone can be off. The bots keep working.
Five bots can work at the same time on five different things.
Open any bot's screen and watch it, from your desktop or your phone.
What you're watching: the panel on the right is that bot's own screen on the cloud computer, with its Routines listed underneath it.
I run Claude Code, Hermes and OpenClaw every single day.
Those all do real work. The difference here is the packaging.
No terminal. No server setup. No config files.
You download an app, sign in, and you're talking to your first bot in about two minutes.
xAI say their own employees used early versions before it shipped.
Sales outreach, marketing, onboarding, bug fixes.
Cursor Ultra is about two hundred a month. Teams pay one twenty per seat.
On the top Grok tier, it's included.
There's a free trial, but heavy use burns through it fast.
Some people got less than a day out of it.
Go to x.ai/bot. Download the desktop app, and grab the iPhone app too.
Everything syncs, and the phone does everything the desktop does.
This is the most important lesson in the whole course.
Get this before you build anything.
With Claude Code you think in jobs — do this task, then that one.
Here you build a teammate around a theme, and it owns that theme forever.
You don't build a bot to write one email — you build an inbox bot that owns your inbox.
Cram ten jobs into one bot and quality drops.
Cram ten jobs into one mega bot and it gets confused.
Even xAI's own site shows one role each.
Click new chat, click create new bot.
You don't fill in forms — you just talk to it.
What you're watching: a real bot being created from nothing — the plus button, create new bot, and the brain dump going in.
The bot asks what you want it around for, and you brain dump.
That's the whole setup.
It renames itself, checks what's already connected —
and creates its own morning routine without being asked.
The bot writes its own description.
That description matters more than you think.
Clear, specific, one sentence.
"Looks in my Gmail and calendar to plan my day, every weekday."
If you've ever set up an agent before, you know this part.
API keys. Tokens. Half a day gone before it does anything.
The bot says: I'll check your email, please authorize Gmail.
One click. You sign in like any normal app. Done.
Because everything runs on one shared computer, you authorize once.
The bot you build next month is already connected.
The bot opens its own browser and logs in like a person would.
It pulls up the login screen and hands you the controls.
You type it yourself, straight into the site.
The bot never sees your password in plain text.
Tell it: every weekday at seven, look at my calendar and email and send me a plan.
It doesn't just answer — it saves a routine.
What you're watching: a routine being written in the real editor — a name, and plain-English instructions.
A saved, scheduled job that runs on the cloud computer.
Whether your devices are on or not.
Meetings listed. Emails that need action flagged.
It even tells you where your day is overloaded.
Same process. New bot, brain dump the role.
Point it at your channel and let it learn what already works.
What you're watching: the content bot being built, then going off to study my actual YouTube channel so its pitches aren't guesses.
Freelancer, agency, creator, ecommerce.
The role changes, the process doesn't.
Point a bot at your product pages.
It drafts descriptions in the brand voice every time new stock lands.
You don't tell them which sites to check or how to do the job.
You describe the outcome; they ask two smart questions and go.
If you're used to babying agents through every step, this takes adjusting.
You lose some control. You gain a lot of speed.
Download it, poke around for a week, never turn it into anything.
That's exactly why the Boardroom exists.
You can wire all of this together yourself with the steps above.
Or join the room where we build with agent tools like this every week, and walk out with:
A 30-day roadmap so you're not guessing what to build first.
And the Agent OS, where every agent you run shares one memory vault.
Open one chat with two, three, five bots in it.
They work the task together.
Without you asking, and you can read every message.
Watch the screen — I didn't route any of this.
What you're watching: two real bots in one group chat. Research @-mentions Content with what it found, Content @-mentions Research with the finished title and hook — then one of them says 'nothing new to add — we already locked it.' Nobody routed that but them.
Ask for this week's priorities in a group chat.
The chief takes calendar and email; the content bot takes the ideas.
The chief takes calendar and email, because that's its lane.
Then it texts the content bot for the ideas.
You get one answer back, built by both of them.
Click into their thread and read the whole thing, view only.
Some people only ever talk to their chief of staff.
If no specialist exists, it creates one.
Ask your chief of staff: can you create other bots?
Ask for video, research or reporting. It spins one up.
Message one bot from the gym — what's the status on the client report.
The answer comes back before your set is done.
This is where it stops being a chat app.
A routine is a saved job with instructions, and it fires two ways.
Every weekday at seven, plan my day.
Every Monday at eight, reconcile the invoices.
You don't build these in a settings panel — you describe them in chat.
Half the time you don't even ask.
A trigger fires when something happens, not when a clock says so.
Look at the real menu on screen.
What you're watching again — but look only at the menu this time: On a schedule, Slack message, Git event, Teams message, Linear issue, Sentry alert, PagerDuty incident.
Someone posted a fake sponsorship message in a Slack channel.
Moments later the bot sent a summary of the deal, unprompted.
One prompt, about two minutes.
A traditional automation tool takes fifteen minutes of dragging nodes.
The bot can only hear channels its app has been invited to.
It gives you the exact invite command. Run it once.
A freelancer wakes the billing bot on the word invoice.
A creator gets winning topics before breakfast.
A skill is a saved, repeatable way of doing something — a markdown file.
Every skill is shared across all your bots.
Type slash and the skill name, and it runs.
That top row on screen is a real one.
What you're watching: typing a single slash in the composer. Look at the top row — that's a real skill, learn-from-demonstration, sitting one keystroke away.
Just ask. Or upload a file.
Teams share entire playbooks as a zip.
Hand a zip of skill files to a fresh bot and it installs them.
Three starter skills are in the pack for this course.
Open the bot's computer, hit teach a task.
It records its own screen while you drive.
It studies the recording and turns your clicks into a skill.
This solves the oldest problem in automation.
There are tools your business runs on that no automation platform can touch.
Log in once, show it once, and it's a repeatable job.
A bot decided its results were unclear at one step —
and edited its own skill file to add a check. Nobody asked it to.
Nobody asked it to.
Each run adds context, so week four beats week one.
A built-in marketplace — Gmail, Calendar, Drive, Slack, GitHub, Notion.
One click, one sign-in each.
What you're watching: the real plugin marketplace inside the app, sorted by category, with an Add button on every one.
If an app isn't in the marketplace, this connects your bots to over nine thousand.
And the setup is almost silly.
From then on you just name the app you want.
And there's Firecrawl in the real marketplace.
What you're watching: searching the real marketplace and finding Firecrawl — 'web scraping, crawling, and search for AI agents' — one Add button away.
AI agents are surprisingly bad at reading the open web.
Sites block them. Pages come back as mess.
Competitor pricing pages daily. Public info on leads before outreach.
Documentation sites read properly.
Roles, connections, group chats, routines, skills, plugins.
Five real builds, simplest to most complete.
One bot. Gmail and Calendar, seven a.m. weekday routine.
Your training wheels build — it only reads, it never sends.
Gmail plus your project tool.
Every morning it pulls real tasks out of your inbox onto your board.
Tasks land on a board your whole team sees, sorted by urgency.
This build alone changes your mornings.
A research bot with Firecrawl scans competitors daily.
It messages the content bot directly when fresh topics land.
The research bot messages the content bot directly when fresh topics land.
Your idea drought, gone permanently.
An inbox bot and an invoice bot in a group chat.
Upload one example invoice and tell it to always match that style.
Check my email daily, find anything invoice related, build it in my style.
Draft the reply with it attached, and log the status.
The invoice bot messages the inbox bot on its own.
The send button stays yours. Nothing goes out without you.
Connect a meeting notes tool, then a five p.m. routine.
Every action item, onto the right board with an owner and a date.
Client actions to the client board. Content actions to the content board.
It figures that out from the notes.
Morning planning. Inbox sorting. Content research. Billing. Meeting follow-up.
Five recurring drains, each built with plain English in under an hour.
A course that skips the problems isn't a course.
Four things to know before you commit.
Adding your tenth bot adds no new risk — same machine.
But it is one basket, and every login you hand it lives there.
A Linux computer in a California data center signs in as you.
Some sites will email you a verification alert.
LinkedIn and others have terms unfriendly to automated access.
Email and calendar, low drama. Strict platforms, think twice.
There's a checkbox asking to retain your private data.
You can decline it, and the service works exactly the same.
The plan comes with weekly usage, and running many bots hard eats it.
Start with two or three. Learn what earns its place.
No model picker — it chooses, and you can't override it.
No live voice mode, no Android app.
Rough edges. The occasional error.
Judge it as a version one.
Wrong: "I need to be technical to run a team of AI agents."
Right: There is no terminal here. You download an app, sign in, and describe a job in plain English — the setup is the conversation.
Wrong: "I should wait until these tools settle down."
Right: Every platform is moving the same way — roles, always-on machines, bots that talk to each other. The habits you build now carry to all of them.
Wrong: "Buying the tool is the hard part."
Right: The tool is the easy part. The system around it — the roles, the routines, the shared memory — is what actually gives you the hours back.
Members post their wins every day — agency owners, ecom founders, course creators, solo operators across 38 countries. Real businesses, real numbers, in their own words.
Read the 158-page wins doc →This is the first agent product where installing an app is the whole setup.
No technical step at all.
It gives you a phone-first layer for the admin work.
Your heavy builds stay where they are.
If you keep hitting weekly limits on your other tools,
this is a separate pool of agent work at a flat price.
Buy it with no plan.
A subscription without a system is just a monthly reminder.
A day after Grok Bot launched, xAI shipped the model powering it.
Same foundation — all the gains came from post-training.
SpaceX bought Cursor in June for sixty billion in stock.
Millions of real coding sessions came with it.
An agent's job is long tasks with many steps.
Recovering from its own mistakes, and knowing when to stop and ask.
It ties GPT-5.6 Sol on the Artificial Analysis index.
It gained five points in about a month.
On some agent benchmarks it still trails.
Terminal Bench: twenty-six against thirty-four point six for the leader.
CursorBench is run by Cursor — owned by the same parent as xAI.
And an earlier Cursor codebase leaked into training data.
Treat company-owned numbers carefully, independent ones as the real story.
It closed most of the distance to the frontier in a month.
Every major AI company is making the same move.
Take the developer tool and turn it into an employee anyone can use.
Agents with roles, on always-on computers, talking to each other, reachable from your phone.
The app you pick matters less than knowing how to run it.
The people who get value out of tools like this aren't the ones who watch a course.
They're the ones with a system around it.
Your Claude, your Hermes, your OpenClaw, your free Claude Code — and now your Grok Bot — held together by one shared memory vault, instead of five tools floating alone.
Readers bookmark this page and still hand-sort their inbox on Monday. Operators install one build this week and never touch that job again.
Get the Agent OS → Inside the AI Profit Boardroom · aiprofitboardroom.comFour live coaching calls every week where members bring their actual setups.
Plus a prompt library so your bots start smart instead of blank.
Your Claude, Hermes, OpenClaw and free Claude Code on one shared Obsidian vault.
A kanban board to dispatch work, plus video, SEO and avatar tools built in.
The zip file, the roadmap, a video tutorial, and daily updates.
Over three thousand business owners, some who'd never used AI at all.
