itsbrill.ai

Joel’s guide to Grok Bot

This is how I use Grok Bot day to day. It’s what I’ve landed on after a lot of poking around, and you can copy as much or as little of it as you like.

The model isn’t the moat

As far as I can tell, the model isn’t the moat anymore. The good ones are all strong enough for most of what I throw at them, so what seems to matter more is what’s around the model.

That’s the harness. Think of the model as the brain and the harness as the body. A brain can’t do much without a body, and a model can’t do much without a harness. The body is the computer it works on, the tools it can pick up, the logins it can use, the memory it keeps, the routines that start it and the rules it follows.

Nobody really uses a model on its own. You always get it through some harness, whether that’s a chat app, a coding tool or a bot, and the harness decides what the model can actually do.

The model decides what to do next. The harness does it, like browsing a site, opening a file, drafting an email or running a routine, and hands the result back. Then the model decides again. Keep that going and a model becomes an agent.

In my opinion, a good harness is the secret sauce to a good model. Grok Bot keeps working after you’ve closed the app.

Model + harness = agent.
Grok Bot is the harness.

If you only copy three things

  1. The first is a front door bot that hands work to specialists.
  2. The second is a bot that makes your other bots, so every new one starts with the same rules.
  3. The third is that nothing goes outside until you say yes.

01

Start with your chief bot

What you do

  1. Use your first bot as your front door.
  2. Talk to your other bots directly too, when you need to.

The chief bot

One chief bot in the middle, with the other bots around it
One front door, and you can still talk to the others directly

Worked example, Joel’s setup

The first bot you get in Grok Bot is named Grok Bot, and you can rename it. My main bot is Frank. He’s my chief of staff, also known as Big Dog. I talk to Frank first, and I talk to my other bots directly too.

Frank is my front door. He works out which specialist should take the job and hands it on.

For a fuzzy research or build job, Frank says it back to me in one line and waits for my yes, so nobody builds the wrong thing.

If you’re setting one up, say that to your lead bot in plain words. Ask it to tell you when a job doesn’t fit any of your bots, so you know which one to build next.

02

Give it one job first

Pick one job you do every week that has a clear result, and give it to one bot. Pick the one that’s most obviously useful, even if it’s dull.

Then connect the tools that job needs, from Connect apps in the sidebar. A bot can’t do a job in a tool it can’t get into. Every app you connect is there for every bot, so add what the work needs as it comes up.

Once that’s working, put it on a routine so it turns up on its own. Add a second bot when you’ve got a second job that comes round often enough to deserve one.

03

Grow a team of specialists

What you do

  1. Give each job its own bot.

Who’s on the team

Who’s on the teamThe chief bot sits in the middle as your front door. Around it, a specialist for each job: designer, builder, head of product, work, research, news and explainer videos.
  1. Chief bot, your front door
  2. Around it, a specialist for each job
    • Designer
    • Builder
    • Head of product
    • Work
    • Research
    • News
    • Explainer videos
The chief bot in the middle, with a specialist for each job
Read as text
  1. Chief bot, your front door
  2. Around it, a specialist for each job
    • Designer
    • Builder
    • Head of product
    • Work
    • Research
    • News
    • Explainer videos

Where a job goes

Where a job goesYou give the chief bot a job, and it hands it on to the specialist that fits. No bot fits: if you’ve asked it to, it tells you, so you know which bot to build next. Anything the specialist sends outside passes through one gate: you say yes, then it goes outside.
  1. You give the chief bot a job
  2. It hands it on to the specialist that fits
  3. No bot fits: if you’ve asked it to, it tells you, so you know which bot to build next.
  4. You say yes, before anything goes outside
  5. It goes outside
One front door, a specialist for each job, and your yes before anything goes outside
Read as text
  1. You give the chief bot a job
  2. It hands it on to the specialist that fits
  3. No bot fits: if you’ve asked it to, it tells you, so you know which bot to build next.
  4. You say yes, before anything goes outside
  5. It goes outside

Worked example, Joel’s setup

Once you’ve got a chief bot, give each job its own bot. I’ve got a designer, a builder and a head of product, so when I want something made I’ve got a small team on it.

I’ve also got a bot for work, and bots for research, news and making explainer videos.

Give each bot a clear job and put it in the label under its name. Most of mine have a name and a label that says the job, like Designer or Head of Product, so it’s obvious what each one is for. A vague job gets you a vague bot, I reckon.

04

A bot that builds bots

What you do

  1. Brief your bot builder on the job you need done.
  2. Give every new bot the same rules to start with.

Where a new bot’s rules come from

