How we put Grok Bot to work
Grok Bot runs on its own computer. These 7 steps make it actually work. Steps 6 and 7 cover what still bites: lag and token burn.
Independent guide. Not affiliated with or endorsed by the Grok Bot team.
Setup is a message
01 Hand it one real job
DO
Create a Bot, name it, and hand it one task you already do every week. Grant access when it asks.
WHY Per the docs, setup is a message. In our experience, one real job teaches more than ten test prompts.
Sources
Connect apps · @
02 Connect your apps first
DO
Open Connect apps and add Gmail, Slack, Drive, Notion or Calendar. Type @ in chat to hand one to a task.
WHY The docs call connectors often more reliable than clicking through a website. For us this is the smoothest part.
/workspace
03 Let it use its own computer
DO
Every Bot works on a persistent cloud computer with a browser and a terminal. All your Bots share it, logins and files included.
WHY Work keeps going with your laptop closed. In our runs it clicks through real sites and saves real files.
Settings › Computer
04 Add your own machines, carefully
DO
Set each machine to “Never allow” in Settings › Computer › Computers. If a Bot needs local files, use “Ask every time” and pick “Allow once”.
WHY The docs say “Never allow” unless a Bot has a specific reason. Picking “Always allow” at the prompt applies to every Bot until you change it.
50 routines · 5 min apart
05 Turn wins into routines
DO
“Run this every Monday at 8:00 and leave me a draft.” Where available, use Teach a task and do it once while it watches.
WHY Routines run on schedule with your laptop closed. Test on a safe example before you schedule anything.
Recover computer
06 Plan for the lag
DO
In our runs, long jobs sometimes slow down or stall. Ask it to save progress to /workspace and report at each checkpoint.
WHY Our first con: latency and instability at times. If the computer drops, the app offers Recover computer.
Sources
- Grok Bot docs, Computer and apps (Recover computer)
- The lag itself: MindLink’s own experience, no external source
On-demand monthly limit
07 Watch the token burn
DO
Pause routines you don’t need, widen schedules, narrow triggers, and set a monthly cap on extra usage.
WHY Our other con: loops and graph renders eat usage fast. The help center warns an hourly routine can use a week of usage in a day.
SAVE THIS. GIVE IT ONE REAL JOB.
Pick a task you did twice this week. Hand it over on Monday.
Talk to us