How to use Grok Bot, step by step

Grok Bot gives you Bots: AI teammates with a name, a job and context that builds up over time. Each Bot works on a persistent cloud computer with a browser, files and a terminal, so the work lands in your real tools, and it keeps going when you close your laptop. You message a Bot like a colleague, and several Bots can work at once and hand work to each other.

All of your Bots share one cloud computer: the same files, browser sessions and logins. Handoffs are easy, but separate Bots are not separate security boundaries; anything you sign in to for one is available to the others.

Grok Bot is not the Grok chat app; a paywall or limit inside the Grok app isn't about Grok Bot. You sign in with a Cursor account, and Grok Bot picks the AI model for each task itself. It launched in beta on 11 August 2026 and is now part of The X Subscription.

There's no separate Grok Bot subscription. On The X Subscription it comes with Premium ($30 a month), Super ($100) and Ultra ($200), for individuals and team seats. The Free and Plus plans don't include it.

Older plans still work: every paid individual Cursor plan and Cursor Teams include Grok Bot, and you can link an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription to a Cursor account. Some accounts are offered a trial instead: a usage credit with a 7-day window that never turns into a paid plan.

Every plan comes with a weekly usage allowance shared with the Grok apps and Cursor. The full plan table, the trial rules and what happens when the allowance runs out are on our Grok Bot pricing page.

A template is a public copy of someone's Bot setup at an x.ai/bot/… link. Adding it creates your own independent copy; you never get the creator's computer, logins or conversation history. Think recipe, not meal: plugins have to be reinstalled, and custom MCP servers, scripts and code aren't included, so some templates need setup. Templates are made by other users, not xAI, and adding one accepts xAI's third-party bot terms.

A skill is a reusable set of instructions for how to do a task: the steps, decision rules, expected output and what needs approval. Skills live in one private library shared by all your Bots, although a Bot still needs the right app or login to use one.

The easiest way to make one is to finish a task well, then ask: "Save the process we just used as a skill called Weekly report." Where Teach a task is available, you can instead record yourself doing a browser workflow once (up to ten minutes, no microphone audio) and the Bot turns it into a draft skill to review and test. It's rolling out gradually.

A routine tells one Bot when to run a workflow: on a schedule, or when something happens, such as a Slack message, a GitHub, Linear, Sentry or PagerDuty event, an email to the Bot's own address, or a webhook call. Routines run in the cloud while your laptop is closed.

Ask for one in plain words, like "every weekday at 8:00 AM, run the Inbox skill and post a summary here; never send anything." Then check the routine's When to run, which shows the saved schedule and time zone. A new routine waits for its next scheduled time; Test runs it now, and does real work.

Limits: 50 routines per Bot, the last 20 runs kept, and schedules at least five minutes apart.

Apps (often called connectors) give a Bot a structured way to use services like Gmail, Google Calendar, Notion and Slack. Open Connect apps in the sidebar, add the app and finish the sign-in in your browser. An app can only do what the account you authorise can already do, and its login tokens stay on Cursor's connector backend, not on the Bot's computer.

Two things surprise people. A connected app is available to every Bot on your account. And apps can write: Gmail can read, draft and send mail and apply labels; Calendar can create events and answer invitations; Slack posts as you.

Approvals are your safety net. Auto Review is on by default: most actions run on their own, and when one needs your OK you get a card with Allow once, Always allow or Deny. Narrow Ask first rules always stop the actions you name. Approvals raised by a routine expire after about 30 minutes and the action doesn't run, and no approval undoes work already done.

Your plan gives you one weekly usage pool, shared across Grok Bot, the Grok apps and Cursor. Work is measured in agent steps and tokens, not messages, and Super and Ultra get bigger pools than Premium. xAI doesn't publish the pool's size or a cost per task.

When the pool runs out, the Bot stops until your allowance resets, unless you've added prepaid credit. Auto Top-up stays off unless you turn it on, and a monthly cap limits paid usage.

Routines are where usage disappears. Every run spends usage, even a run that finds nothing to do, and Cursor's own help page warns that an hourly schedule, a short interval or a Slack trigger on a busy channel can use a week of usage in a day. The arithmetic is simple: a weekday-morning routine runs 5 times a week, a daily one 7, an hourly one 168, and every 15 minutes is 672.

Grok Bot is built with Cursor. You sign in with a Cursor account, your data and privacy settings follow that account, and your Bots' computers run in Cursor's cloud. It's a separate desktop app from the Cursor code editor, also downloadable from the Grok Bot page of the Cursor dashboard.

On The X Subscription, Grok Bot draws from the same weekly pool as Cursor and the Grok apps. On a legacy Cursor plan (Pro, Pro+, Ultra or Teams), usage is metered on your Cursor account, and extra usage is Cursor on-demand usage if you've turned it on.

Two things are easy to miss: a Cursor team's model allowlist doesn't apply to Grok Bot, and deleting your Grok Bot account deletes the Cursor account too.