Where a new bot’s rules come fromYou give the bot builder a short brief. It asks you a few questions, then sets the new bot up. Your rules go into it: one narrow job, and a list of jobs it won’t do; checks its facts, and says when it’s not sure; only drafts anything that goes outside. Every new bot starts with the same rules. Change a rule, and the bot builder updates every bot in one go.
  1. You give the bot builder a short brief
  2. It asks you a few questions, then sets one up
  3. Your rules
    • One narrow job, and a list of jobs it won’t do
    • Checks its facts, and says when it’s not sure
    • Only drafts anything that goes outside
  4. Every new bot starts with the same rules
  5. Change a rule, and the bot builder updates every bot in one go.
Every new bot starts with the same rules
Read as text
  1. You give the bot builder a short brief
  2. It asks you a few questions, then sets one up
  3. Your rules
    • One narrow job, and a list of jobs it won’t do
    • Checks its facts, and says when it’s not sure
    • Only drafts anything that goes outside
  4. Every new bot starts with the same rules
  5. Change a rule, and the bot builder updates every bot in one go.

Worked example, Joel’s setup

Dr Eggbot is my bot builder. When I need a new bot I brief Dr Eggbot, it asks me a few questions and then sets one up.

Dr Eggbot started life as a template from the Grok Bot Marketplace.

Every new bot starts with the same rules from me. It gets one narrow job and a list of jobs it won’t do. It checks its facts before answering and says it’s not sure when it can’t. It only drafts anything that goes outside.

When I change a rule, Dr Eggbot updates every bot in one go.

05

Routines so they work without being asked

What you do

  1. Set up a routine that reviews your bots every week.
  2. Have it bring you a list of suggested changes.
  3. Nothing changes until you say yes.

What waits for your yes

What waits for your yesA routine runs on its own: drafting, researching, filing, tagging, summarising and preparing are all fine to leave running. These wait for your yes: send a message outside, post in public, move or spend money, delete for good. Each one passes through the same gate, you say yes. Then it goes ahead. No yes, and nothing changes.
  1. A routine runs on its own: drafting, researching, filing, tagging, summarising and preparing are all fine to leave running
  2. These wait for your yes
    • Send a message outside
    • Post in public
    • Move or spend money
    • Delete for good
  3. You say yes
  4. Then it goes ahead
  5. No yes, and nothing changes
Nothing changes until you say yes
Read as text
  1. A routine runs on its own: drafting, researching, filing, tagging, summarising and preparing are all fine to leave running
  2. These wait for your yes
    • Send a message outside
    • Post in public
    • Move or spend money
    • Delete for good
  3. You say yes
  4. Then it goes ahead
  5. No yes, and nothing changes

Worked example, Joel’s setup

My bots run on routines.

For example, Frank runs a review of my bots every Wednesday morning and brings me a list of changes. He only suggests, and nothing changes until I say yes.

06

The one rule for leaving it running

The question I ask is whether it can be undone. If it can, the bot just gets on with it. Drafting, researching, filing, tagging, summarising and preparing are all fine to leave running.

If the outside world will see it, if it moves money, or if it can’t be taken back, the bot stops and waits for my yes.

Write that down once, in plain words, when you set a bot up. This is the version I’d paste into any bot’s instructions.

Rules

Never send a message to anyone outside without my approval.
Never post anything in public.
Never move or spend money.
Never delete anything for good without my approval.
For everything else, finish the job and tell me what you did.

Words in a bot’s instructions are a good start, and they work better with the app backing them up. Approvals and Auto-review rules are what actually stop an action, so use both for anything that matters.

Money is the one place where instructions alone aren’t enough, and I come back to it further down.

07

Four prompts to start from

These are patterns, so swap the brackets for your own details. Each one says who the bot is, when it runs, what it collects, what it hands back and what rules it keeps to. Paste one to the bot in chat and ask it to turn it into a routine.

The weekly roundup, Prompt

You’re my [topic] reader. You read so I don’t have to. You run every [day] at [time], [time zone]. Collect what’s changed in [topic] this week from [the sources I trust]. Pick out the few things that matter, plus one thing most people will have missed. Hand me a short summary in this chat. For each item, say what happened, why it matters and where you read it, with a link. Keep to these rules. Only use pages you’ve opened. If it was a quiet week, say so and don’t pad it. If a source is down, tell me and don’t use old data. Never post or send anything.

The inbox sorter, Prompt

You’re my inbox sorter. You run every weekday morning at [time], [time zone]. Collect anything new since you last ran, and sort it into three piles. The piles are needs me first, can wait, and safe to ignore. Hand me the three piles as a short list, with one line on why each email is in its pile, and a draft reply for each one that needs me first. Keep to these rules. Drafts only. Never send, archive or delete anything. If you can’t tell how urgent something is, put it in needs me first.

