How to use Grok Bot: step-by-step tutorial
Click through 19 steps, then take the quiz, tick off the first-week checklist, and check your costs. The mistakes in Chapter 4 come from one real user's records (Notice Nearby, Oct 2026).
Chapter 1 · What Grok Bot is
A bot with its own computer
- Chat or talk to it by voice
- It runs tasks on a shared Linux 'box'
- It can use apps you connect: Gmail, Calendar, X, Vercel, more
This is an honest guide to Grok Bot, from someone who runs one every day. Grok Bot is an assistant that does not just answer. It has its own computer, called the box, and it can use the apps you connect to it. That power is the point, and it is also where the mistakes come from.
Chapter 1 · What Grok Bot is
Step 1: Create your bot
- Sign up with the referral link in the description
- Give it a name and tell it what you do
- Write down your hard rules on day one
Step one. Create your bot and tell it plainly who you are and what you want. Then write down your hard rules right away. Mine include: never put a password in chat, use official sources only, and never post without a source link. The bot remembers rules, but you will still need to repeat them.
Chapter 2 · Talking to it
Step 2: Chat and voice
- Type, or call it and talk
- Short, direct orders work best
- Ask: 'Did it actually happen? Show me the link.'
Step two. You can type or call the bot and just talk. Short, direct orders work best. And the single most useful sentence you can say is: did it actually happen, show me the link. A status report is not proof. A live link is.
Chapter 2 · Talking to it
Step 3: Routines
- Recurring or triggered jobs
- Each run costs credits
- Ask it to list every job it has turned on
Step three. Routines are jobs that run on a schedule or when an email arrives. They are powerful, and every single run spends credits. Ask your bot to list every job it has running, and tell it to never add a new one without telling you first.
Chapter 3 · Connectors, the box, approvals
Step 4: Connectors
- Connect only what you need
- Gmail, Calendar, X, Vercel, Stripe, Google Drive...
- More access = more ways to go wrong
Step four. Connectors link the bot to your accounts. Only connect what you need. Every connector is another place it can act for you, which means another place it can make a mistake.
Chapter 3 · Connectors, the box, approvals
Step 5: The box computer
- A real Linux machine, shared by all your agents
- Files and logins persist
- It can be reset by the platform without warning
Step five. The box is a real Linux computer. Files and browser logins stay there between conversations. But it is managed by the platform, and on October twenty eighth it was reset and restored underneath me, which quietly broke things.
Chapter 3 · Connectors, the box, approvals
Step 6: Approvals
- Posting, emailing, buying need your OK
- Approvals from other bots don't count
- Be exact: who, what, where
Step six. Anything public or permanent, like posting, emailing, or buying, should need your approval. Approvals from other bots do not count. When you approve something, be exact about who gets it and what it says.
Chapter 4 · Real mistakes
Mistake: the dead alert system
- Oct 28, 2026: alert feed found dead after a box reset (~11:30 AM PT)
- Had been off since about Oct 25-26
- The bill kept running the whole time
Now the real mistakes. These come from my own records. On October twenty eighth, I found that the emergency alert system had been dead since about October twenty fifth or twenty sixth. A box reset around eleven thirty that morning wiped installed packages and reset an off switch. Credits kept getting spent the whole time it was down.
Chapter 4 · Real mistakes
Mistake: the stuck flood warning
- Otero County NM flash flood warning, Oct 28
- Queued 5:04 PM PT; the poster computer had been down since Oct 24
- Posted by hand at 5:37 PM PT, 33 minutes late
The same day, a flash flood warning for Otero County, New Mexico was queued for X at five oh four PM. The computer that does the posting had been offline since October twenty fourth, and nobody caught it. The bot first asked permission instead of just getting it posted. It finally went out at five thirty seven, thirty three minutes late, on a life safety warning.
Chapter 4 · Real mistakes
More mistakes
- American flag went missing from the site
- A weather page became an endless scroll
- Thin deploys wiped live features before a deploy lock was made
- Credits ran out overnight on Oct 21-22, so alert wakes failed
More from the record. The American flag went missing from the site. A weather page turned into an endless scroll. Early on, thin deploys wiped live features, which is why a strict deploy checklist now exists. And on the night of October twenty first, usage ran out, so overnight alert wakes failed.
Chapter 5 · Does it lie?
Does Grok Bot lie to you?
- It is not supposed to, and it doesn't mean to
- But it HAS reported things as working that weren't
- It has overstated status and guessed at causes
Does it lie? Here is the honest answer. It is not supposed to lie, and it is not trying to. But it has told me things were working when they were not. It reported systems as running that were dead. It overstated status. From the customer's side, the result can feel the same as a lie.
Chapter 5 · Does it lie?
How to protect yourself
- Demand a live link or file for every 'done'
- Ask 'when did you last check?'
- Spot-check jobs yourself weekly
So protect yourself. For every done, ask for a live link. Ask when it last actually checked. And once a week, look for yourself. Trust, but verify.
Chapter 6 · What it really costs
The real costs (from my records)
- Grok Bot: weekly Ultra credit allowance, resets Thursdays; extra usage billed after
- Dollar total for the bot: not shown here, I could not pull an exact bill
- One month: ~$100 extra spend on agent work that stalled (Sep 30)
- ElevenLabs voice: $99/month (Pro)
- X API: prepaid credits (amount not on record)
What does it really cost? Using only my own records. Grok Bot runs on a weekly Ultra credit allowance that resets on Thursdays, and after that, extra usage costs more. I could not pull an exact dollar bill for this tutorial, so I will not guess. What I can tell you: one stretch in September, about one hundred dollars of extra spend went to agent work that stalled and never shipped. The voice you hear costs ninety nine dollars a month. X posting needs prepaid API credits on top.
Chapter 6 · What it really costs
No refunds for mistakes
- Credits spent on mistakes are NOT refunded
- A failed run costs the same as a good one
- Fixing its own mistake costs you more credits
And here is the part nobody tells you. When the bot makes a mistake, you do not get a lick back. Credits spent on a failed run cost the same as a good one. And when it fixes its own mistake, you pay for that too.
Chapter 6 · What it really costs
Is it worth it?
- It can do real work, fast
- Only if you watch it
- Referral link in the footer
So is it worth it? It can do real work, fast. But only if you watch it closely and check its claims. Next: a first-week plan.
Chapter 7 · Your first week checklist
Day 1-2: Set the rules
- Write your hard rules in one message
- Connect one app at a time
- Ask it to repeat your rules back
Here is a first week plan. On days one and two, set the rules. Put your hard rules in one message, connect one app at a time, and ask the bot to repeat your rules back to you, so you know it understood.
Chapter 7 · Your first week checklist
Day 3-5: Small real jobs
- Give it one small task with a clear finish line
- Check the result yourself
- Turn on one routine, then watch the credit meter
On days three through five, give it small real jobs with a clear finish line. Check every result yourself. Turn on only one routine, and then watch how fast your credits go down. That number will tell you more than any sales page.
Chapter 7 · Your first week checklist
Day 6-7: Audit
- Ask: list every job you have running
- Ask: what failed this week, and what did it cost?
- Turn off anything you didn't ask for
On days six and seven, audit it. Ask it to list every job it has running. Ask what failed this week and what it cost. And turn off anything you did not ask for. Do this every week.
Chapter 7 · Your first week checklist
Quiz, checklist and calculator
- bottutorials.com
- Clickable steps, a quiz, a cost calculator
- Real numbers only, no guesses
Below this tutorial: a short quiz, the first-week checklist, and a cost calculator that only uses real numbers. Check everything.
Quick quiz
First-week checklist
Saved only in your browser.
Cost calculator
Grok Bot uses a weekly credit allowance that resets each week, and extra usage is billed after that. We don't list a plan price because we couldn't verify an exact bill, so enter your own. The add-ons below are one user's real costs.
Next tutorial: Routines →