Skip to main content

Command Palette

Search for a command to run...

Grok Bot

Grok Bot

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. 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.

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 plugins 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 iOS.
  • 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.

A good first handoff

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

Pull this week's pipeline review list from our CRM. Skip anyone already in an active sequence. Research the top five accounts across the web and Slack, pull the right contacts, draft outreach in my voice, and leave me drafts to approve by tomorrow morning.

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.

FAQ

Yes. Work runs on the cloud computer. Closing the app, your laptop, or your phone doesn't stop a background turn or a routine.

Yes. Bots can reason, use plugins, work with files, and coordinate in parallel. Each Bot gets its own screen on the shared computer, and one Bot runs one computer-use task on its screen at a time.

Stable preferences, role context, and summaries of prior work. Conversations and learned context stay separate per Bot, while shared files, browser sessions, and direct handoffs move context between them. For consequential decisions, ask the Bot to check the current source instead of relying on memory.

Bots can use many browser-based tools, including services without a plugin. A site can still block automation, expire a session, or require a human step. The Bot hands those steps to you rather than working around them.

The desktop app runs on macOS (Apple silicon and Intel) and Windows (x64 and Arm64), and the mobile app runs on iPhone. There is no Linux desktop app, and the computers Bots work on run in Cursor's cloud.

Access is included with every paid individual Cursor plan and with the Cursor Teams plan, or through an individual SuperGrok account link. Usage resets weekly. See Plans and billing.

Next steps

Get started

Install the app, create your first Bot, and hand it a useful task.

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 in one place.

Teams and Enterprise

The security model, approvals and Auto Review, admin controls, and the recommended rollout baseline.