Grok Bot 101
AI teammates you can give real work to.
Bots can sign in to your tools, use them just like you do, and come back with finished work.
This page covers the Grok Bot 101 deck — Agrim Singh (@agrimsingh), SpaceXAI, September 2026 — as a guide you can keep open while you build. Official product docs live at docs.x.ai.
This is the whole app
The sidebar is the roster. A room like Monday is a group chat where you give the week to more than one Bot at once: Inbox Manager sorts, Expense Manager closes receipts, Chief of Staff names the two decisions that are actually yours. Nothing goes out without you.
It looks like a team that already ran. Chief of Staff stayed quiet if nothing changed. Inbox Manager left four reply drafts and sent none of them. When a send comes up, the Bot stops: not yet, or send. Click a name. Type if you want — it still waits.
Chief
Yesterday 10:51 PM
Slack's quiet. two things from today:
- Deck → numbers checked against finance's sheet
- Offsite → 3 venues shortlisted. the one on Folsom has a hold until Friday.
take the venue, i'll do the deck
Yesterday 11:51 PM
booked the venue. calendar invite is in your drafts — not sent.
book it
👍booked the venue and sent the confirmation around.
What you will have by the end
Two things. Not a fleet, not a workflow builder.
1
A Bot doing a job you already do
One Bot, one job, and a description you wrote yourself.
2
A rule about when it has to ask
If it is about to send, publish, buy, delete, or sign, it stops. Everything up to that point it does on its own.
Pick one job
Start with a job someone in the room already owns. The three that teach the pattern:
Inbox Manager
Sorts the inbox, flags what is urgent or where someone is waiting, and drafts replies.
Where it asks you
It sends nothing until you approve it.
Expense Manager
Logs receipts that arrive by email, builds the weekly summary, and chases missing categories.
Where it asks you
It pays or reimburses nothing without you.
Sales Outbound
Researches accounts overnight, picks the contacts worth reaching, drafts emails in your voice, and leaves you a list.
Where it asks you
It sends nothing until you approve each one.
Five words you will see in the app
That is the whole vocabulary. Models, context windows, and sandboxes never come up.
1. Bot
A teammate with a name, its own memory, its own computer, and its own tools.
Example:
Chief of Staff2. Chat
Where you talk to one Bot, or to a group of them.
Example:
Message Chief of Staff3. Prompt
An instruction. Use it once, save it as a skill, or schedule it as a routine.
Example:
Every weekday at 8:004. Tool
How a Bot reaches software: a plugin, the browser, the shell, or its computer.
Example:
Gmail · Slack · Chrome5. Artifact
What the Bot leaves behind: a document, a draft, a sheet, a change to code.
Example:
weekly-summary.md
Create a Chief of Staff and one specialist
You only talk to one Bot. Chief of Staff routes work and reports back. The specialist is the job the room picked — Inbox, Expense, or Sales Outbound. The description field is enough to create it. Plugins and the approval rule come next.
Chief of Staff description
You are my Chief of Staff. Watch my calendar, Slack, and inbox. Stay quiet if nothing changed. When something needs me, say what is done, what is blocked, and the one decision only I can make. Never, without asking: send, publish, buy, delete, or sign.
Plugins are how a Bot gets into your apps
Plugins
25 installed · 7 private
Featured
Gmail
Search, read, draft, and manage email.
Google Calendar
Search events and schedule meetings.
Google Drive
Search, read, create, and share files.
Granola
Read and search your meeting notes.
Slack
Read channels, search history, post as you.
X
Read X, draft posts and replies.
A plugin is a connection to one app.
Gmail, Slack, your calendar, your CRM.
Add it once for the account.
Then tell each Bot which ones to use. Every Bot can still reach all of them.
Your own tools go here too.
Anything your team builds, or an MCP server, sits next to the public ones.
Open Settings → Plugins in the app. Type @ in chat to attach a connector, and / for a saved skill. This directory lists bots by the tools they work with. Browse integrations or pick the tools you already use.
Set what it has to ask before doing
New email
Ready to send
- From
- you@yourcompany.com
- To
- sarah@acme.com
- Subject
- Moving Friday's review to 2 PM
Hi Sarah, could we move Friday's design review from 11 AM to 2 PM? A client call came up and I do not want to rush our discussion. Thanks.
The Bot stopped here and is waiting for you.
Set once, in Settings. Require approval for the actions that leave the building — send, publish, buy, delete, or sign. Always allow the ones that only read or draft. When two rules collide, require approval wins.
You are not done setting up until you have watched the Bot stop and ask you once. Draft an email, let it reach Send, and confirm the conversation shows it waiting. Official detail: Approvals, security, and privacy.
When a login comes up, you type the password, not the Bot
accounts.google.com
Enter the code from your phone
You take over its screen, type the password or the code, and hand it back. Nothing you typed ends up in the chat.
Write the first task in five parts
Write all five before you press enter. The Bot does exactly the job you described, so say where it should stop as carefully as what it should do.
Outcome
My inbox is sorted into Needs me today, Waiting on others, Newsletters, and Everything else. Threads where I am blocking someone are at the top.
Sources
Gmail, and the Slack channels #ops and #leadership for context on who is waiting.
Constraints
Do not send, archive, or delete anything. Do not reply to anyone outside the company.
Deliverable
A short list in this chat — each urgent thread, one line on why, and a draft reply saved in my Drafts folder.
Review point
Stop after the drafts are saved. I will read them and send the ones I agree with.
Outcome
Last week's receipts are logged, categorized, and ready for me to approve.
Sources
The finance inbox, the expense tool, and last week's summary file.
Constraints
Do not pay or reimburse anyone. Do not message a vendor.
Deliverable
A sorted list of receipts, totals that reconcile to the source, and one draft chase per missing category.
Review point
Stop after the list and drafts. I decide what gets paid.
Outcome
A review list of accounts worth reaching, with contacts and draft outreach in my voice.
Sources
The CRM view I named, company websites, and the style examples in this chat.
Constraints
Do not send or enroll anyone. Skip anyone already in a sequence.
Deliverable
Ranked accounts, up to three contacts each, and a draft email saved — not sent.
Review point
Stop at the review list. I send the ones I agree with.
The first result is something you can check, not something already done. Inbox or Sales hands you a list of drafts — nothing sent. Expense hands you a sorted list of receipts — nothing paid.
Every Bot gets a computer that stays on

