What is Grok Bot? An AI teammate with its own computer

Most AI assistants answer a message and stop. Grok Bot is built around a different idea: a Bot is a teammate with a name, a job and a computer of its own, so the work finishes in your real tools instead of ending as a draft in a chat window.

What Grok Bot actually is

The official Grok Bot 101 guide puts it more bluntly: “Grok Bot is an agent with a computer.” The computer lives in the cloud. It has a desktop, a filesystem, a terminal and apps, and you can open a Bot's window and use that machine like a remote desktop.

Two things people mix up:

• It is not the Grok chat app. The FAQ is explicit: Grok and Grok Bot are two different apps, and Grok Bot signs in with your Cursor account. A paywall or a “Weekly SuperGrok Limit” in the Grok app has nothing to do with Grok Bot.
• It runs on Cursor's infrastructure. The computers Bots work on run in Cursor's cloud, and Grok Bot uses Cursor authentication and account data settings (FAQ).

How you work with a Bot

You talk to it. The Grok Bot 101 guide lists three ways a Bot gets work:

1. Chat. You send it a message, dictate one, or start a voice chat.
2. Routines and triggers. A Bot can run on a schedule or start when something happens in another app, such as a Slack message or a GitHub event. See skills vs routines.
3. Other Bots. Bots can message each other, work in group chats and hand work off.

You can also hand a post to your Bot by tagging @bot on X, though the docs note this isn't available in every region yet.

When a Bot reaches something only you can do, such as a CAPTCHA, a passkey or a single sign-on step, it hands you the computer. For passwords it uses a login saved in Vault or shows you a Secure Form, so the Bot never sees the value (Get started).

What a Bot is made of

• A job. Each Bot should own one area of work. The docs recommend a separate Bot when the work has a distinct goal, toolset, working style, approval boundary or schedule.
• Memory. A Bot keeps stable preferences, role context and summaries of prior work. Conversations and learned context stay separate per Bot, except a few facts about you (like your name and time zone) that all your Bots share.
• Skills. Reusable instructions for how to do a task.
• Routines. When a Bot runs a workflow on its own.
• Connected apps. Structured connections to services like Gmail, Notion or Slack, available to every Bot on your account.
• Approval rules. Auto Review checks each action before it runs and asks you when needed. See Auto Review and approval cards.

The one thing to understand first: the shared computer

This is what makes handoffs between Bots easy, and it's also the most common surprise. Sign in to a site for one Bot and every other Bot can reach it. We wrote a full guide on what the shared computer means for logins and context.

Where it runs and what it costs

The desktop app runs on macOS (Apple silicon and Intel), Windows (x64 and Arm64) and Linux (x64 and Arm64). The phone app runs on iPhone with iOS 18 or later and Android 9 or later, and connects to the same Bots, chats, routines and computer (FAQ).

On The X Subscription, Grok Bot is included with Premium, Super and Ultra and draws from the same weekly usage pool as Cursor and the Grok apps. Plus and Free don't include it. Legacy Cursor plans and some linked Grok subscriptions also give access. The details, with sources, are in which plan you need and on our plans and limits page.

There is no model picker: Grok Bot chooses the model for each task, and the choice can differ from one request to the next (FAQ).

When Grok Bot is the wrong tool

It is still a beta product. According to Flavio Copes's deep dive, the beta launched on August 11, 2026, and access rules have moved quickly since. That's worth remembering before you build anything critical on it.

Where to go next

Start with one narrow job you already know how to do by hand. Read how to write a brief a Bot can finish, or skip the setup and add a ready-made Bot from a share link. Browse the directory to see what others have built, with each bot's permission level shown up front.