update · TowCue Editorial Team
xAI launches Grok Bot: always-on AI teammates with their own cloud computer
xAI launched Grok Bot on August 11, 2026 — a team of always-on AI agents with their own cloud computer that sign into your tools, work across apps, and collaborate autonomously. Available in beta for SuperGrok and Cursor subscribers.
Quick answer
xAI launched Grok Bot on August 11, 2026 (expanded access August 21) — a team of always-on AI agents that each have their own persistent cloud computer with browser, terminal, and filesystem. Bots sign into your existing tools (Gmail, Slack, CRM, Figma, GitHub, etc.), work across apps and websites — including those without clean APIs — and collaborate autonomously with other Bots via shared computer, group chats, and direct handoffs. They only surface to you for approval.
Availability (as of Aug 21, 2026): Beta, bundled into existing premium plans — SuperGrok / SuperGrok Plus / SuperGrok Heavy, Cursor Pro / Pro+ / Ultra, and Cursor Teams Standard / Premium. Grok Bot usage is separate from your Grok/Cursor plan quotas. Enterprise access via waitlist. Desktop (Linux/macOS/Windows) and iOS apps available; Android "coming soon."
Official sources: xAI Blog — Introducing Grok Bot (Aug 11) | xAI Blog — Grok Bot now included with more plans (Aug 21) | Grok Bot product page | Grok Bot docs
What is Grok Bot?
Grok Bot is xAI's first product explicitly sold as digital labor — not a chat assistant, but a team of always-on AI teammates. Each Bot is a named, persistent agent with:
- Its own cloud computer (persistent VM with browser, filesystem, terminal)
- Durable identity & memory — name, role, conversation history, preferences, files, browser sessions persist across turns
- Tool access — signs into your apps/websites (Gmail, Slack, CRM, Figma, GitHub, Linear, Notion, etc.) via connectors/MCP where available, and computer use for platforms without clean APIs
- Autonomous collaboration — multiple Bots share one user-scoped cloud computer, message each other, share context in group chats, hand off tasks, and coordinate without you routing between them
- Routine learning — you demonstrate a workflow once; the Bot saves it as a routine and re-runs it on schedule or demand
- Durable context — context compounds over time; Bots learn your voice, edge cases, and preferences
Core differentiator from chat assistants: Bots have their own computer in the cloud. They don't draft work for you to copy-paste — they log into your actual tools and finish the job in the real application. Work continues 24/7 even when your laptop is closed; you only get pinged for approval.
How it works: the architecture
One computer, many Bots
All your Bots share one persistent cloud computer (user-scoped, not Bot-scoped). This means:
- Shared files, browser sessions, app logins across all Bots
- Handoffs happen without re-authentication or context reloading
- Each Bot gets its own "screen" on that computer — parallel browser/desktop use without separate security boundaries
- The computer is isolated to your account, not individual Bots
Multi-Bot coordination
- Group chats: 2–6 Bots in one thread, visible handoffs,
@mentions,@everyonefor broadcasts - Direct Bot-to-Bot messages: asynchronous handoffs, receiving Bot wakes up, handles request, replies later
- Threads & reactions: keep main transcript clean, preserve decision context
- Chief of Staff pattern: one coordinating Bot delegates to specialists (inbox, expenses, recruiting, bug fixes, ops)
Routine learning (no workflow builder)
"Ask a Bot to follow along the next time you do a job. It watches the steps and remembers how you like the work done. It saves your workflow as a routine, takes your corrections, and runs it on its own next time." — xAI docs
No drag-and-drop builder. You demonstrate once, Bot persists the routine, re-runs on schedule or trigger.
Availability & pricing (as of Aug 21, 2026)
| Plan | Grok Bot access |
|---|---|
| SuperGrok | ✅ Included |
| SuperGrok Plus | ✅ Included |
| SuperGrok Heavy | ✅ Included |
| Cursor Pro | ✅ Included |
| Cursor Pro+ | ✅ Included |
| Cursor Ultra | ✅ Included |
| Cursor Teams Standard | ✅ Included |
| Cursor Teams Premium | ✅ Included |
Key points:
- Grok Bot usage is separate from your Grok/Cursor plan quotas
- Desktop apps: macOS, Windows, Linux (download from x.ai/bot)
- Mobile: iOS app available; Android "coming soon"
- Enterprise: waitlist only (sales-led)
- Bot limits: up to 50 Bots + group chats combined per account
Not a standalone product — Grok Bot rides on existing premium subscriptions. Cursor Ultra ($200/mo) includes Grok Bot's computer, tool sign-ins, scheduled routines, desktop/mobile access, and extended token limits. Cursor Premium Teams ($120/seat/mo) adds centralized billing, team marketplace, shared analytics, SAML/OIDC SSO.
Inside xAI: how the SpaceXAI team uses Grok Bot
xAI dogfoods Grok Bot internally. Per the launch post and PM guide:
| Bot role | What it does |
|---|---|
| Sales outbound | Researches accounts overnight, scores contacts for intent, drafts email/LinkedIn in each seller's voice, leaves approval queue |
| Demo readiness | Checks environment overnight, fixes broken seeds/stale data in product UI, drops pre-call checklist |
| CRM hygiene | Updates CRM notes from call transcripts, processes invoices from Gmail, seats new hires |
| Engineering (PM Pete's team) | Chief of Staff → Eng Manager (Emily) → 5× Eng IC agents. EM breaks down work, delegates to ICs, validates outputs. Eng agents spin Cloud Agents, test, coordinate. |
| Data analyst (Ashley) | Warehouse queries, charts, goal tracking, morning dashboard review |
| PM Pete | RFCs, research, feedback, docs, product reviews that "sound like a PM, not an intern" |
| Recruiter | Finds undiscovered talent, manages recruiting loops |
Key PM insight (Kevin Niparko, xAI PM): "Grok Bot now represents a double-digit percent of our internal merged PRs." The EM/IC agent pattern with Cloud Agents under the hood lets PMs operate at higher abstraction — express sophisticated goals, Bot decomposes, allocates, reviews, integrates.
Grok Bot vs. other agent approaches
| Dimension | Grok Bot | Traditional chat agent | Workflow builders (Zapier, n8n) | Codex Remote / Claude Computer Use |
|---|---|---|---|---|
| Execution environment | Persistent cloud VM (browser + terminal + FS) | None (chat only) | Your machine / cloud functions | Your machine (Codex) / Anthropic sandbox (Claude) |
| Tool access | Connectors + computer use (any web/desktop app) | Limited to APIs/MCP | Pre-built integrations | Connectors + computer use |
| Persistence | Named Bots, durable memory, shared computer | Session-based | Workflow-state only | Session-based (Codex) / session (Claude) |
| Multi-agent | Native: shared computer, group chat, direct handoff | Manual orchestration | Manual | Manual (Codex) / not in Managed Agents (Claude) |
| Routine learning | Demonstrate once → auto-routine | Not supported | Build visually | Not native (Codex) / not native (Claude) |
| 24/7 operation | Yes (cloud VM always on) | No | Scheduled triggers | Requires host awake (Codex) / host awake (Claude) |
| Human role | Approver / chief of staff | Prompter / micromanager | Workflow designer | Approver / supervisor |
| Pricing model | Bundled in premium plans | Per-token / subscription | Per-task / subscription | Bundled (Codex) / per-token (Claude API) |
Limitations & open questions (as of Aug 2026)
| Area | Status |
|---|---|
| Android app | "Coming soon" — not yet available |
| Enterprise self-serve | Waitlist only; sales-led |
| Bot limits | 50 Bots + group chats per account |
| Platform support | Desktop (macOS/Win/Linux), iOS only |
| Security boundaries | All Bots share one computer — single security boundary per account. No per-Bot isolation of logins/files. |
| Connector coverage | Computer use covers apps without APIs, but reliability varies by platform |
| Audit/governance | No documented per-action audit log, approval trail export, or domain allowlist for built-in browser (similar to Claude's gap) |
| Model | Uses Grok 4.6 (per product page); future models not confirmed |
| Third-party Bot sharing | Public share links copy Bot config (identity, description, skills, routines) — not your computer, logins, or history. Third-party Bot terms apply. |
TowCue take
Grok Bot represents a category shift: from "AI assistant you prompt" to "digital teammate you manage." The architectural choices are deliberate:
- Shared cloud computer — solves the handoff/auth fragmentation that plagues multi-agent systems. One login, shared session, parallel screens.
- No workflow builder — demonstration-based routines lower the adoption barrier but trade off explicit controllability. Good for repetitive ops; risky for regulated workflows.
- Bundled distribution — riding on Cursor/SuperGrok plans is smart go-to-market. Lowers CAC, locks in xAI↔Cursor ecosystem.
- PM-as-chief-of-staff — the EM/IC agent pattern mirrors how engineering orgs actually work. This is the first agent product designed for that mental model.
For teams evaluating:
- Strong fit: Sales outbound, recruiting, ops, PM-heavy engineering orgs already on Cursor/SuperGrok. Repetitive multi-tool workflows (CRM → Gmail → Slack → Linear).
- Proceed with caution: Regulated environments needing per-action audit trails, per-Bot isolation, or domain allowlists. No Android yet.
- Wait: If you need enterprise SSO/SCIM, self-serve admin controls, or Android support.
Bottom line: Grok Bot is the most opinionated "digital teammate" product to date. It bets on shared computer + demonstration-based routines + native multi-agent coordination over explicit workflow construction. For Cursor/SuperGrok subscribers, the beta is zero-marginal-cost to try — create a Bot, give it a real task this week, and see if it feels like a teammate or a toy.
Verify current plan eligibility and download links at x.ai/bot.