01
What is Grok Bot?
Grok Bot is xAI’s app for AI teammates. It opened in beta on August 11, 2026. Each bot has a name, a job, and memory, and works on a cloud computer with a browser, files, and a terminal.
Unlike a normal chatbot, it can:
- Sign in to the tools you already use
- Work across apps and websites
- Use the screen like a person when no connector exists
- Keep working when your laptop is closed
- Learn workflows you show it
- Coordinate with other bots
- Ask for your approval before consequential actions
Grok chats with you. Grok Bot works for you.
02
Who can use it
- SuperGrok plans
- SuperGrok, SuperGrok Plus, and SuperGrok Heavy subscribers
- Cursor plans
- Cursor Pro, Pro+, and Ultra, plus Cursor Teams
- Enterprise
- Available through a waitlist and team plans
Grok Bot has its own usage allowance, separate from normal Grok or Cursor use, and it resets weekly.
03
Where it runs
- Desktop
- macOS, Windows, and Linux
- Mobile
- iPhone, iPad, and Android
- Cloud
- Your bots’ computer runs in the cloud, so tasks continue when your device is off
04
Create your first bot
Give it a name and a focused job description.
Example
- Name: Researcher
- Job: Competitive research
- Description: Research AI products using public sources. Keep a direct source link for every important claim.
One clear job per bot beats one bot that does everything.
05
Give it a real task
A good task spans tools and has a clear finish line:
- What to find or do
- Which tools to use
- What to skip
- What the output looks like
- Where to put it
- When to ask you
Pull this week’s pipeline review list from our CRM. Skip anyone already in an active sequence. Research the top five accounts and draft a personalized email for each. Do not send. Put the drafts in one doc for my review.
06
Grant access only when needed
- Connect a tool when a task requires it
- Use connectors where they exist
- Let the bot use the screen only for tools without connectors
- Type passwords and two-factor codes yourself, never in chat
- Sign out of services you no longer need
All bots on your account share one cloud computer, its files, and its browser sessions. Separate bots are not separate security boundaries.
07
Approve before anything leaves
Grok Bot sends drafts and voice memos for approval and asks before consequential decisions. Always review:
- Emails and messages
- Posts and publishing
- Deletions
- Purchases
- Changes to production systems
- Anything shared outside your team
Never approve an action whose target or effect you cannot identify.
08
Set Auto-review rules
Auto-review is a separate layer that checks risky actions, such as shell commands, plugin calls, and computer use. Add personal rules in Settings → General → Auto-review.
- Ask first
- For anything that sends, spends, deletes, or publishes
- Allow automatically
- Only for narrow, known, low-risk actions
Keep rules narrow and tied to a known action. Broad rules remove the protection.
09
Teach skills by showing
Perform a browser workflow once while the bot watches. It can save the repeatable path as a skill.
Good first skills:
- Processing invoices from email
- Updating a CRM after calls
- Filing bug reports from a template
- Preparing a weekly report
- Onboarding a new hire checklist
10
Run routines on a schedule
Turn a skill into a routine that runs on a schedule:
- Every morning: summarize new leads
- Every Monday: prepare the pipeline review
- Every Friday: draft the weekly update
- Every month: reconcile invoices
Check the first few runs closely before you trust a routine.
11
Build a small bot team
Several bots can work in a group chat, share context, and hand work to each other.
- Researcher
- Finds and verifies information
- Writer
- Drafts emails, docs, and posts
- Operator
- Updates tools and records
- Coder
- Reproduces bugs and prepares fixes
Add a bot only when a real job needs one. More bots use your weekly allowance faster.
12
Use cases that work well
- Outbound sales research and email drafts
- CRM and pipeline updates
- Demo environment preparation
- Bug reproduction and ticket filing
- Email and invoice processing
- New hire onboarding
13
Keep your data safe
- Bots act as you and can only reach what you can reach
- Give each task the least access it needs
- Keep sensitive files out of the shared workspace
- Pause or delete routines you no longer use
- Uninstall plugins you do not need
- Remove old files from the bot computer
14
Prompts to try
- “Research these five companies and give me a one-page brief on each with sources.”
- “Read today’s invoices in my inbox and list them by due date. Do not pay anything.”
- “Reproduce this bug from the report and file a ticket with steps and screenshots.”
- “Draft this week’s team update from our project board.”
- “Watch me do this task once, then save it as a skill.”
- “Every Monday at 9:00, prepare the pipeline review and message me.”
- “Tell me what access you need before you start.”
- “Show me every action you plan to take before taking it.”
15
What bots handle and what you handle
- Bots handle
- Research, drafting, data entry, routine updates, reproducing issues, and preparing work.
- You handle
- Access, approvals, sensitive decisions, sending, spending, and quality checks.
The real opportunity
Do not ask: “What can Grok Bot do?” Ask: “Which repeatable task can one bot finish this week, with my approval at the end?”
- Bot
- Job
- Task
- Access
- Approve
- Skill
- Routine
Start with one bot and one routine. Build the team only when the first bot earns your trust.
