Research summary

Grok Bot

Prepared for Josh D 2026-08-12 Researcher Deep dive · functionality, config, privacy, community
SpaceXAI + Cursor Early beta · launched 2026-08-11 Agents · cloud computer · routines Light theme

Executive brief

Grok Bot is a team of persistent AI “teammates” (Bots) you message like coworkers. They run on a user-scoped cloud Linux computer, sign into real apps (Plugins/MCP when available, browser computer-use otherwise), finish multi-step work, and interrupt mainly for approvals. Skills and routines make work repeatable; multiple Bots can coordinate via messaging and group chats.

Access
SuperGrok Heavy · Cursor Ultra ($200) · Teams Premium ($120/seat)
Clients (official)
macOS · Windows · iPhone (iOS 18+)
Architecture
One shared cloud PC per user · per-Bot screens
Privacy headline
Cursor privacy · Legacy Privacy Mode blocked

Functionality

Core model

  • Bot = named persistent agent with memory, profile, skills, routines.
  • Work lands in real tools (CRM, inbox, UI), not only as chat drafts.
  • Prefer connectors (Settings → Plugins); fall back to computer-use for sites without API/MCP.
  • Up to 50 Bots + group chats combined; group chats support 2–6 Bots; Bot-to-Bot messaging.
  • No user/admin model picker — automatic routing / failover.
  • Optional: launch Cursor Cloud Agents from Grok Bot (team toggle, default on).

Skills & routines

  • Skill = reusable how-to (steps, rules, approval boundaries).
  • Routine = schedule or event trigger (e.g. Slack/GitHub via Cursor account integrations).
  • Teach-by-demonstration (≤10 min, no mic) → draft skill; gradual rollout.
  • Limits: 50 routines/Bot; 20 recent run records kept per routine.

Documented starter roles

Sales Outbound · Talent Scout · Paid Media · Expense Manager · Product Performance · Bug Reproduction · Account Health · Chief of Staff — all framed as prepare/draft first, then approve send/change.

Configuration

  1. Eligible plan; leave Legacy Privacy Mode.
  2. Install desktop app (macOS/Windows) or iOS; sign in with Cursor (SSO if org).
  3. Create focused Bots (name, job, standing boundaries in description).
  4. Connect tools via Plugins and/or Agent Computer login handoff.
  5. Stabilize a task → save skill → test → schedule routine.
Platform nuance
Official docs: no Linux desktop app at launch (cloud computer itself is Linux). Several press pieces incorrectly list a Linux client — prefer docs.
SurfaceOfficial status
macOS / WindowsSupported
iPhone (iOS 18+)Supported (App Store: Anysphere)
Linux desktop / Android / iPadNot supported at launch
Local Mac/Windows executionOptional · default ask every time

Privacy & security

Still open
Exact retention for transcripts/snapshots; whether enterprise CMEK/residency covers Grok Bot VMs like Cloud Agents; exact models in the router set.

Primary refs: Approvals, security, and privacy · Cursor Privacy · Cursor Security

How people are using it

Day-one signal (product launched 2026-08-11)
Community evidence is early-beta: launch press, official demos, a few named testers, one strong HN report. Many YouTube hits are the wrong product (Grok model in Cursor IDE).

Patterns

Marketing vs docs
Press often says “each Bot has its own computer.” Docs are clear: one shared computer per user, with per-Bot screens only.

Open questions

  1. When will Linux desktop / Android / richer audit logs ship?
  2. Will users get a model picker or pin?
  3. How painful is token cost for always-on multi-bot fleets in practice?
  4. Enterprise CMEK / residency coverage for Agent Computer VMs?
  5. How durable is “Sand → Grok Bot” lineage for understanding roadmap? (press only)

Sources