Grok Bot, set up safely

• An idea of what you already pay for: a Cursor plan, a SuperGrok subscription, X Premium+, or none of these.
• Ten minutes and the official Grok Bot page open in a browser tab.

Grok Bot is included with eligible paid plans rather than sold on its own. Work out which of the three plan families you are in, then confirm on the official page that your tier is still listed.

1. 1

   Step 1: Open the official Grok Bot page (the button in the callout above this section) and find its plan and pricing section.

   At the time of checking the entry points were Cursor Pro ($20 a month), SuperGrok ($30 a month) and Cursor Teams Standard ($40 per seat a month); higher tiers in each family include more weekly usage. SuperGrok Lite and the free tiers do not include Grok Bot.

2. 2

   Step 2: If you already have a Cursor plan (Pro, Pro+, Ultra or a Teams seat), you are eligible through that account. Nothing more to buy.

3. 3

   Step 3: If you already have SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+, note that these are linked to a Cursor account to grant usage; the Team and Enterprise SuperGrok plans cannot be linked. You will create or reuse a Cursor account in section 3.

4. 4

   Step 4: If you have none of these, decide which family fits: a Cursor plan if you might also use Cursor's coding tools, SuperGrok if you already live in the Grok app. Do not buy yet; the app offers a free trial credit first.

5. 5

   Step 5: Write down which account will hold Grok Bot. A SuperGrok or X link is permanent and pairs one Cursor account with one Grok or X account, so the choice is hard to undo.

Included Grok Bot usage is its own weekly pool, separate from your normal Grok or Cursor usage, and the official pages describe tiers only relatively (higher tiers get more) without numbers. Once the weekly pool is used, further Bot work draws on your Cursor account's shared on-demand spend if that is enabled, so a plan is a ceiling on included work, not a flat fee for unlimited work.

Nothing to save on a computer. Keep the note about which account will own Grok Bot; you need it in section 3.

Before moving on, say these out loud:

1. My plan family is Cursor, SuperGrok or X Premium+, or I am starting on the trial credit.
2. I know which single account will own Grok Bot and the link.
3. I have seen today's eligibility list on the official page, not a screenshot from a post.

• A Mac (Apple silicon or Intel), a Windows PC (x64; Arm64 builds are listed in the docs), or a Linux machine (.deb, .rpm or AppImage builds); or an iPhone on iOS 18 or newer (iPad support was added to the iOS app in early September 2026), or an Android phone on Android 9 or newer.
• Permission to install apps on that device.

Grok Bot is an app, not a command-line tool. Desktop is the best place to start because the computer view is easier to follow on a large screen; the phone app is for checking in later.

1. 1

   Step 1: Desktop: open the official Grok Bot page and choose the download for your operating system; the More downloads panel lists the other platforms.

   The same builds are served from Cursor's official download page. Do not use a third-party download site.

2. 2

   Step 2: macOS: open the downloaded file, drag Grok Bot into Applications, then open it and accept the system prompt that asks whether you want to open an app downloaded from the internet.

3. 3

   Step 3: Windows: run the installer and follow its prompts. Linux: install the package for your distribution, or run the AppImage.

4. 4

   Step 4: Phone or tablet: install Grok Bot from the App Store or Google Play and open it. The listing is published under xAI's company names (you may see SpaceXAI, X.AI Corp. or X Corp.), and its support and terms links point to cursor.com.

5. 5

   Step 5: Open the app. Stop at the Get started screen; signing in is the next section.

The app updates itself after installation, so you will not repeat this section for new versions.

Nothing to configure. The installer places the app; settings live in your account, not in local files you need to manage.

The app is installed when:

1. Grok Bot opens from Applications, the Start menu or your phone's home screen.
2. The first screen offers Get started or sign-in rather than an error.

• Section 1 decided: which account owns Grok Bot.
• A browser on the same device; sign-in completes in the browser and returns you to the app.

