- 1. How is Grok Bot different from the Grok chatbot?
- 2. How do you set up Grok Bot?
- 3. What is a Grok Bot team?
- 4. How do skills and routines work?
- 5. Who can use Grok Bot right now?
- 6. When is Grok Bot the wrong tool?
- 7. Questions people ask about Grok Bot
How is Grok Bot different from the Grok chatbot?
Grok on grok.com and X is a chatbot: it answers a message and stops. Grok Bot is a named teammate with a job, a conversation, memory, and a cloud computer that keeps working after you close the laptop. xAI opened that product in beta on 11 August 2026. The unit of work is one Bot.
Grok Bot is your team of always-on agents. They have their own computer, work inside tools and apps like you do, and keep working 24/7.
In the Docs and in the Grok Bot app, a Bot = a single persistent, named agent or one AI teammate.
That computer is the whole product. A Bot can use a browser, a filesystem, a terminal, and connectors (the app currently labels those Plugins). Work can land in the actual tool. The UI still presents each Bot as a separate teammate. The isolation boundary is the account.
The computer is isolated to your account, not to an individual Bot. Treat a login or file placed on the computer as available to all of your Bots.
How do you set up Grok Bot?
Install the macOS or Windows app, sign in with an eligible Cursor or SuperGrok plan, and create one Bot with a single job. Give it a task that names the outcome, the sources, the stop line, and the deliverable. Take over the computer for passwords and codes. Save a skill only after the job works twice, then put that skill on a routine.
- Open the Grok Bot access page and install the macOS or Windows app.
- Sign in with the Cursor account that has an eligible plan.
- Create one Bot with a short name, one primary job, and a description of how it should work.
- Give it a first task that names the outcome, the sources, the constraints, and the deliverable.
- Take over the computer for passwords, passkeys, two-factor codes, and CAPTCHAs. Do not paste those into chat.
- Correct the process. Save a skill only after the job works twice. Create a routine after that.
xAI's first-Bot example is a product-performance investigator called Piper. The useful part of that prompt is the stopping rule: preserve links and screenshots, separate evidence from hypotheses, never change production. If the job is already a roster, copy an installer from this directory. Nothing here signs in for you. The click path is on How do you create a Grok Bot?. The paste path is on How do you install a Grok Bot team?.
What is a Grok Bot team?
On this directory a Grok Bot team is two to six named Bots in one group chat, with standing routines. A bot is one Bot and no group chat. On 24 August 2026 this repo listed 140 teams and 59 bots. 56 of those bots are write-ups of jobs xAI publishes. The team spec holds the file format and the published caps (50 Bots and group chats combined, 50 routines per Bot, 20 stored runs).
Connectors are account-wide. Read or draft on a team page is wording in the installer. The switch is Settings, then Plugins. We keep a connectors catalog of 342 rows, last checked 2026-08-21. Prefer a plugin when one exists. The account-wide rule is on How do Grok Bot connectors work?. The group-chat cap is on What is a Grok Bot group chat?.
How do skills and routines work?
A skill is the written method. A routine is the schedule or event that runs it. The order that holds up is one-time task, corrected task, saved skill, tested routine. Type / for a skill and @ for Bots, groups, routines, and connectors. A test run performs real work, so keep writes behind approval until you have watched it twice.
A skill is a reusable set of instructions for how to do a task.
A routine tells one Bot when to run a workflow—on a schedule or, where supported, after an event.
Teach a task can draft a skill from a browser demonstration up to ten minutes. Audio is not recorded. Treat that draft as a happy path and write the failure cases yourself. Deleting a routine has no undo. Deleting a Bot removes the routines it owned. The longer order is on How do Grok Bot skills and routines work?.
Who can use Grok Bot right now?
On 24 August 2026 the get-started page listed SuperGrok Plus, SuperGrok Heavy, Cursor Pro+, Cursor Ultra, and Cursor Teams Standard or Premium. Cursor Pro without the plus is absent from that list. Desktop clients are macOS and Windows. Mobile is iOS. That page lists plans, not a dollar figure.
An eligible plan: SuperGrok Plus, SuperGrok Heavy, Cursor Pro+, Cursor Ultra, or Cursor Teams Standard or Premium (sign in with your Cursor account)
The launch post also says enterprise users can join a waitlist. Legacy Privacy Mode is incompatible; Grok Bot requires cloud data storage. Recheck the live docs before you change a plan. Plan names without dollar figures are on Who can use Grok Bot right now?.
When is Grok Bot the wrong tool?
Use Grok Bot when the job still needs a judgment call across a few apps and can stop at a reviewable artifact. Use a script when the input, the rule, and the output are fixed. Keep sending, publishing, purchasing, deletion, and production changes on approval.
| Job | Use |
|---|---|
| Named teammate that signs into apps and keeps a computer | Grok Bot |
| Two to six Bots, one group chat, standing routines | A Grok Bot team from this directory |
| Fixed input, fixed rule, fixed output | A script or an automation tool |
| Deep work inside one repository | A coding agent in that repo |
Do not use separate Bots as a security boundary.
The combination we like: a Bot gathers evidence, a coding agent changes the repo, a person merges. Drafts first. Approval on the irreversible step. Named 1:1 pages start at Grok Bot alternatives. The shared-computer rule is on How does Grok Bot security work?.
Questions people ask about Grok Bot
Does creating a second Bot isolate logins and files?
Every Bot on an account uses the same cloud computer. Browser sessions, files, and command-line credentials are shared. A second Bot is a second conversation and job. Treat the roster as one trust zone. Put only credentials that every Bot on the account may use.
Can you run Grok Bot on Linux?
The get-started page, read on 24 August 2026, names macOS and Windows as the desktop clients and iOS for mobile. It has no Linux desktop app. The cloud computer your Bots share is a managed Linux environment, which is a different machine from the client you install.
What happens to files when you delete a Bot?
Deleting a Bot removes its profile, conversation, and routines. Files and signed-in sessions on the shared computer can remain. Sign out of sites, uninstall connectors, and remove project files under /workspace if that work should stop being available to the rest of the roster.
Does Cursor Pro include Grok Bot?
The get-started page we read on 24 August 2026 lists Cursor Pro+, Cursor Ultra, and Cursor Teams Standard or Premium. Cursor Pro without the plus is absent from that list. SuperGrok Plus and SuperGrok Heavy are listed too. Recheck the live docs before you change a plan.
More how-to and comparison pages sit under Guides. Related recipes on this directory: the SEO desk, the GEO / AEO desk, the SEO / AEO Auditor, and the On-page SEO fixer. All of them stop before publish.
Verified against docs.x.ai/grok-bot/overview, get-started, and x.ai/news/introducing-grok-bot on 2026-08-24. Team and bot counts are from this repository on the same day. Grok Bot remains a beta. Recheck the live docs before you change a plan.
