Grok Bot Setup: Install, Sign In, and Your First Bot

Before you start

Step 1 — Install the desktop app

Download from x.ai/bot. Only use that page or your OS's official store listing. Grok Bot is popular enough that lookalike downloads are a real risk.

• macOS: pick Apple silicon or Intel → open the disk image → drag Grok Bot to Applications → launch.
• Windows: pick x64 or Arm64 → run the installer → open from the Start menu.
• Linux: pick x64 or Arm64 in your format, then install with your package manager, or mark the AppImage executable and run it:

# Debian/Ubuntu
sudo apt install ./grok-bot_*.deb
# Fedora/RHEL
sudo dnf install ./grok-bot-*.rpm
# AppImage
chmod +x Grok*.AppImage && ./Grok*.AppImage

File names vary by release. Use the one you downloaded.

Step 2 — Sign in (and link SuperGrok if that's your plan)

1. Choose Sign in on the welcome screen. If the app is already open, use Sign In with Cursor in Settings.
2. Finish authentication in the browser window, then return to Grok Bot.
3. SuperGrok subscribers: Settings → Usage & Billing → Link SuperGrok Heavy (or your tier).

Step 3 — Create your first Bot

Choose New in the sidebar or press Cmd/Ctrl+N. Pick a suggested teammate or Create your own, and give it three things: a short name, one primary job, and how it should work.

The description holds the Bot's permanent rules. Messages are for task-specific guidance. Write the description as rules you'd want enforced every time, including at least one "never":

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

Example adapted from xAI's getting-started guide. Start with the smallest useful roster. One Bot with a clear job beats five vague ones.

Step 4 — Give it a first task: the five-part formula

1. Outcome: the final deliverable you want.
2. Sources: which apps, sites, files or conversations to use.
3. Constraints: what to avoid, and what needs your approval.
4. Deliverable: the exact output format.
5. Review point: when it should stop and check with you.

Summarize this document in five bullets. List every date, decision and open
question separately. Cite the page or section for each. Do not change the
source file. Stop and show me before doing anything else with it.

Step 5 — Logins: computer takeover, not pasted passwords

When a Bot needs to log into a site, don't paste a password into chat. Open Agent Computer from the conversation, take over control, enter the password, 2FA code or CAPTCHA yourself, and hand control back. The browser session then persists on the shared computer, so your other Bots can reuse that login. Keep that in mind when deciding which accounts to log into (see security).

Where a connector exists, prefer it: Marketplace in the sidebar → find the service → add the account → authorize. Connector tokens stay on Cursor's backend and are never stored on the computer. Details in plugins.

Step 6 — Review, refine, then automate

Ask for revisions, and name the preference when you do ("always put dates in ISO format") so the Bot remembers it. Once a workflow produces what you want twice in a row, save it as a skill, then attach a routine to run it on a schedule or an event. See skills & routines.

Troubleshooting setup