What is Grok Bot?

Sources

How you work with Grok bots

You message a Bot like a teammate: task, context, and the tools it needs. Official docs say it takes on multi-step work across apps and websites, updates you in the conversation, and returns when something needs your approval.

What official docs say makes it different

• Each Bot has a computer — persistent cloud machine; work can continue while your laptop is closed.
• Setup is a message — create a Bot, describe the job, grant access as asked (desktop and mobile).
• Bots can coordinate — parallel work, group chats, handoffs.
• Skills from demonstration — walk a path once; save as a skill; rerun on a schedule. A later skills guide is deferred in this pack.
• Context compounds — named Bot keeps memory, files, sessions, and preferences across sessions.

Platforms and access (known)

Per official get-started / overview (2026-09-18 CT):

• Desktop: macOS (Apple silicon & Intel), Windows (x64 & Arm64), Linux (x64 & Arm64)
• Mobile: iPhone, iPad, Android
• Computers: run in Cursor’s cloud
• Access: included with every paid individual Cursor plan and Cursor Teams; or link an individual SuperGrok / SuperGrok Plus / SuperGrok Heavy subscription. Usage resets weekly — see official Plans and billing for the matrix.

Unknown / verify live: exact weekly usage numbers and current plan prices change; this handbook does not invent them. Check official Plans and billing.

Shared computer — important boundary

All of your Bots share one cloud computer (files, browser sessions, app logins). The computer belongs to your account, not to one Bot. Between users, isolation is strict. Do not treat separate Bots as separate security boundaries.

For approvals, Auto Review, and privacy controls, see Grok Bot approvals, security, and privacy.

A good first handoff

Official guidance: pick a real task with a clear finish line — research + draft, stop before send. Example pattern from docs: pull a list from a CRM, research top accounts, draft outreach, leave drafts to approve.

Then: review → correct → save as skill or routine when stable.

Roles that fit coding agents and ops

Official use-cases page frames roles around a repeatable outcome (sales outbound, talent scout, paid media, expense manager, product performance, bug reproduction, account health, chief of staff). Start read-and-prepare; keep consequential actions behind approval.

Creating Grok bots (official)

Per docs.x.ai/grok-bot/bots: a Bot is a durable teammate with name, job, own conversation, and developing context. Create separate Bots for distinct goals, tools, style, approval boundaries, or schedules. Docs example jobs (illustrative, not Botski Hall listings): Talent Scout, Expense Manager, Bug Reproduction. Description = standing rules; messages = task-specific. Pin/hide (hide does not pause routines). Duplicate copies profile/settings/skills/routines/avatar — not history, learned memory, or attachments.

Clash: Official example job names are documentation examples. They are not Hall inventory. https://bot.ski/bots stays empty (needs Clerk). Marketing chips on https://x.ai/bot are illustrative only.

Clash flag — Botski vs product

Do not read this page as “Botski is Grok Bot.” Botski is a third-party handbook and workshop stance — see How Botski fits as a third-party workshop.