Get started

Set up Grok Bot, create your first Bot, and hand it a useful task.

You need:

• An eligible plan: SuperGrok Heavy, Cursor Ultra, Cursor Teams Premium (sign in with your Cursor account)
• The Grok Bot desktop app for macOS or Windows
• An app or website where your first Bot can do useful work

Grok Bot is not currently available as a Linux desktop app. You can also set up and use Grok Bot for iOS.

Grok Bot requires cloud data storage. Accounts using Legacy Privacy Mode must move to a supported Cursor data setting before Grok Bot can start. Open Cursor privacy settings to review the account setting.

Open the Grok Bot access page and choose the download for your computer.

1. Choose the Apple silicon or Intel download.
2. Open the downloaded disk image.
3. Drag Grok Bot to Applications.
4. Open Grok Bot. If macOS asks for confirmation, choose Open.

To check which download you need, open Apple menu → About This Mac. A Chip field means Apple silicon; a Processor field means Intel.

1. Choose the x64 or Arm64 download.
2. Run the installer.
3. Open Grok Bot from the Start menu.

To check the architecture, open Settings → System → About → System type.

Grok Bot checks for updates automatically. You can also use Check for Updates from Settings → Beta.

1. Choose Get started on the welcome screen. If you are already in the app, use Sign In with Cursor from Settings.
2. Finish authentication in the browser window that opens.
3. Return to Grok Bot after the browser confirms the sign-in.

Grok Bot uses your Cursor account. If your organization requires single sign-on (SSO), complete the normal organization sign-in flow.

On first use, Grok Bot introduces Bots, the shared computer, and routines, then asks which tools you use. These answers shape the first teammate suggestions; they do not connect or modify those tools by themselves. Computer setup runs in the background and the final step opens Meet a future teammate.

Choose a suggested teammate from Meet a future teammate, or choose Create your own and give the Bot:

• a short name;
• one primary job; and
• a description of how it should work.

For example:

Name: Piper
Job: Product performance
Description: Investigate product-performance questions using our observability tools. Preserve links and screenshots, separate evidence from hypotheses, and return a short summary with the highest-impact issue first. Never change production settings.

Focused Bots build more useful context than one catch-all Bot. You can add more Bots later with New → Create new agent when work naturally splits into distinct roles.

A strong request includes:

1. Outcome: What should be finished?
2. Sources: Which apps, websites, files, or conversations matter?
3. Constraints: What must the Bot avoid or ask before doing?
4. Deliverable: What should it return?
5. Review point: When should it stop for you?

For a five-minute first result that needs no connector or website login, attach a document and try:

Summarize this document in five bullets. List every date, decision, and open question in a separate section. Cite the page or section for each item. Do not change the source file.

Then try a task in one of your tools:

Open our analytics dashboard and compare new-user activation for this week with the previous four weeks. Identify the largest step-level change and draft a short investigation plan with links to the relevant charts. Do not change any dashboards. Ask me to sign in if needed.

Before allowing external changes, review Approvals, security, and privacy.

When the Bot reaches an app that requires authentication, it may ask you to take over the computer.

1. Open Agent Computer from the conversation.
2. Choose the takeover control.
3. Enter the password, passkey, two-factor code, or complete the CAPTCHA yourself.
4. Return control to the Bot.

The browser session persists on your shared Grok Bot computer, so other Bots can use the same signed-in session when appropriate.

For supported services, you can also install a connector from Settings → Plugins and authenticate it in your browser.

Ask the Bot to revise anything that is incomplete or formatted incorrectly. Name the lasting preference explicitly:

Use this format for future weekly reports: five bullets, source links inline, and a final section called “Decisions needed.”

When the process is stable, ask the Bot to save it as a skill or create a routine.

• Create and manage more Bots
• Use apps and the cloud computer
• Attach files and review results
• Set approval and privacy controls