Set up your first Grok Bot

Step 1

Requirements and plans

No separate Grok Bot subscription. Access is included with:

There is a free trial (usage credit + 7-day window). Credit is consumed by agent steps and tokens, not by message count. A long job can empty it in one run.

Grok Bot has its own weekly quota, separate from regular Cursor and Grok usage. If you have both Cursor and SuperGrok, the one that gives you more is used. When the quota runs out, work can continue on-demand if that is enabled.

Platforms (September 2026)

Step 2

Download the app

1. Go to x.ai/bot
2. Pick the right build

macOS. Apple silicon or Intel (Apple menu → About This Mac: Chip = Apple silicon, Processor = Intel). Open the dmg, drag Grok Bot to Applications. If macOS asks: Open.

Windows. Run the installer (x64 or Arm64), open from Start.

Linux. Under More downloads on x.ai/bot. uname -m → x86_64 = x64, aarch64 = Arm64.

iPhone / Android. App Store / Play. The same Bots and conversations sync.

Step 3

Sign in

1. Get started on the welcome screen (or Sign In with Cursor under Settings)
2. Finish sign-in in the browser window that opens
3. Return to Grok Bot

Sign-in is your Cursor account, not a separate Grok Bot account. Companies with SSO use the normal organization login.

The first time, the app asks which tools you use. That shapes suggestions for your first teammate, but does not connect the tools for you. If you only have SuperGrok or X Premium+ (no Cursor plan): link the account from Grok Bot’s plans screen after sign-in.

Step 4

Create your first Bot: Chief of Staff

The pattern tutorials and X users land on: one pinned coordinator you talk to, that delegates to specialists.

1. Pick a suggested teammate, or New (Cmd/Ctrl+N) → Create new agent
2. Bot actions → Edit Profile: name, title, description, avatar
3. Pin it

The description is the system prompt. Write it like a job, not a personality.

Step 5

First task: five parts

Official get-started and X users agree on what a good first question contains:

1. 1OutcomeWhat is done when the job is finished?
2. 2SourcesWhich apps, sites, files?
3. 3LimitsWhat must it not do?
4. 4DeliveryWhat format should you get back?
5. 5ReviewWhen should it stop and ask you?

First test, no login. Attach a document:

“Summarize the document in five bullets. List dates, decisions, and open questions in their own sections. Cite page/section for each point. Do not change the source file.”

Second test, in a real tool:

“Open our analytics dashboard and compare new-user activation this week with the previous four. Call out the biggest step that changed and write a short investigation plan with links to the charts. Change no dashboards. Ask me to log in if needed.”

Step 6

Connect tools

Plugins (first choice)

1. Settings → Plugins
2. Add what you need
3. Authenticate in the browser
4. In chat: @ for a connector, / for a skill

Start with mail + calendar. The X plugin automatically creates a developer account with starter credits when you connect your X profile. There is a Microsoft plugin for Outlook, Calendar, and OneDrive.

Plugins are account-wide. One login applies to all Bots.

The browser (when there is no plugin)

When the Bot hits a login, it asks you to take over:

1. Open Agent Computer in the conversation
2. Take control
3. Type passwords / 2FA / CAPTCHA yourself
4. Hand control back

Step 7

Skills, then routines

The order in the docs, and what builders on X repeat:

once → make it reliable → save as skill → test → only then schedule

A routine inherits every unspoken assumption in the task it was built from. A wrong morning routine can run four days before you notice.

Save a skill

“Save the process we just used as a skill named "Weekly account health". Include source systems, risk definitions, output format, and the rule that customer contact always requires approval.”

A good skill says: when to use it, which inputs, step order, how to validate the result, what comes back, what needs approval.

Teach a task (if the button is visible): open the computer view, record up to 10 minutes, review the draft skill, test on a safe example. No mic audio. Do not show secrets in the recording.

Create a routine

“Every weekday at 08:00, run skill X against list Y. Post the result in this thread. Contact no one. If the source is down: report the error, do not invent data.”

Confirm: owning Bot, timezone, input, expected result, approval boundary, what happens when the source is missing. Then Test run. A test does real work, so keep write actions behind approval.

Manage routines via the Bot → View conversation details → Routines (pause, test, edit, history). One Bot can own 50 routines. The 20 most recent runs are kept. Deletion has no undo.

Step 8

First-evening checklist

1. 01Paid Cursor plan, SuperGrok, or X Premium+ (or trial)
2. 02Turn off Legacy Privacy Mode in Cursor
3. 03Install from x.ai/bot
4. 04Sign in with the right Cursor account
5. 05Create a Chief of Staff, pin it, write fences in the description
6. 06One five-part task against a document
7. 07Connect Gmail + Calendar when you need them
8. 08One more task in a real tool, drafts only
9. 09Save as a skill when the flow sticks
10. 10Routine on a weekday morning, with a test run first