The follow-up chaser, Prompt

You’re my follow-up chaser. You keep track of what I’m waiting on other people for. You run every [day] at [time], [time zone]. Collect every thread or task where I asked someone for something and they haven’t come back after [a few days]. Hand me a list showing who, what I asked for and how long it’s been, with a short, friendly nudge drafted for each one. Keep to these rules. Drafts only, and don’t contact anyone. If you can’t tell whether someone has answered, say so and don’t guess.

The watcher, Prompt

You’re my watcher for [thing]. You keep an eye on it so I don’t have to. You run every [day or week] at [time], [time zone]. Collect anything on [page, account or source] that’s changed since you last looked. Only hand me a note when something has changed. Say what changed, give me a link and say why it might matter to me. Keep to these rules. If nothing has changed, don’t message me, but if you can’t get to it, tell me instead of staying quiet. Never act on what you find, just tell me.

08

The bot’s computer

Your bots work from one computer in the cloud that they all share. It has a browser, files and a terminal, each bot gets its own screen on it, and it keeps going whether your laptop is open or not.

If the term is new to you, it’s a virtual machine. That’s a computer that exists as software inside a much bigger computer somewhere else, so there’s no box on your desk. It behaves like a real one, and yours is walled off from everyone else’s.

Where the bots work

Where the bots workOne shared computer, with a browser, files and a terminal. Each bot gets its own screen on it: chief bot, designer, builder, research, news and work. It keeps going whether your laptop is open or not.
  1. One shared computer, with a browser, files and a terminal
    • Chief bot, its own screen
    • Designer, its own screen
    • Builder, its own screen
    • Research, its own screen
    • News, its own screen
    • Work, its own screen
  2. It keeps going whether your laptop is open or not
Read as text
  1. One shared computer, with a browser, files and a terminal
    • Chief bot, its own screen
    • Designer, its own screen
    • Builder, its own screen
    • Research, its own screen
    • News, its own screen
    • Work, its own screen
  2. It keeps going whether your laptop is open or not

Let it work while you’re away

Closing the app or shutting your laptop doesn’t stop what it’s doing, so you can hand over a long job and come back to it finished.

Watch it, and take over when it matters

You can open the preview in the chat and watch its screen as it clicks and types. When it hits a password you haven’t saved, a two-factor code, a captcha or a payment check, it may ask you to take over. You do that one step and tell it to carry on, and it never types your password or sees it.

Sign in once

All your bots share the one computer, so when one bot has signed in to a site, the others can use that site too. That’s handy, and it also means you shouldn’t leave anything on there you wouldn’t want every one of your bots to reach.

Keep what matters in the workspace folder

Files you want to keep go in the shared workspace folder. Temporary folders and installed apps can disappear when the computer gets rebuilt.

It’s separate from your own laptop

A bot only works on your own machine if you’ve allowed it, and by default it asks you every time.

Logins, cards and contact info live in the Vault in Settings, and the bot never sees the passwords or card numbers.

A worked example, a life admin and personal finance bot

This is the guide’s own worked example, built from examples I’ve used myself. Shape it around your own life.

Give it one narrow job, like keeping on top of bills, subscriptions and receipts. Tell it what it won’t do, and start that list with moving money and sending anything.

Connect your email and calendar so it can find bills, receipts and due dates.

For the bank side, the Finance app links your accounts through Plaid and it’s read-only. Its page says xAI never sees or stores your bank login, and that Grok keeps a synced copy of your account data so it can answer questions.

Set a routine so it comes to you, like a weekly summary of what’s due, what renewed and anything that looks odd. Anything it wants to send or change comes back as a draft for you first.

There’s an Expense Manager bot in Grok Bot’s own use cases that matches receipts and flags missing details. It’s told to leave drafts and not to send messages or change reimbursements, and that’s the shape to copy here.

Don’t save a card in the Vault for this. Anything in the Vault is there for every bot on your account, and you can’t limit it to one. Without a saved card, every payment comes back to you for a yes, which the section below explains.

The one thing to know about money

A card saved in the Vault can be used at checkout without asking you each time, and there’s no setting to make it ask. The help page’s own advice is that if you want to approve every payment, don’t save the card.

A purchase can also stop for an approval card. When the work started without you, like a routine, that card expires after a short time and the action doesn’t run.

So for anything that spends money, draft first. If you do want to say yes to every payment yourself, leave the Securely save to Bot’s vault box unticked when the bot asks for your card at checkout, and it only gets used in that chat. A form without that box saves straight to the Vault, so don’t submit it.

