Grok Bot: What It Does and Who Can Use It
SpaceXAI launched Grok Bot on August 11, 2026: named AI teammates that share a persistent cloud computer, sign into your tools, and keep working after you close your laptop. It is an early beta, it comes with The X Subscription from Premium up and with paid Cursor plans, and the single most important thing to understand before you hand it real work is that every Bot you create shares one machine.
What it actually is
A Bot is a persistent, named agent. You message it the way you would text a colleague, hand it a task, and it works in the real tools rather than returning a draft in chat. SpaceXAI’s own description is that Bots “finish jobs end to end, and only come back when something needs your approval.”
Three properties make it different from asking a chatbot for help:
- It has a computer. Each Bot works on a cloud virtual machine with a browser, a filesystem, and a terminal. It can use connectors where they exist and drive the browser where they do not, which covers services with no clean API.
- It persists. Named Bots keep memory, files, browser sessions, and preferences across turns, so context compounds instead of resetting every task.
- Bots coordinate with each other. They can message each other, share context in group chats, and pass ownership, with one Bot acting as a chief of staff over specialists.
Grok Bot is not the Grok you use on grok.com, and it is not Grok Build. Those are three separate products, and the differences matter most around what can start work on its own.
One computer, shared by every Bot
This is the detail worth reading twice, because it runs against the way the product is described. “A team of teammates” implies separation. There is none.
Every Bot on your account uses the same cloud computer. Per the Grok Bot documentation, browser cookies and signed-in sessions are shared, files are visible to every Bot, and command-line credentials are shared. Each Bot gets its own screen on that machine, and SpaceXAI is explicit that the screens “are separate work surfaces, not separate security boundaries.”
The practical consequences:
| What you might assume | What actually happens |
|---|---|
| Each Bot has its own logins | Signing in for one Bot makes the session available to all of them |
| A connector belongs to one Bot | Installed connectors are account-wide |
| A sensitive file is scoped to one Bot | Files on the computer are visible to every Bot |
| Separate Bots limit blast radius | The docs say plainly: do not use separate Bots as a security boundary |
So the recruiting Bot can reach whatever the finance Bot signed into. If you want a real boundary, the unit is the user account, not the Bot.
What can start a Bot on its own
Grok Bot saves a working method as a skill and assigns it to a Bot as a routine. Routines run while your laptop is closed, and they are capped: a Bot can own up to 50, and the app keeps the 20 most recent run records for each one. If you stay away long enough, Grok Bot may ask whether to keep routines running and pause them if nothing answers.
On what wakes a routine up:
A Grok Bot routine starts on a clock or on one of the events Cursor documents: Slack, GitHub, Linear, Sentry, PagerDuty, a webhook, or mail to the Bot's own address. That is a developer's list. Your inbox, your calendar, your CRM and your billing system aren't on it. Carly watches all of the systems the work actually starts in.
This is a genuine step past assistants that can only work on a timer, and it is worth being precise about rather than dismissive. It is also narrow in a specific direction. Slack and GitHub are well covered. The events most businesses actually run on, a deal stage changing, an invoice aging past due, a form arriving, a file landing in shared storage, are not on the documented list, and the docs hedge the whole capability with “where supported.”
Who can actually get it
Access runs through a Cursor account, which follows from SpaceX’s acquisition of Cursor’s parent company Anysphere, announced in June 2026. Grok Bot uses Cursor authentication, inherits your Cursor team’s MCP policy, and is administered from the Cursor dashboard.
The plans changed again in October. Grok Bot is now sold through The X Subscription, where it is included on Premium, Super and Ultra, for individuals and team seats; Plus and Free don’t include it. Cursor’s Pro, Pro+, Ultra and self-serve Teams plans are now called legacy plans, and they still include it, as does linking an individual SuperGrok or X Premium+ subscription. Enterprise access goes through a Cursor account executive.
What replaced the access question is the usage one. Each plan carries a weekly Grok Bot allowance, and the reports from the first fortnight are consistent: heavy users burn it in a day or two, including on Ultra at $200 a month. Past the allowance, usage bills from the shared on-demand pool with no confirmation step, and the dashboard meter does not break spend down by product, so Grok Bot spend is hard to separate from everything else. Cursor staff call the spillover intended behavior and point people at a spend cap in the billing dashboard, which you can set to zero to stop it outright. One user moved to the API instead and spent $27 in ten minutes. Set the cap before the first routine runs, not after.
Platform support has widened since launch. As of September 29, 2026 the desktop app runs on macOS (Apple silicon and Intel), Windows (x64 and Arm64) and Linux (x64 and Arm64), and the companion app runs on iPhone and iPad (iOS/iPadOS 18 or later) and Android 9 or later. Legacy Privacy Mode blocks Grok Bot entirely because the product requires cloud data storage.
Where Carly fits
Carly is built around the part Grok Bot documents least: work that starts because something happened, in the apps a business actually runs on. Carly watches your calendar and inboxes and acts on what arrives, across Gmail and Outlook together, without a Slack or GitHub notification standing in as the trigger.
Carly connects to thousands of apps. Pricing is free Zapier-style workflows, with AI agents from $35/month, and it runs on the web rather than requiring a desktop app on a supported OS.
Putting Carly inside Grok Bot
Separation is an argument for how accounts should be held, not an argument for picking one product. Grok Bot keeps the chat, and Carly sits inside it as a plugin:
- In a chat with your Bot, send this message:
- Confirm when the Bot reads back the name and address.
- Click Authorize on the card it posts, then sign in to Carly.
For calls and texts from your business number, add Carly Teams the same way: see can Grok Bot make phone calls.
Carly’s tools are there from your next message. A Bot can then hand Carly the calendar and mailbox work, with Carly holding those accounts, instead of spreading them across account-wide plugins and a browser session that every other Bot on the machine can see. It also gets Carly’s ready-made workflows, so you skip the rounds of prompting, permission changes and token refreshes it takes to build the same thing inside Grok Bot by hand.
Grok Bot has no settings form for adding a server by its address, so the chat message is the way in; Connect apps in the sidebar only lists marketplace plugins. Grok Bot inherits your Cursor team’s connector policy, so on a team plan an admin can block servers that aren’t approved.
Frequently asked questions
Is Grok Bot the same as Grok?
No. Grok on grok.com is the assistant, with its own Automations feature for scheduled and email-triggered tasks. Grok Bot is a separate desktop and iOS app for persistent AI teammates on a cloud computer. Grok Build is a third product, for coding.
Do Grok Bots have separate logins from each other?
No. All of your Bots share one cloud computer, including its browser sessions, files, and command-line credentials. SpaceXAI advises against treating separate Bots as a security boundary.
Can Grok Bot work while my laptop is closed?
Yes. Work runs on the cloud computer, so closing the app, the laptop, or your phone does not stop a background turn or a routine.
What does Grok Bot cost?
It is bundled rather than sold separately. It comes with the Premium, Super and Ultra tiers of The X Subscription, but not Plus or Free, and with Cursor’s legacy paid plans, Pro, Pro+, Ultra and self-serve Teams. You can also link an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription. Each carries a weekly usage allowance shared with Cursor and the Grok apps, and anything past that is paid from prepaid credit or on-demand usage, depending on the plan, unless you set a limit.
Which platforms does Grok Bot support?
Desktop: macOS (Apple silicon and Intel), Windows (x64 and Arm64) and Linux (x64 and Arm64). Mobile: iPhone and iPad on iOS/iPadOS 18 or later, and Android 9 or later. Linux, Android and iPad were added after the August launch.
Can I add my own MCP server to Grok Bot?
Yes, by asking in chat. There is no settings form for it: send your Bot “Add this MCP server:” followed by the address, confirm the details it reads back, and authorize the card it posts. For Carly the address is https://carlyassistant.com/mcp. The server has to be reachable on the public internet, and on a team plan your Cursor connector policy can block servers an admin hasn’t approved.
Can Grok Bot use apps that have no API?
Yes. Because each Bot drives a real browser on its computer, it can work in sites and tools that expose no clean API or MCP server. A site can still block automation or demand a CAPTCHA, in which case the Bot hands control back to you.
Related: Grok alternatives · Connect multiple Gmail accounts to Grok Bot · Connect multiple Outlook accounts to Grok Bot · Best AI agents for productivity
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