There is no separate Grok Bot login. The app uses a Cursor account, and a SuperGrok or X Premium+ subscription is attached to that Cursor account by linking it from the plan screen.

1. 1

   Step 1: Choose Get started (desktop) or Login with Cursor (phone). A browser tab opens for authentication; it may also offer Sign in with Grok, which still ends in a Cursor account.

2. 2

   Step 2: Sign in to the Cursor account that should own Grok Bot, or create one. Organizations that use single sign-on with Cursor sign in the same way.

3. 3

   Step 3: Return to the app when the browser confirms sign-in. On desktop it usually switches back on its own.

4. 4

   Step 4: Open the plan screen (Plans and billing, or the plan prompt during onboarding). If you have a Cursor plan, it is already applied.

5. 5

   Step 5: If you have SuperGrok or X Premium+, choose Link Grok Account or Link X Account (offered on the Get started screen and on the plan screen), sign in to that account, and confirm. The link pairs exactly one Cursor account with one Grok or X account and cannot be moved later.

6. 6

   Step 6: If you have no eligible plan yet, start on the free trial credit and buy after section 5, once a Bot has done real work for you.

If your Cursor account was set to the older privacy option that keeps all data local (Legacy Privacy Mode), the app asks you to change that setting before continuing; Grok Bot needs to store data in the vendor's cloud to work at all. The current Privacy Mode still keeps your data out of model training.

Nothing to save by hand. The sign-in and the plan link are stored on your account and follow you to the phone app.

You are signed in properly when:

1. The app shows the account name you chose in section 1.
2. The plan screen names a plan with Grok Bot usage, or the trial credit.
3. You did not paste a password or a key into any chat box; sign-in happened in the browser.

• Signed in with a plan or trial (section 3).
• One small, real, harmless job you would like done: a research summary, a weekly digest draft, a tidy-up of a document.

A Bot is a named, persistent teammate: it keeps its own conversation and working context, and it uses the account's cloud computer. Onboarding offers suggested teammates; you can also describe your own.

1. 1

   Step 1: Choose Create a Bot, or pick a suggested teammate to edit.

2. 2

   Step 2: Give it a short name and a one-line primary job. One job, not a list; you can create more Bots later.

   Good first jobs are read-mostly: summarize, draft, compare, monitor. Save anything that sends, buys or deletes for after section 7. Some versions of the onboarding also ask for a shape, colour and title; those are cosmetic.

3. 3

   Step 3: Write a few sentences describing how it should work: what to look at, what a good result looks like, and what it must ask you before doing.

4. 4

   Step 4: Finish onboarding. The app opens the Bot's conversation; the account's cloud computer is set up in the background during onboarding and may still be finishing.

Each Bot is separate in role and conversation, but every Bot on your account shares the same cloud computer, files and website logins. Keep that in mind before you name a Bot after a client.

Bot configuration saves automatically to your account and appears on every device you sign in on.

The Bot exists when:

1. It appears in the Bots list with the name and job you gave it.
2. Opening it shows an empty conversation ready for a first message.

• A Bot from section 4.
• A task you can check yourself in under five minutes.

Describe the outcome you want in the Bot's chat, as you would to a new colleague. You can steer or stop it at any time by sending another message. Here is a first task that produces something you can verify:

Read the public page at [paste a URL you know well] and give me a five-bullet summary. Do not sign in to anything, do not fill in any form, and do not send anything. Tell me when you are done.

1. 1

   Step 1: Copy the task below into the Bot's chat and send it. Watch the computer view: the Bot opens its cloud browser and works whether you watch or not; closing the app does not stop it.

2. 2

   Step 2: When it reports back, check the result against the page yourself. The test is accuracy, not speed.

3. 3

   Step 3: Send one follow-up that changes the result (a different focus for the summary, say) and confirm the Bot uses the earlier context.

