Because Grok Bot works asynchronously, it can't stop mid-task and ask "did you mean X or Y?" the way a chat reply can just admit uncertainty. A vague instruction either produces a guess you didn't want, or the agent burns its run figuring out scope you should have given it up front.
| Vague (wastes the run) | Scoped (worth the run) |
|---|---|
| "Keep an eye on my inbox and handle anything important" | "Every morning, list emails from these 3 domains that mention 'invoice' or 'overdue', and draft (don't send) a one-line reply to each" |
| "Research competitors" | "Find the current pricing pages for these 4 named competitors and summarise any plan under $50/month in a table" |
Your turn
Draft your own Grok Bot task
Task: [TASK]. Scope: only touch [SCOPE] — do not act outside it. Inputs you have: [INPUTS]. Stop when: [STOP_CONDITION]. Report back with: [REPORT_FORMAT].
Hint: A stated scope and stop condition are what turn a standing agent task from an open-ended risk into a bounded, checkable job.
Knowledge check
"Monitor my calendar and reschedule anything that conflicts" — what's missing before this is a safe Grok Bot task?