2026-08-27 · Guide
Grok Bot vs Grok the Chatbot: Teammate Product vs Chat Product
People install Grok Bot to get a better Grok chat, then discover Tuesday's inbox still has no watcher.
That is the grok bot vs grok mix-up in one night. People treat installing Grok Bot as getting a better Grok chat. It is not. grok.com and the Grok app are conversation. You type, you get a reply, the thread is the product. Grok Bot is named bots, routines, plugins, approvals, and one shared persistent cloud computer assigned to your user account. Same family name. Different job. Different blast radius.
Grok Bot launched in beta on 11 August 2026. Eligibility widened on 21 August 2026. Search collapses the two products because both say Grok. Your credit card does not. Confirm chat SKUs on x.ai the day you buy. Bot SKUs below were rechecked 23 September 2026. For a definition without a comparison, use What Is a Grok Bot?. This page is only the split, with Grok Build parked in a third column so it does not steal the argument.
Stop treating a Grok Bot install as an upgrade to grok.com
The upgrade story is seductive. You already talk to Grok. Someone on X says Grok Bot is Grok with hands. You pay more and expect the same window with a longer memory and a Gmail login.
What you actually bought, if the plan includes it, is a roster on a managed Linux VM that belongs to the account, not to the bot. Each bot has a screen. The screen is a work surface, not a private computer. Chat did not grow a desk. You entered a product whose failure mode is a signed-in mailbox sitting next to a research session, not a weak paragraph in a thread.
If grok.com felt slow or forgetful, fix that inside the chat product, or leave. Do not pay for Grok Bot as a personality upgrade. Pay for it when a job has to exist next Tuesday with the same stop line, on a computer that stays up after the laptop lid closes.
Keep grok.com and the Grok app as conversation, not as a desk
This article will not print a Grok chat feature list. Those pages move. Voice, apps, memory, image tools: confirm on x.ai and grok.com. Inventing that list would go stale and would train you to compare the wrong objects.
A chat product answers you. The unit of work is a turn. If you close the tab, the conversation is a log. It is not a coworker with a name, a routine cap, and a machine that still has last week's file. You can paste yesterday's mail and ask for drafts. Useful. Still conversation. The product does not become Inbox Triage because you wrote "every morning" in a prompt. Prompts are not schedules. Threads are not screens.
Treat chat as the place you think with Grok. Treat Grok Bot as the place you staff Grok. If you only need the first, stay on grok.com and never connect a mailbox to a cloud VM.
Staff named bots with routines, plugins, and a stop line
A Grok bot is a named role. Inbox Triage classifies mail, drafts a few replies, and never sends. Chief of Staff Briefing is a morning packet that never moves a calendar event. Lead Scout researches and ranks and never contacts anyone. A teammate product needs a stop verb. Chat does not become that verb because you typed "never send" once.
Routines attach a workflow to one bot. Maximum 50 per bot. The app keeps the 20 most recent run records per routine. Deleting the bot deletes its routines. Nothing is team-level. Plugins reach mail and the rest of the desk. This page will not print a plugin count. Connect the minimum. Prefer read-only where the job only reads. Approvals gate a proposed action. They do not reverse work already completed. Full model: approvals, rules, reversibility.
The computer is one persistent cloud machine per user account. Every bot shares cookies, sessions, files, and CLI credentials. Each bot gets a screen. Docs are blunt: do not use separate bots as a security boundary. Deleting a bot does not remove shared files or browser sessions. Isolation lives in One Computer, Many Screens, not in a second name.
Supported clients: macOS (Apple silicon and Intel), Windows (x64 and Arm64), iPhone on iOS 18 or later. There are Linux desktop and Android apps as of September 2026, and the iOS app also runs on iPad (iPadOS 18 or later). The computer is a managed Linux VM, which is not a Linux desktop client. From the phone app (iPhone or Android) you can approve steps and pause or resume a routine, but not edit it. Editing and testing a routine still need the desktop app; the phone can now show run history and delete a routine. No model picker for members or admins. Do not assert that Grok Bot runs grok-4.6. The Bot serving set is unpublished. No Grok Bot-specific spend cap: weekly allowance, then on-demand. No published dollar figure for the allowance. Never invent one. See Grok Bot cost.
Leave Grok Build in the third column so the names stop collapsing
Search will also hand you Grok Build: a coding CLI, skills, local files. Third object. Not a better chat. Not Grok Bot. Grok Build went open source on 16 July 2026. Claude Code / SKILL.md / CLAUDE.md compatibility is Grok Build, never Grok Bot. Pasting a SKILL.md into a Bot charter will not constrain tools.
This page will not remake that comparison. Read Grok Bot vs Grok Build when the question is CLI versus teammate. Stay here when the question is chat window versus named bot.
| Object | Kind | What you do with it | What you must not infer |
|---|---|---|---|
| grok.com / Grok app | Chat product | Talk, draft in a thread, think with Grok | That a prompt is a routine, or that the thread is a shared computer |
| Grok Bot | Teammate product | Name bots, connect plugins, assign routines, approve | That you bought a better chat, or that each bot has its own VM |
| Grok Build | Coding CLI | Work in a repo with skills on a machine you control | That Bot will honour SKILL.md, or that chat grew a terminal |
Three rows. Three docs trees. One brand. If you cannot point at which row is on screen, stop connecting Gmail.
Buy Grok Bot on Cursor and SuperGrok tiers that actually include it
Access is where grok bot vs grok becomes a billing error. Grok Bot is bundled. No standalone Bot SKU in the docs we checked. Eligible: every paid Cursor plan (Pro, Pro+, Ultra), Cursor Teams, and a linked individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription, plus a one-time trial. Eligibility first widened on 21 August 2026.
The traps are Cursor Hobby, SuperGrok Lite, and an individual SuperGrok nobody linked. People already paying for "Grok" or for Cursor assume Bot is in the bundle. On Hobby and Lite it is not. On SuperGrok it arrives only after you link it from the Grok Bot plan screen. Cheapest paid path, checked 23 September 2026: Cursor Pro at 20 dollars a month. If both a Cursor and a SuperGrok subscription are present, Grok Bot uses whichever has more usage. A one-time trial is not a forever SKU. See Grok Bot free trial and Cursor account explained.
| What you already pay | Grok Bot included? | What people assume |
|---|---|---|
| grok.com / Grok app (confirm the chat SKU on x.ai) | Chat access is not proof of Bot | "I have Grok, so I have Grok Bot" |
| SuperGrok (individual) | Yes, by linking | Link it from the Grok Bot plan screen; it grants usage and is not a Cursor plan |
| SuperGrok Plus | Yes, by linking | Correct for Bot, still not a chat upgrade |
| SuperGrok Heavy | Eligible. Confirm the live price on x.ai | Do not trust a viral Heavy figure |
| Cursor Hobby | No | Free Cursor unlocked the teammate |
| Cursor Pro at 20 dollars a month | Yes. Cheapest paid path | Often missed because it sounds too cheap |
| Cursor Pro+ at 60 dollars a month | Yes, with more weekly usage | Bought for usage, not for a different bot |
| Cursor Ultra, any seat on a self-serve Cursor Teams plan | Yes | Teams seats are easy to miss |
| One-time trial | Eligible for individuals | That trial leftovers isolate a mailbox |
Hedge Grok chat pricing on x.ai instead of copying a screenshot
Third-party roundups love a grid with a winner in bold. The Bot column can be sourced. The chat column goes stale, and half the grids mix API token prices, SuperGrok, and X Premium into one "Grok" cell. Do not budget Grok chat from this page. Open x.ai, write down the chat SKU, then separately check whether it is also Bot-eligible. SuperGrok Lite is the documented Grok-branded plan that does not include Bot, and SuperGrok Team and Enterprise cannot link. Other chat SKUs: confirm.
The same hedge applies to clients. grok.com is a site. There is a Grok app. What phones, what desktops, what happens on X: confirm live. Do not copy Bot's platform list onto chat, and do not copy chat's web URL onto Bot and expect a browser client. Bot facts above were rechecked 23 September 2026. A pricing tweet from May is not a source.
Ask chat to watch the inbox, then watch the request fail as a standing job
Monday, 07:20. You open grok.com or the Grok app. You paste: "Watch my inbox. Flag anything that needs me. Draft replies in my voice. Do this every weekday."
The model answers well. It explains labels. It offers to draft if you paste threads. At 07:21 you still have an inbox that only you are watching. At 07:30 on Tuesday, nobody ran. You are the scheduler. Watching an inbox is a standing job with logins, a clock, a stop line, and a desk. Conversation is the wrong object.
| When | grok.com / Grok app | Named Grok Bot with Inbox Triage |
|---|---|---|
| Monday 07:20 | You ask. It replies. You still paste mail by hand | You name the bot, paste a charter, connect mail narrowly |
| Monday 18:00 | Thread buried. Nothing ran. Nothing was scheduled | A routine fired. Drafts wait. Send stays off if the stop line held |
| Tuesday 07:30 | You forgot, or you pasted a new dump and Monday's instructions drifted | Same bot, same labels, same never-send. App keeps 20 run records per routine |
| Day 8 | You rewrite the prompt. "Just send the obvious ones" creeps in | Charter still forbids send. Approvals still sit in front of any proposed send |
| Day 30 | Strong advice in old threads. No coworker | Named bot, a month of files, and a mailbox session other bots on the account can reach |
Day 8 is the fork. Chat has no standing stop line unless you retype it. Bot has a charter, and still has a shared computer. Pick the failure you can supervise. A one-off mailbox export can stay in chat. Weekday mail for the rest of the year wants Inbox Triage, not a better paragraph.
Paste Inbox Triage into Grok Bot and keep send off the desk
Paste a charter into the named bot before you complete the Gmail consent screen. The boundary is the product. Inbox Triage never sends. Every draft waits.
You are Inbox Triage.
Every weekday at 07:30 in Europe/London:
Scan mail since the last run.
Classify each message as needs-reply, waiting-on-others,
newsletter, receipt, or noise. Label it. Archive noise and receipts.
For the three highest-priority needs-reply threads, write a draft
in my voice: short sentences, answer first, no filler.
Write a summary I will actually read: counts per label, the three
drafts with one-line context, and anything older than three days
still unanswered.
WHERE YOU STOP
Never send. Drafts stay drafts until I approve each one.
Never unsubscribe, delete, or forward.
If a thread involves money, legal, or HR, do not draft. Flag it needs-me.
If you are unsure, prefer needs-reply over archive.
If login failed or the mailbox is empty in a way you cannot explain,
write BLOCKED and stop. Do not invent a quiet morning.
IF YOU ARE UNSURE
Ask me. Waiting is correct. Sending is not.
That block is pointless in a grok.com thread you will not reopen at 07:30. It is the whole point on Grok Bot. Pair it with a routine on this bot only. A second copy "for redundancy" shares the computer. You doubled the hands on one mailbox, not the safety. Gmail scopes: Grok Bot and Gmail. Clock shape: Grok Bot scheduling. Mail Cleanup Assistant is cleanup, not daily triage. Do not run both against the same send-capable grant until you can say which bot may propose which verb.
Measure blast radius on the shared computer, not on a chat thread
Chat blast radius is mostly the text you pasted and whatever the chat product retains. Confirm retention on x.ai. Do not copy Bot's VM model onto grok.com.
Grok Bot blast radius is the desk. One computer. Cookies, sessions, files, CLI credentials. A Lead Scout that may only research still sits on the same machine as Inbox Triage. Naming does not partition credentials. Screens are not security boundaries. Deleting Inbox Triage does not log the browser out. You rotate the session. Delete removes the bot and its routines. It does not unsay the login. Hosted MCP sign-in tokens stay with Cursor's backend, not on the computer. That does not make Gmail cookies private to one screen.
Chat leakage is a transcript problem. Bot leakage is a computer problem. Installing Bot because you wanted a smarter transcript gives you the larger radius for free. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording. Prefer draft-only. See Least privilege bots.
Fire a routine on one bot and accept the twenty-run history cap
"Watch my inbox" in chat is a wish for a clock. Grok Bot's clock is a routine assigned to one bot, not to the account, not to the team. Max 50 per bot. The app keeps 20 most recent run records per routine. That history is how you debug a silent Tuesday. It is not a year of logs. Copy summaries somewhere you own if you need a paper trail.
Deleting the bot deletes the routines. Files on the shared computer may still be there. Operators think delete is cleanup and think the schedule will survive a rebuild. Opposite on both counts. Repeating a prompt in grok.com is not a routine. Neither is a calendar reminder you set for yourself.
Teach-by-demonstration exists on Bot: up to ten minutes, no microphone audio, draft skill, browser workflows only, unavailable on iPhone. It is not how grok.com learns your inbox.
Match the search sentence to the product before you connect a mailbox
Most grok bot vs grok confusion is a sentence with the wrong noun.
| Sentence you typed | Product that matches | Mistake if you buy the other |
|---|---|---|
| I want a better Grok chat | grok.com / Grok app (confirm SKU on x.ai) | You paid for a VM you will not staff |
| Watch my inbox every weekday and never send | Grok Bot plus Inbox Triage | You asked a thread to be an employee |
| Reuse my Claude Code skills | Grok Build | You dropped SKILL.md on a Bot |
| Pin grok-4.6 | API or Build. Not a Bot setting | You planned a picker Bot docs refuse |
| Keep going after I shut the laptop | Grok Bot's cloud computer | You expected a website tab to be a desk |
| Talk through a strategy for an hour | Chat product | You created a bot for a conversation you will not repeat |
| Weekly brief that diffs last week's file | Grok Bot (Chief of Staff Briefing) | You hoped a thread would open last week's file |
Fail the noun test and every later decision is theatre. Connect mail only after the row is Grok Bot, the charter has WHERE YOU STOP, and you accept that every other bot on the account shares the session.
If you live on a Linux laptop, Grok Bot has a Linux desktop app as of September 2026 (.deb, .rpm or AppImage). Chat in a browser may still work. Confirm. Any eligible plan unlocks the Linux Bot client; no tier is Linux-only. Supported platforms is the Bot client list. This page will not invent chat clients to match it.
Concede the case where a chat window is the whole job
The strongest argument against this article is that you already open Grok every morning, you already paste the messy question, and a named bot is ceremony around a conversation you actually have. That case wins more often than Bot marketing wants it to.
It wins when the work is thinking or one-off: a tradeoff, a rewritten email, a page you will not revisit. Those jobs want turns, not a VM. Staffing Inbox Triage for a mailbox you check twice a year is how you leave a Gmail grant on a shared machine for no cadence. It wins on friction: opening grok.com is cheaper in attention than naming a bot and connecting plugins. A chat you use beats a roster you meant to staff. It wins on price if your current chat SKU is enough. SuperGrok does not bring Bot until you link it, and the link is permanent. Stay there if chat is the job. Buying Plus or Pro+ "so Grok gets better" is the upgrade fallacy this page is for.
It loses when the name has to survive you forgetting. Weekday mail, daily lead ranking, a Monday brief that must open last week's file: those jobs fail as repeated chats because you are the memory and the stop line. The prompt drifts. "Just send the obvious ones" appears. A charter is a written refusal that does not depend on you retyping it before coffee. It also loses on desk stalls: a portal, 2FA, a four-minute export, a labelled archive that must still exist in October. Conversation cannot hold that stall. A persistent computer can, and that capability is the blast radius.
If the objection is "I will just remember to ask grok.com every morning," keep a two-week tally. If the tally has holes, you wanted a routine on a bot, not more sincerity.
Prove the split with checks that fail if you opened the wrong Grok
Do not trust the feeling that you are in "Grok." Point at the UI.
| Check | Grok Bot | Chat product | Fail meaning |
|---|---|---|---|
| Named roster | Yes | Threads, not bots | You are staffing a conversation |
| Routine on one bot (cap 50) | Yes | No | Your "every morning" is still you |
| Agent computer / screens | Yes. One computer, many screens | No | You expected a desk inside a tab |
| SKILL.md changes behaviour | Not a Bot feature | Not a chat feature either | You wanted Grok Build |
| Model picker | No, for members or admins | Confirm on x.ai | You planned to pin grok-4.6 on Bot |
| Linux desktop client | No | Confirm chat on the web | You bought Bot for a machine it does not support |
| iPhone can edit a routine | No. Pause, resume and approve only | Confirm the Grok app on x.ai | You thought phone Bot was the full product |
| Delete worker, sessions vanish | No | A deleted thread is not a VM logout | You used delete as cleanup |
If you cannot fail a row, you cannot risk-assess the product. A mailbox connected on a pass that should have failed is the incident. Run the table before the consent screen, not after the first draft goes out. Teammate pre-flight: Grok Bot safety checklist. Chat-side privacy toggles belong on x.ai. Do not mix the checklists.
Keep both products when talk and standing work arrive in the same week
You can keep grok.com and Grok Bot. Stop using one object for the other object's job.
Keep chat for talk: drafts you will paste yourself, questions that end when the answer lands, one-off rewrites. Confirm what that product stores. Do not ask it to watch a mailbox as a standing employee. Keep Grok Bot for standing work: named jobs, routines, plugins, last week's file. Staff few bots. Connect few accounts. Write the verb that must never happen. Every bot shares the computer. Overflow has no per-bot cap, only the account's On-demand monthly limit. Linux and Android are Bot clients as of September 2026, and the iOS app also runs on iPad. Keep Grok Build in the repo if you want a CLI. Do not put mail on that story. See Grok Bot vs Grok Build.
A coherent week: chat for a pricing-page argument, Inbox Triage for drafts you send, Standup Scribe for a record nobody ships from, Chief of Staff Briefing for a Monday diff. Nobody asks grok.com to be the mailbox. Nobody asks Bot to pin grok-4.6. An incoherent week is one word, Grok, covering all of that. That week is how an unlinked SuperGrok receipt gets treated as a Bot license.
Worth-it framing is a standing-job question, not a "do I like chatting with Grok" question: Is Grok Bot worth it?.
Keep reading: What Is a Grok Bot?, Grok Bot vs Grok Build vs Grok 4.6, One Computer, Many Screens.
Frequently Asked Questions
Is Grok Bot just a better version of grok.com?
No. grok.com and the Grok app are a chat product. You talk, you get a reply, the thread is the unit of work. Grok Bot is a teammate product: named bots, plugins, routines, approvals, and one shared persistent cloud computer for the account. Installing Bot does not upgrade the chat window. It opens a desk with a larger blast radius. If you only wanted better conversation, stay on the chat SKU you can confirm on x.ai and do not connect mail to a VM.
Does Grok Bot run grok-4.6 like the chatbot does?
Do not assert that. grok-4.6 is a documented model with a published cutoff on the developer side. Grok Bot has no model picker for members or admins, uses a fixed serving set with automatic failover, and does not publish which model served a given bot turn. Chat model names, if the Grok app shows them, belong on x.ai's current pages. Mixing those names into a Bot rollout is how teams plan a pin that the Bot product refused.
I already pay for SuperGrok. Do I have Grok Bot?
Only after you link it. An individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription can be linked to your Cursor account from the Grok Bot plan screen; the link is permanent and grants usage, not a Cursor plan. SuperGrok Lite does not include Grok Bot, and SuperGrok Team or Enterprise cannot link. Cursor Pro at 20 dollars a month is the cheapest paid Cursor path, and it includes Bot. Chat access on grok.com is not proof of Bot. Confirm both the chat SKU and the Bot SKU on x.ai and cursor.com the day you subscribe.
Can I use Grok chat and Grok Bot at the same time?
Yes, if you split by job. Use grok.com or the Grok app to think and to handle one-off drafts you will paste yourself. Use Grok Bot for standing named work such as Inbox Triage, where a routine, a charter, and a stop line have to survive next Tuesday. Do not ask chat to watch a mailbox as if it were a coworker, and do not treat a Bot screen as a private chat. Every bot on the account shares one computer. A thread on grok.com is a different product, not a second sandbox.