Grok Bot: AI teammates that work on their own cloud computer

Grok Bot gives you Bots you can keep around: AI teammates with names, jobs, and context that compounds over time. Each Bot works on a persistent cloud computer with a browser, filesystem, and terminal, so tasks finish in your real tools instead of as chat drafts. Get started with your first Bot, or read how teams roll it out.

You work with a Bot by messaging it. Type, dictate, or start a voice chat. Give it a task, the relevant context, and access to the tools it needs. It takes on multi-step work across apps and websites, keeps you updated in the conversation, and comes back when something needs your approval.

Grok Bot runs on macOS, Windows, Linux, iOS, and Android. On The X Subscription, it's included with Premium, Super, and Ultra, for individuals and team seats. On a legacy Cursor plan, it's included with every paid individual plan and with Cursor Teams. You can also link an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ subscription, or sign in with a seat on a self-serve Grok Business plan. See Grok Bot on The X Subscription and Plans and billing for the full matrix.

What makes Grok Bot different

• Each Bot has a computer. Your Bots run on a persistent cloud computer with a browser, filesystem, and terminal. They use connected apps where available and computer use for everything else, and work continues while your laptop is closed.
• Setup is a message, not a workflow builder. Create a Bot, describe the job, and grant access as it asks. The same Bot is reachable from the desktop app and the iPhone and Android apps.
• Bots coordinate with each other. Your Bots can run in parallel, message each other, share context in group chats, and pass ownership of a task, so you aren't the router between tools.
• Bots learn workflows from demonstration. Walk a Bot through a multi-step path once, and it can save the path as a skill and rerun it on a schedule.
• Context compounds. A named Bot keeps its memory, files, browser sessions, and preferences across sessions instead of resetting on every task.

Your Bots share one computer

All of your Bots use the same cloud computer, sharing its files, browser sessions, and app logins, which makes handoffs work without repeating setup. The computer belongs to your account, not to an individual Bot, so treat anything placed on it as available to every Bot you run; between users, isolation is strict. The computer and apps covers the full model. When you chat with a teammate's shared Bot, it usually works on your computer too.

A good first handoff

Start with a real task that spans a few tools and has a clear finish line:

This tells the Bot what to do, where to work, what context to pull in, and what finished work looks like. Review the result, correct it, and turn the stable process into a skill or routine.

Tag @bot on X

You can also start work from X. Tag @bot in a post or reply, and your main Bot picks up the post as a task while @bot confirms with a short public reply. Tagging requires an X account connected to your Grok account and is not available in every region yet. Tag @bot on X covers setup, regional availability, and why @bot might not reply.

Next steps

• Get started — Install the app, create your first Bot, and hand it a useful task.
• Troubleshooting — Fixes for sign-in, computer, plugin, routine and update problems.
• Use cases — Roles that work well, with starter prompts you can adapt.
• Work with Grok Bot — Bots, messaging, the shared computer, and skills and routines, one page each.
• Teams and Enterprise — Admin controls, identity, private networks, and the recommended rollout baseline.
• Security — Network policy, approvals and Auto Review, logging, and data handling.
• Deployment — Push the desktop app to managed devices, pick a version, and plan updates.