4. 4

   Step 4: Optional: close the laptop for a minute and reopen the app. The conversation and the result are still there; the Bot's computer keeps its files between sessions.

A Bot proves itself with a result you can check, not with a welcome message. Only the second step of this section is the test.

Results stay in the conversation. If you want a file, ask the Bot to save one to the workspace and send it to the chat as an attachment.

You have a first success when:

1. The result matches the page you asked about.
2. A follow-up message changed the result without you repeating the task.
3. The conversation was still there after closing and reopening the app.

• A proven Bot (section 5).
• One tool you use every week, ideally one with a plugin: a calendar, a notes app, an inbox.

Bots reach the outside world in two ways. Plugins are structured connectors to services such as email, notes and chat tools; they belong to your account and are shared by all your Bots. Computer use is the Bot operating its cloud browser like a person, which works for sites without a plugin but is less reliable than a connector and needs you to sign it in. Prefer a plugin when one exists.

1. 1

   Step 1: Open Plugins (in Settings, or from the sidebar) and look for the tool. If it is listed, connect it and approve the access request in the browser.

   Connector sign-in happens with the service itself in your browser. The Bot never sees your password, and the connector's access token stays on Cursor's backend rather than on the cloud computer.

2. 2

   Step 2: If there is no plugin, open the computer view and use the takeover control to sign in to the website yourself on the Bot's screen. Complete any two-factor step yourself, then hand control back.

3. 3

   Step 3: Ask the Bot for a read-only task using that tool: list this week's events, summarize unread messages from one sender, find one note.

4. 4

   Step 4: Check the result in the tool yourself.

If a Bot ever asks you for a password or a code in the chat, do not type it there. The app has a separate secure secret request for this: it masks the value, keeps it out of the transcript and hides it from the model. Use that, or sign in yourself through the takeover control.

Connections persist on your account and on the cloud computer's disk. Browser sign-ins made on the Bot's computer usually stay signed in, though they can drop if the computer is recreated; sign in again through the takeover control if a site asks.

The tool is connected when:

1. The plugin is listed as connected, or the site shows as signed in on the Bot's screen.
2. A read-only task returns data you recognize from the tool.
3. You never typed a password or a code into the chat.

• Sections 1 to 6 complete.
• Fifteen minutes in Settings.

Grok Bot ships with sensible defaults for approvals and privacy. The baseline is not changing them blindly; it is looking at each one and knowing what it does. Four moves:

1. 1

   Step 1: Approvals: open the settings for approvals and sensitive actions (the Auto Review controls). Confirm that sensitive actions (sending, purchasing, deleting, sharing outside your account) require your approval, and keep it that way for every Bot that touches money, clients or public channels.

2. 2

   Step 2: Privacy Mode: confirm your Cursor account is on the current Privacy Mode, which keeps your data out of model training. Read the current data-handling page so you know what is stored in the vendor's cloud: files, browser sessions and conversations persist there.

3. 3

   Step 3: Account separation: decide now whether your own business and any client work need separate accounts. All Bots on one account share one computer, one set of logins and one file workspace, so separating identities means separate accounts, not separate Bots.

4. 4

   Step 4: Secrets: agree with yourself never to paste passwords, codes or keys into a chat. Use the secure secret request or the takeover sign-in, and revoke any credential that ever appears in a transcript.

Routines that run unattended (see Go further) inherit these settings. The official guidance matches ours: keep routines for reports and digests, and keep sending, purchasing, deleting and publishing behind approval.

Settings apply account-wide and immediately; there is no file to edit.

Prove it, do not assume it:

1. Ask a Bot to do one clearly sensitive but harmless thing and watch for the approval prompt, then decline it. If you connected an inbox in section 6, drafting and sending a message to yourself is the easiest test; otherwise ask it to delete a file it created on its own computer.
2. Confirm Privacy Mode is on in your Cursor account settings.
3. Confirm no second identity shares this account, or that you have created a separate account for it.