Learn

What is Grok Bot?

Grok Bot is an official product: named AI agents (“Bots”) you keep around, with jobs and context that build up over time. Each Bot works on a persistent cloud computer — browser, files, and terminal — so work can finish in real tools, not only as chat drafts.

This Botski page summarizes that official picture for newcomers. It is an independent guide, not a replacement for docs.x.ai/grok-bot.

How you work with a Bot

You message a Bot like a teammate: the task, the context, and the tools it may use. It can take multi-step work across apps and websites, update you in the conversation, and pause when something needs your approval.

What stands out in official docs

  • Each Bot has a computer — a cloud machine that can keep working even if 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 through a flow once, save it, reuse it later (including on a schedule)
  • Context compounds — a named Bot keeps memory, files, sessions, and preferences across sessions

Platforms and access

From official get-started / overview material (as of 2026-09-18 CT):

  • Desktop: macOS, Windows, Linux
  • Mobile: iPhone, iPad, Android
  • Computers: run in Cursor’s cloud
  • Access: included with paid individual Cursor plans and Cursor Teams; or link a SuperGrok / SuperGrok Plus / SuperGrok Heavy subscription. Usage resets weekly.

Exact weekly limits and prices change — check official Plans and billing rather than trusting a number on this page.

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 a single Bot. Between different users, isolation is strict. Don’t treat “two Bots” as two separate security vaults.

For approvals and privacy controls, see Approvals, security & privacy. If a Bot stays silent after you message it, see When your Grok Bot gets stuck.

A good first task

Pick something real with a clear finish line — research and draft, then stop before send. Official examples look like: pull a list, research the top items, draft messages, leave drafts for you to approve.

Then review, correct, and only later save a skill or routine when the pattern is stable.

Creating Bots

A Bot is a durable teammate with a name, a job, its own conversation, and developing context. Create separate Bots when goals, tools, tone, approval boundaries, or schedules differ.

  • Description = standing rules
  • Messages = this task

Pin or hide Bots as you like — hide does not pause routines. Duplicating a Bot copies profile, settings, skills, routines, and avatar — not chat history, learned memory, or attachments.

Job names in official docs (like “Talent Scout” or “Expense Manager”) are examples, not a public catalog of bots on bot.ski. Marketing role chips on x.ai/bot are illustrative too.

Botski vs the product

TopicOfficial Grok BotBotski
Where the product livesCursor / xAI apps and docsIndependent project
HandbookOfficial docs & guidesThird-party Learn pages
EndorsementNot endorsed by X, xAI, or Grok

Read next: What Botski is · Chat vs Grok Bots · Connectors & plugins · When your Grok Bot gets stuck.

Sources

Fetched 2026-09-18 CT.

SourceURLFetchedNote
Grok Bot docs hubhttps://docs.x.ai/grok-bot/2026-09-18 CT
Get startedhttps://docs.x.ai/grok-bot/get-started2026-09-18 CT
Use caseshttps://docs.x.ai/grok-bot/use-cases2026-09-18 CT
Create and manage Botshttps://docs.x.ai/grok-bot/bots2026-09-18 CT
Grok Bot Guideshttps://x.ai/bot/guides2026-09-18 CT
Grok Bot producthttps://x.ai/bot2026-09-18 CTRole chips are illustrative

Cookie preferences