Getting started with Grok Bot

The safest way to learn Grok Bot is to complete one small, verifiable job before adding plugins or schedules. This guide moves from platform and account checks to a useful manual task, then to reusable skills and routines.

1. Confirm your platform

Use the official download route and match the installer to your device:

• macOS: Apple silicon or Intel
• Windows: x64 or Arm64
• iPhone: iOS 18 or later

The dedicated app is not currently documented for iPad, Android, or Linux desktop. Use the platform checker if you are unsure. Avoid third-party installers.

2. Confirm your access path

Paid Cursor individual plans and Cursor Teams currently include Grok Bot. Eligible individual SuperGrok plans can be linked to Cursor, but not every tier or organization plan uses this route. Confirm the current rule with the plan finder and official plan page before buying or changing a subscription.

Sign in with the identity that owns the eligible plan. An account mismatch can look like a product failure.

3. Choose a first task with a visible result

Good first tasks are small, reversible, and easy to inspect:

• Turn supplied notes into a one-page brief
• Compare two documents and cite the relevant sections
• Create a checklist from an existing process
• Organize a harmless sample folder and produce a manifest
• Draft a message without sending it

Avoid production deployments, customer data, broad folder access, or external sending during onboarding.

4. Write an output contract

State what “done” means before starting. A compact brief should include:

Goal: [one concrete outcome]
Allowed inputs: [specific files, notes, or URLs]
Output: [format, length, required citations]
Do not: [external actions and other non-goals]
Missing data: stop and list what is missing
Review: create a draft; I approve before any external action

The workflow builder produces a reusable version of this brief.

5. Treat approvals as decision points

Read the proposed action and target. A request to read one folder is different from access to an entire drive; drafting is different from sending. Keep passwords, cookies, keys, recovery codes, and unrestricted production credentials out of prompts.

If an approval is broader than the task needs, deny it and narrow the task. See approvals and safer workflows.

6. Verify the actual artifact

Inspect the file, document, branch, message draft, or connected-service record. Do not treat “done” in chat as proof. Check:

• Did the requested artifact appear in the intended location?
• Are factual claims tied to the allowed sources?
• Did the task stay inside the stated scope?
• Is any external action still waiting for human review?

Record one thing that improved the prompt and one thing you would forbid next time.

7. Save a skill after the method works

Turn stable instructions into a skill only after a successful manual run. Keep temporary details outside the skill. This makes the method reusable without freezing today’s project or date into every future task.

8. Add one plugin only when earned

Cursor currently documents Gmail, Notion, and Slack plugins. Start with the smallest account and access level needed. Read the live provider authorization screen, test with non-sensitive data, and keep a draft-before-send rule. Use the plugin access planner before connecting.

9. Create a routine last

A routine should specify its schedule or event, timezone, inputs, output contract, stop conditions, and review gate. Run it manually first, then inspect recent run history after scheduling. Do not duplicate a routine just because one run appears late; diagnose the original first.

First-week finish line

Onboarding is successful when you have:

1. One verified artifact you trust
2. One reusable skill or saved brief
3. A written permission boundary
4. One routine candidate with a test run and review gate
5. No unexplained plugins or broad approvals

Use the setup checklist to track this locally. If something fails, start with the troubleshooter rather than resetting immediately.

Sources and verification

Last verified: August 27, 2026.

• Grok Bot: Get Started (xAI)
• Getting started with Grok Bot (Cursor)
• Skills, routines, and automations (xAI)
• Approvals, security, and privacy (xAI)
• Connect plugins to Grok Bot (Cursor)