Full Tutorial Guide: Grok AGENTS

Grok Bot is xAI’s system of AI teammates. Each bot runs on a cloud computer, signs into real apps and websites, and completes work end-to-end.

The most important architectural fact

All bots on one account share one persistent cloud computer.

Each bot gets its own screen, but files, browser sessions, and logins are shared.

Official statement from xAI documentation:

“Do not use separate Bots as a security boundary.”

1. Requirements and access

Eligible plans: SuperGrok Plus / Heavy, Cursor Pro+ / Ultra, or Cursor Teams

Cursor account (authentication and data settings are handled by Cursor) • Supported platforms: macOS, Windows, iOS 18+

2. Installation and sign-in

1. Download the app from x.ai/bot or cursor.com/bot/onboarding.

2. Install and launch it.

3. Click Sign in with Cursor.

3. Creating your first bot

1. Click New → Create new agent.

2. Set the name, role, description, and avatar via Edit Profile.

Good role description example:

> Own weekly account-health review. Never contact customers or change accounts without approval.

Limit: up to 50 bots + group chats per account.

4. Interface and giving tasks

Left sidebar — list of bots.

Center — chat.

Right side (or via button) — Agent Computer screen.

Write to the bot like a teammate. A strong request always includes:

> Desired outcome

> Sources

> Constraints

> Deliverable format

> When to stop for your approval

5. Shared computer and takeover

Open Agent Computer to watch the bot work in real time.

When the bot needs a password, 2FA, CAPTCHA, or payment confirmation, it hands control to you:

1. Click Take over

2. Complete the sensitive step yourself

3. Return control with I’m done

Never send passwords or one-time codes in regular chat.

6. Managing bots

From the bot menu you can:

> Edit Profile

> Duplicate

> Hide

> Delete

Important: Deleting a bot only removes its profile, conversation, and routines.

Files and logins on the shared computer may remain. Always revoke access in the external services separately.

7. Security and approvals

• Grant access at the account level

• Put clear boundaries in the bot description and every request

• Create narrow Require Approval rules in Settings → Auto-review

• For local computer access, start with Never allowed

Group chats, Skills, and Routines all run on the same shared machine.

8. Recommended safe pilot

1. Create 1–3 focused bots

2. Start only with reversible tasks (research, drafts, triage)

3. Keep payments and production systems out of the pilot

4. Set Require Approval for all external actions

5. Weekly check what has accumulated on the shared computer

Quick reference

• Marketing says “its own computer” → architecture says “one shared computer per account”

• A separate bot is not a security boundary • Secrets only via takeover

• Deleting a bot ≠ cleaning up its traces

• Authentication and data are governed by Cursor Official documentation: docs.x.ai/grok-bot