$ run weekly-summary reading 14 receipts ✓ summary saved
Browser
stays signed in to your tools
Files
stay where the Bot left them
Tools
are installed once and kept
Routines
run on schedule, laptop open or not
Most AI agents run on your laptop, so they stop when you close it. A Bot runs on its own computer. Close the laptop and it keeps going.
Most tools assume you have one email and one Slack. A Bot's computer can be signed into all of yours at once — four addresses, seven workspaces — and one Bot reads them in one place. See Use the computer and apps.
Each Bot has its own memory. They all share one computer.
Chief of Staff
Own memory and routines
your calendar habits, who matters this week
Inbox Manager
Own memory and routines
which senders are urgent, your reply tone
Expense Manager
Own memory and routines
your categories, who owes a receipt
One computer. One set of logins.
Browser sign-ins, installed tools, plugins and saved Skills are shared by every Bot on the account.
Shared logins make handoffs between Bots easy. They also mean a second Bot adds no safety. Telling a Bot which plugins to use is an instruction, not a lock.
If you want the Bot to remember something, put it in a file.
Chat · Last Tuesday
Sarah moved to the Berlin office, so treat her mail as European hours.
Noted.
Also, receipts over 200 need a project code now.
Understood.
Twelve conversations later, this is far up the scroll.
expense-rules.md
the Bot rereads this before every run
# Rules that change - Sarah is in Berlin. European hours. - Receipts over 200 need a project code. - Q3 travel goes to cost centre 41. # Ask before - Any reimbursement - Any message to a vendor
Rules that last go in the Bot's description. Facts that change go in a file, and the description tells the Bot to reread it.
Start with two Bots. Not five.
- 1
Chief of Staff
quiet and useful - 2
Inbox Manager
drafts waiting - 3
Expense Manager
fine, if you have that job - 4
Research
wrote the same summary as Chief of Staff - 5
Thumbnails
edited a file another Bot was working on
Before you leave tonight
1. Create Chief of Staff
Write the description in your own words. Keep the line about asking first.
2. Create one specialist
Inbox Manager, Expense Manager, or Sales Outbound. Add the plugins it needs.
3. Run one task with all five parts
Then ask it to send one draft, and watch it stop.
If the Bot did not stop at step three, fix Settings before you give it a second job.
How it compares to ChatGPT, OpenClaw, and Hermes
Written in September 2026. These products change often. Check the current docs before you quote this.
ChatGPT Projects
A chat with files attached. It does not have a computer that stays on after you leave, and it does not sign into the rest of your tools as a coworker would.
OpenClaw
Software you run on your own machine. You pick the machine, connect each tool yourself, and keep it running. The most control and the most maintenance.
Hermes
Plain files on your own machine. Who the agent is lives in a soul file, what it knows in a memory file. You see everything because you are the one running it.
Grok Bot
A coworker on a computer xAI runs. You only touch files when you want the Bot to remember something. Rooms and handoffs between Bots are built in.
How far can you push Grok Bot?
It can open websites and click around.
linkedin.com/in/someone
Jordan Lee
VP, Operations
MessageMessage draft
Saw your team is hiring across operations...
Saved in LinkedIn · not sent
Book something
Fill the form, stop before payment
Work through an old portal
Click the buttons an API never exposed
Leave the work there
A draft in LinkedIn beats instructions in chat
You can give it more tools.
wacli
Read and draft WhatsApp messages
Peekaboo
See and use apps on my Mac
AgentCookie
Bring a browser session across
If a tool works from a computer, the Bot can usually learn to use it.
WhatsApp wasn't built in. I added it.
Grok Bot talk
Send the field guide to the event group when it is live.
The field guide is live. Here is the link.
Draft only
Grok Bot stopped here
Send this message?
You can change the copy, choose the chat, or leave it as a draft.
Sometimes a website blocks it.
shopee.sg
Access denied
This browser doesn't look familiar.
Try againThe cloud browser is signed in, but the site still won't let it through.
BlockedSo I let it use my Mac.

shopee.sg
Found it in your Chrome
Your usual session is working
- 1
Peekaboo sees the screen
- 2
The Bot uses the real app
- 3
I tell it to stop before buying
Same Chrome. Same login. I still tell it to ask before buying. Peekaboo does not block the click.
Once you have a few Bots, put them in a room
Launch room
Three Bots in this chat
Research the company, update the page, then draft the announcement. Ask me before anything goes out.
Research
I checked the claims and marked two that need softer wording.
Builder
I have the checked brief. Cursor is building the update now.
Launch
I will bring the preview and the draft back here for you.
It can send coding work to Cursor.
Update the page from the checked brief. Return the PR when it is ready.
Sent to a Cursor Cloud Agent. I will bring the PR back here.
Update the Grok Bot field guide
Donecursor/grok-bot-field-guide-9d83 PR #20
merge it for me
Merged. PR 20 is on main as ec62a11.
The terminal output stays in Cursor. Only the result comes back to the chat.
Give it something you already hate doing
Open x.ai/bot, create the two Bots, run one five-part task, and watch it stop. Then pick a template from this directory so you are not starting from a blank description.
When a setup works, share the template so someone else can import it. Showcase is for the 𝕏 posts. The original slides stay up if you want the deck form.