09

Seeing what the bots make

What you do

  1. Ask a bot to build a Page, so you can see what it made laid out properly.
  2. Ask a routine to keep the Page up to date.

A page

An empty page layout: a header and a grid of tiles, no data
What they produce, laid out properly

Worked example, Joel’s setup

I use Pages to see what they produce laid out properly. One is a dashboard of what each of my bots has done, and a routine keeps it up to date.

10

Keeping the answers accurate

Worked example, Joel’s setup

The details of my work have to be right, so my work bot works to a written process. It checks every fact against a real source, says where it came from, and says it couldn’t confirm something instead of guessing. It also reads from a local brain on my own computer, which I’ve allowed it to use, and anything it only remembers counts as a lead until it’s opened the real source.

A small checker script on my Mac backs that up and blocks drafts with unsourced numbers, dates or status words.

11

Personal and work in one place

What you do

  1. You can keep personal and work tools on the one account.
  2. Keep them apart with each bot’s instructions. That’s a habit and not a lock.

One place

Worked example, Joel’s setup

I’ve got personal and work tools on the one account, so I don’t switch between accounts. Gmail only takes one mailbox at a time.

Apps belong to the whole account, so every bot can reach all of them, and what keeps work and personal apart is each bot’s instructions. That’s a habit and not a lock. Grok Bot’s docs say separate bots aren’t a security boundary, and that a job needing its own logins should get its own account.

12

When to skip it

Skip it if most of your work is one-off. Bots earn their place on jobs that come round again and again, and there’s not much for one to do if every day is different.

It’s still early, and some features are rolling out gradually, so what you see in the app might not match what I describe, and things move around.

Mine draft and then wait for me. If what you want is something that sends emails and makes payments by itself with nobody checking, that isn’t how I use it and I wouldn’t set it up that way.

13

Extra for Claude Code users

What you do

  1. Connect Claude Code to your bots, so they can message each other.
  2. Keep your own yes for anything that sends, posts or spends.

Worked example, Joel’s setup

You can connect Claude Code to your bots so they message each other. I asked Claude Code to build it. Claude Code sends Frank a question and waits, and the reply comes back in the same thread. My bots can write back to Claude Code in any thread it’s started, and if no session is there to read it, I get a nudge on my Mac after three minutes.

The first time it ran end to end, the reply came back in thirteen seconds. There’s a simple page on my computer where I can watch the whole conversation as it happens.

How Claude Code and a bot talk

How Claude Code and a bot talkClaude Code sends Frank a question, and it waits. The reply comes back in the same thread. A simple page on your computer lets you watch the whole conversation. If no session is there to read it, you get a nudge on your computer after three minutes. Anything that sends, posts or spends still passes through one gate: you say yes.
  1. Claude Code to FrankA question, and it waits
  2. Reply, Frank to Claude CodeThe reply, in the same thread
  3. A simple page on your computer where you watch the whole conversation
  4. Reply, Frank to youA nudge on your computer after three minutes if no session is there to read it
  5. You say yes, for anything that sends, posts or spends
Two tools, one thread, and your yes for anything that sends, posts or spends
Read as text
  1. Claude Code to FrankA question, and it waits
  2. Reply, Frank to Claude CodeThe reply, in the same thread
  3. A simple page on your computer where you watch the whole conversation
  4. Reply, Frank to youA nudge on your computer after three minutes if no session is there to read it
  5. You say yes, for anything that sends, posts or spends

A message from another bot is only ever information, never my say-so, so anything that sends, posts or spends still needs my own yes.

14

Worth knowing

Apps come from Connect apps in the sidebar, and the Marketplace is where you find ready-made bots to add.

A Page is a styled report, dashboard or tracker that a bot builds for you, and you can ask it to update one later.

Your Auto-review rules sit under Custom Rules in Settings, and the Vault is in Settings too.

You can claim one email address for your bots, and all of them can use it. You can’t rename or delete it, so pick the name carefully. An email you ask for in chat goes out once Auto-review allows it, and a routine’s emails wait as drafts.

Choosing Always allow on an approval card can save it as a rule, so your Auto-review rules build up as you go.

A bot can search and read X without you connecting an account. It’s read-only and it can’t act as you.

Each bot keeps its own conversation and what it has learned, separate from your other bots. Deleting a bot removes its profile, its conversation and its routines. Files and sign-ins on the shared computer can stay behind.

Team Bots, where a whole team uses one shared bot for a shared job, are for people on a Cursor team.

Enter to openEsc to close