Everybody keeps asking me the same question this month: what is Grok Bot, and should I care? I’ll be upfront that Miami Mike has not run it yet. It launched on August 11, it is still in beta, and I have spent the last two weeks reading the docs, the pricing pages, and the launch coverage instead of paying for a subscription I did not need. This is the post I wish someone had handed me before the third person brought it up at lunch.
Quick answer to what is Grok Bot: it is a team of always on AI agents from SpaceXAI, the merged xAI and SpaceX entity that is also buying Cursor. Each Bot you create gets access to a persistent cloud computer with a browser, a file system, and a terminal. It signs into your real apps, works through multi step jobs while your laptop is closed, and comes back only when something needs your approval.
How does Grok Bot work
You download a desktop app, create a Bot, give it a name and a role, and message it the way you would text a coworker. That is the whole onboarding. There is no workflow builder and no flowchart to draw first. The Bot reads your message, opens the tools it needs on its cloud machine, does the work inside those tools, and posts updates back in the thread.
The part that makes this different from a chatbot is where the output lands. A normal assistant drafts an email in the chat window and you copy it out. Grok Bot signs into Gmail and leaves the draft sitting in your drafts folder. It updates the CRM record instead of describing the update. That is the pitch, and it is a good one, because the gap between 90 percent done and actually done is where most AI tools lose people.
The launch announcement says the product started as an internal prototype and spread across the company before it shipped. The examples they give are a sales Bot updating the CRM from call transcripts, an ops Bot processing invoices out of Gmail, and an engineering Bot reproducing a bug and handing the fix to a second Bot. Every one of those is a job a person does today with a browser and a login.
Grok Bot features that actually matter
Strip away the marketing and there are five things the product does that the docs back up.
- A cloud computer that keeps running after you close the app. The work does not depend on your laptop being awake.
- Computer use for apps with no API. If a site has a connector or an MCP server, the Bot uses that. If it does not, the Bot clicks through the browser like a person would.
- Multiple Bots working in parallel. You can put two to six Bots in a group chat, and they message each other, hand off ownership, and only pull you in for judgment calls.
- Skills and routines. A process that worked once can be saved as a skill, and a skill can be scheduled as a routine that runs on its own.
- Teach a task. Where the feature has rolled out, you record yourself doing a browser workflow once, capped at ten minutes, and the Bot turns it into a draft skill you can review.
Memory works per Bot. Each one keeps its own role, preferences, and summaries of prior work. That is why the product pushes you toward a roster of specialists, one for inbox, one for outbound, one for expenses, with a chief of staff Bot on top. The docs also tell you to have the Bot check the live source before an important decision rather than trusting what it remembers, which is a refreshingly honest thing to put in your own documentation.
Platform support at launch is macOS, Windows, and iPhone on iOS 18 or later. No Linux desktop, no Android, no iPad yet, per the official FAQ. Some early coverage listed Linux as supported. The docs say otherwise, and I trust the docs.
How much does Grok Bot cost
There is no Grok Bot subscription. You cannot buy it on its own. Access comes bundled with a plan you buy for something else, and the list of eligible plans has already changed once since launch.
As of late August, the Cursor billing page lists these routes in: Cursor Pro+, Cursor Ultra, any self serve Cursor Teams seat, or a linked individual SuperGrok Plus or SuperGrok Heavy account. Cursor Pro and basic SuperGrok do not include it. The published prices I could verify across the official pages and the sites tracking them are roughly $60 a month for Cursor Pro+, $200 for Cursor Ultra, $40 to $120 per seat for Cursor Teams depending on tier, $100 for SuperGrok Plus, and about $300 for SuperGrok Heavy. Confirm before you buy. These moved between August 11 and August 21 and will move again.
The price of the plan is the easy part. Each plan comes with a weekly Grok Bot usage allowance that resets every week, and when you burn through it, extra usage continues on demand, billed from model and token cost. I could not find a published Grok Bot specific spend cap, and there is no model picker, so you cannot route a cheap task to a cheap model to save money. If you have read my piece on AI inference costs you already know where this goes. An agent that runs for hours in a browser eats tokens in a way a chat session never does.
The Grok Bot free trial is a credit, not a period
The trial is a usage credit with a seven day window on top. It is measured in agent steps and tokens, not messages. Cursor’s own help page says a single large run can consume most or all of it, and used credit is not restored. So do not kick off “clean up my entire CRM” as your first test. Scope the first task small, check the usage meter on the plan screen, and scale up from there.
Grok Bot vs Hermes Agent, OpenClaw, and Buzz
The idea of an agent with its own computer that you message from your phone is not new. Three open source projects got there first, and each of them is a real alternative depending on what you actually want.
| Product | Who makes it | What it is | Where it runs | Model choice | Price |
|---|---|---|---|---|---|
| Grok Bot | SpaceXAI with Cursor | Managed team of always on agents | SpaceXAI cloud VM | Grok only, no picker | Bundled with Cursor or SuperGrok plans, $60 to $300 a month |
| Hermes Agent | Nous Research | Self hosted agent with memory and skills | Your server, VPS, or laptop | Any provider or local model | Free, MIT license, you pay for tokens |
| OpenClaw | Open source foundation, started by Peter Steinberger | Local agent runtime tied to messaging apps | Your machine | Any provider | Free, MIT license, you pay for tokens |
| Buzz | Block | Workspace where agents are members | Self hosted or Block hosted | Bring your own agent and model | Free, Apache 2.0 |
Grok Bot vs Hermes Agent
Hermes Agent came out of Nous Research in February and crossed 100,000 GitHub stars in a few months. It is the closest thing to Grok Bot in spirit. It keeps memory across sessions, writes its own skills after it finishes a hard task, runs scheduled jobs through a built in cron system, and reaches you through Telegram, Discord, Slack, WhatsApp, Signal, and a dozen other channels. The difference is ownership. Hermes runs on hardware you control and talks to whatever model you point it at, including a local one. If you have a box like the one I describe in my DGX Spark home lab post, you can run Hermes on it with zero data leaving the building. Grok Bot cannot do that and never will.
The trade is setup time. Hermes installs with one command, but wiring up messaging gateways, skills, and a proper security posture is a weekend project at minimum, and a multi week project if you want it production grade. Grok Bot is a download and a login.
Grok Bot vs OpenClaw
OpenClaw started life in November 2025 as Clawdbot, got renamed twice over trademark issues, and became the fastest growing repo on GitHub for a stretch. It runs as a single process on your own machine, connects to more than twenty messaging channels, and executes shell commands, file operations, and browser tasks. Its creator joined OpenAI in February and the project moved to an independent foundation. It is free and MIT licensed.
OpenClaw is the one I would be most careful with. It got popular faster than its security matured, and there were enough incidents in the spring that Chinese authorities barred state enterprises from running it on office machines. The project has shipped fixes through 2026, but the broad system access that makes it useful is the same thing that makes it dangerous on a laptop that also holds your client files. Grok Bot has the opposite problem, which I get to below. Your risk does not go away, it just moves.
Grok Bot vs Buzz
Buzz is not an agent. It is a Slack style workspace from Block, Jack Dorsey’s company, released July 21 under an Apache 2.0 license and built on the Nostr protocol. Agents join channels as members with their own cryptographic identity and their own permissions, and you bring whatever agent and model you want behind them. The Block announcement names Claude Code, Codex, and goose as examples. You can self host it or use Block’s hosted version.
So Buzz competes with the group chat feature in Grok Bot more than with Grok Bot itself. Grok Bot gives you a closed room where only Grok powered Bots talk to each other. Buzz gives you an open room where a Hermes agent, a Claude Code agent, and your human team all sit in the same thread with a signed audit log. Block calls it early stage and it is pre 1.0, so I would not move a team onto it yet, but if you are already thinking about a multi model AI strategy it is the one to watch.
Grok Bot security risks nobody put in the launch video
A lot of the launch coverage said each Bot gets its own computer. That is wrong, and the correction matters. The official docs say all of your Bots share one cloud computer assigned to your account. They share its files, its browser sessions, and its command line credentials. Each Bot gets its own screen, so they can work in parallel, but xAI says in plain language not to treat separate Bots as a security boundary.
Think through what that means. You log your outbound Bot into LinkedIn and Gmail. You log your expenses Bot into the company card portal. Every Bot on your account can now reach both. Deleting a Bot removes its profile and routines but leaves the files and logins on the shared machine. The docs are honest about this and give you a cleanup checklist, sign out of sites, revoke connectors, wipe the workspace folder, but it is on you to run it.
The approval system is decent. You can write narrow rules that force a stop before sending external email, publishing, purchasing, deleting, or touching production. Passwords, two factor codes, and CAPTCHAs are supposed to hand control back to you rather than get typed by the Bot. Local computer execution defaults to ask every time, and I would set it to never allowed until you have a specific reason. The Auto Review that evaluates actions is model based, and the docs themselves say it should complement least privilege rather than replace it.
Data handling runs through Cursor’s account and privacy settings, not Grok’s. Legacy Privacy Mode is not supported because the product requires cloud storage. Training opt out follows your Cursor settings. If your work involves client data with any compliance attached, read Cursor’s security page before you sign anything in.
What is Grok Bot worth to a small business right now
So, what is Grok Bot actually good for? Here is where I land after two weeks of reading and zero hours of running it. Grok Bot is a prosumer product today. Enterprise access is a waitlist through a Cursor account team, SuperGrok Team and Enterprise accounts cannot even link to it, and admin controls vary by organization. That is why you are hearing about it from solo operators, sales reps, and founders, and not from anyone with a procurement department. My own enterprise clients are not asking about it yet, and they should not be.
For a five person shop in Doral that already pays for Cursor, it is close to free to try, and the sales outbound use case is real. Research accounts overnight, draft follow ups in your voice, leave them in drafts for you to approve in the morning. That is a workflow I would pilot. I would not point it at anything that can move money or delete records until I had watched it run for a month.
For anyone who cares where their data lives, or who wants to pick their own model, Hermes on your own hardware gets you most of the same capability with none of the shared computer problem. It costs you a weekend instead of a subscription.
