Grok Bot
xAI's always-on AI teammates. Each account gets one persistent cloud computer that your Bots share. They run skills and routines while your laptop is closed.
Grok Bot is a different kind of agent from most of what we cover. You don't install a harness and point it at a model. You create named teammates, each with one job, and they work on a cloud computer xAI runs for you. That computer has a real browser, a file system and a terminal. Bots log into websites the way you would, keep working when you close the app, and can wake on a schedule or an event. The trade-off is the usual one for hosted products: easy to start and always on, but closed, US-hosted, and with a security model you have to understand. The biggest point: all your Bots share one computer, so separate Bots are not separate security zones. This hub covers setup through team rollout, based on xAI's documentation and the builds we've summarised from video.
Guides
If your data must stay on your own hardware or outside the US, Grok Bot is out. Its computers run in the United States and it requires cloud storage. Use Hermes or OpenClaw self-hosted instead. If you need hard isolation between jobs, remember that every Bot on an account shares one computer. If you mainly want a coding agent, Cursor's own agents or Kilo Code fit better, and Grok Bot is aimed at admin, research and operations work. Grok Bot is best for people who want always-on assistants for inbox, research, reporting and web chores without running a server.
At a Glance
| Factor | Detail |
|---|---|
| What it is | Hosted AI teammates, each with a role, on a shared persistent cloud computer (browser, file system, terminal) |
| Who makes it | xAI (docs at docs.x.ai), distributed with Cursor (Anysphere). Accounts and billing go through Cursor |
| Status | Beta since 2026-08-11. The UI changes often, so update the desktop app before following any guide |
| Surfaces | Desktop apps for macOS, Windows and Linux; companion apps for iPhone, iPad and Android. Conversations sync across devices |
| Access | Paid Cursor plans (Pro, Pro+, Ultra, Teams), or linked SuperGrok / SuperGrok Plus / SuperGrok Heavy / X Premium+ |
| Automation | Skills (reusable instructions) plus routines (schedule, Slack or GitHub event, webhook). Up to 50 routines per Bot |
| Isolation | None between Bots on one account. Bots share files, browser sessions and logins |
| Data location | Computers run in the US. Privacy Mode means no training on your data and zero retention at model providers |
| Best for | Inbox triage, research and briefings, reporting, recurring web chores, small teams of role-based assistants |
| Less ideal for | Self-hosting, strict data residency, per-task isolation, heavy software development |
Grok Bot builds we've broken down
Each of these passed our bar: at least one thing you can actually set up.
- Routines that wake on email: webhook triggers and AgentMail (2026-09-16)
- A 5am briefing podcast built from Grok Bot, an MCP voice service and a podcast API (2026-09-03)
- Setting up an agent team: descriptions, delegation and routines (2026-08-31)
- Nine techniques: delegation prompt, shared memory, Composio, routines (2026-08-19)
- Setup: give each bot its own email instead of sharing your accounts (2026-08-17)
- Grok Bot vs Hermes and OpenClaw: teach-by-demonstration (2026-08-11)
Related on This Site
- Hermes: the open-source always-on agent, and the closest self-hosted equivalent
- OpenClaw: a self-hosted personal agent with a large skills ecosystem
- Claude Cowork: Anthropic's hosted workspace agent, a similar product category
- Cost calculator: includes xAI's Grok 4.6 API rates
- Security center: prompt injection and credential hygiene for any agent



