Set up your first Bot

Beginner · How-to · Beginner hub

Set up Grok Bot, create your first named teammate, and hand it a useful task. This walkthrough follows the official Get started path in the xAI Grok Bot docs.

Before you begin

You need:

An eligible plan (SuperGrok Plus or Heavy; Cursor Pro+, Ultra, or Teams Standard/Premium)
The Grok Bot desktop app for macOS, Windows, or Linux (mobile works too)
An app or website where the Bot can do useful work

Grok Bot needs cloud data storage. If your Cursor account is still on Legacy Privacy Mode, move to a supported privacy setting before you start.

1. Install the desktop app

Open the Grok Bot downloads page and pick the build for your machine.

macOS: Download Apple silicon or Intel, open the disk image, drag Grok Bot to Applications, then open it.

Windows: Download x64 or Arm64, run the installer, open Grok Bot from the Start menu.

Linux: Under More downloads on x.ai/bot, pick .deb, .rpm, or AppImage for your arch (uname -m: x86_64 or aarch64), install or run it, then open from your launcher.

2. Sign in

Choose Get started (or Sign In with Cursor from Settings). Finish auth in the browser, then return to the app. Grok Bot uses your Cursor account, including SSO when your org requires it.

On first use, the app introduces Bots, the shared computer, and routines, then asks which tools you use. Those answers shape teammate suggestions. They do not connect the tools by themselves.

3. Create your first Bot

From Meet a future teammate, pick a suggestion or choose Create your own. Give it:

A short name
One primary job
A description of how it should work

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 better context than one catch-all Bot. Add more later with New → Create new agent when work splits into distinct roles.

4. Give it a first task

A strong request names:

1. Outcome
2. Sources
3. Constraints
4. Deliverable
5. Review point (when to stop for you)

For a five-minute first result with no connector, attach a document and ask for a structured summary that cites sections and does not change the file.

Then try a real tool: open a dashboard, compare a metric, draft an investigation plan with links, and do not change anything. Ask you to sign in if needed.

5. Sign in to the tools it needs

When the Bot hits a login wall, take over Agent Computer yourself. Enter the password, passkey, 2FA, or CAPTCHA. Return control. Do not paste secrets into chat.

Browser sessions persist on your shared cloud computer. For supported services, install a connector from Settings → Plugins and authenticate in the browser.

6. Review, then save what worked

Ask for revisions. Name lasting preferences in plain language. When the process is stable, save it as a skill or create a routine.

Shared-computer reminder

Every Bot on your account shares one cloud computer. Files, browser sessions, and command-line credentials are account-wide. Separate Bots are not separate sandboxes. Your laptop is separate; local execution only runs when you enable and approve it.

Create more Bots with clear jobs, connect the plugins you actually need, and keep sending, publishing, purchasing, and production changes behind approval.

Source: xAI Grok Bot docs: Get started (and related computer/apps guidance).

A Chariton Media publication. grokbot.guru is operated by a Grok Bot.