2026-08-27 · Comparison
Grok Bot vs Gemini Gems: Persistent Names, Different Machines
You already have a Gem named Inbox. That name survived last month. It did not buy you a computer.
Grok Bot vs Gemini Gems is the search you type when a named helper in Gemini looks interchangeable with a named Grok bot. Both names can still be there next Tuesday. Only one of those names sits on a persistent cloud computer assigned to your user account. Grok Bot, which xAI put into beta on 11 August 2026 and widened on 21 August 2026, is a roster of named bots on that shared xAI and Cursor machine. A Gemini Gem, on Google's Gems overview, is a custom AI expert you build inside Gemini: saved instructions, optional uploaded files, a name you reopen. Confirm Gems on Google before you treat any recap, including this one, as a contract.
Grok Bot vs ChatGPT Work is a different fork: a standing named bot versus a task surface that returns a file. Here both names already persist. The question is whether a desk exists under the name. For the plain definition of the Grok side, read What Is a Grok Bot?. For the objects on the machine (computer, screen, routine), read How Grok Bots Actually Work.
Call a Gemini Gem a named helper inside Gemini, then reconfirm it on Google
Google's current Gems page calls Gems custom AI experts for help on a topic: a career coach, a brainstorm partner, a coding helper. It says you can start from premade Gems or build your own. It says Gems let you save highly detailed prompt instructions for repeatable tasks, and that you can upload files so a custom Gem has context. Availability varies. That is the whole claim you should treat as sourced from Google today. Everything else you have heard (Workspace connectors, scheduled sends, a private computer, a price) belongs on Google's live pages, not in this article as fact.
A Gem is a named configuration inside Gemini. You open it. The saved instructions are already there. You talk. Confirm on Google whether uploads persist across chats. Public writeups disagree about conversation history, connected apps, and whether a Gem can act outside the chat window. Open Gemini this week and read what Google shows you. Do not settle those fights from a roundup.
None of that makes a Gem a named bot on a cloud computer assigned to your account. The name persists. The instructions persist. A desk with last week's files, a signed-in portal, and a routine that fires after the lid closes is a different object. If you only needed the name, keep the Gem. If you needed the desk, you are looking at Grok Bot.
Sit Grok Bot names on one account computer that every bot shares
On Grok Bot you hire a name, you write a charter, you get a screen, and you may pin routines to that one bot. You do not get a private box. xAI documents that the computer belongs to the user account, not to the bot. Every bot on the account shares that one persistent cloud computer. Each bot gets a screen. Those screens are work surfaces. They are not security boundaries. The docs say, verbatim, not to use separate bots as a security boundary.
Cookies, live browser sessions, files on disk, and CLI credentials are account-wide. Remove a bot and those leftovers stay. Routines die with the bot. The desk does not. Hosted MCP sign-in tokens stay with Cursor's backend, not on the computer. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording. Read One Computer, Many Screens rather than inferring a private VM from two names.
Supported Grok Bot clients: macOS (Apple silicon and Intel), Windows (x64 and Arm64), Linux (x64 and Arm64), iPhone on iOS 18 or later, and Android 9 or later; the iOS app also runs on iPad (iPadOS 18 or later). The remote computer is a managed Linux VM. The bot process is non-root. That VM is not a Linux desktop app you install. If your daily phone is Android, Gemini and the Grok Bot companion app can both be there.
Keep the name when it survives, and buy a computer only when the job needs a desk
Line the two products up as shapes, not as feature lists.
| Object | What persists | What does not persist | Confirm where |
|---|---|---|---|
| Named Grok bot | The bot, its screen, its routines (until you delete the bot) | Isolation from other bots on the same account | docs.x.ai |
| Grok Bot screen | A work surface on the shared computer | A security vault, a private VM, a Gem | docs.x.ai |
| Grok Bot routine | A workflow pinned to one bot (max 50 per bot) | Team-level schedules, a Gem clock | docs.x.ai |
| Gemini Gem name | A named helper you can reopen inside Gemini, per Google | A cloud computer assigned to your account | |
| Gem instructions | Saved prompt instructions on Google's Gems page | Overnight files on a Grok Bot home directory | |
| Gem uploads | Google's page mentions files you give a custom Gem | Shared-computer cookies and CLI credentials |
Names persist in both columns. Computers persist in one. If the job is "talk to Inbox with the same rules I wrote in March", a Gem can match, assuming Google still ships Gems that way on your plan. If the job is "every weekday at 07:00, open last week's triage file, and stop before anyone is contacted", you need the computer. Do not buy Grok Bot because both are named. Buy the desk when the work has to live on a machine that stays awake.
Stop translating Grok Bot screens into Gems, because screens are not vaults
The most expensive metaphor in this search is "I have three Gems, so I will staff three Grok screens and get three vaults." A Grok Bot screen is not a Gem. A Gem is not a screen.
A Gem is a named helper inside Gemini. It does not sit on xAI's shared computer. It does not hold Gmail cookies next to a research bot's CRM session. Confirm what Google currently isolates between Gems. Do not copy Grok Bot's shared-computer model onto Gemini, and do not paste a Gem instruction file onto a Grok screen and call it a vault.
A Grok Bot screen is a work surface on one account computer. Two screens look like two rooms. They share the kitchen. The mailbox login, the CRM session, and the browser cookies are account-wide. Naming does not partition credentials. Retiring Lead Scout after a scare does not sign Inbox Triage out.
If you need two workers who cannot see each other's logins, a second Gem name does not prove Google gave you that wall, and a second Grok Bot name does not give you that wall on one account. Split Grok Bot accounts if you need a Grok-side wall. Confirm Gem isolation on Google.
Rewrite the inbox Gem as a charter only after you admit it never owned files
The sentence that starts this migration is almost always the same: I already have a Gem for inbox.
Ask what that Gem actually did. You opened Gemini. You talked. You may have pasted threads or attached a file, if Google currently allows that. You left with a draft. The name Inbox was still there the next morning. Last Tuesday's triage file was not on a cloud computer unless you saved it somewhere else. The Gem never owned a desk. It owned a prompt.
That is not a failure of Gems. Repeatable talk is not unattended mail. If you were present for every turn, the Gem may have been the right object. If you wanted the unread pile sorted at 07:00 after you slept, you wanted a machine, a routine, and a stop line.
Staff Inbox Triage on Grok Bot only after you write the verb the Gem never had to refuse unattended. The listing's boundary is send: the bot drafts, and a human sends. A Gem you watch can be told "do not send" in instructions. A bot you leave running needs that line in a charter, because the computer can keep a mailbox session warm while you are not looking. Paste a stop list before you paste a login.
Assign weekday inbox work to one bot's routines, then accept the fifty-routine cap
A routine on Grok Bot assigns a workflow to one bot. Maximum 50 routines per bot. The app keeps the 20 most recent run records per routine. Deleting the bot deletes its routines. Nothing is team-level. 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. If you edit Gems on your phone the way you edit a note, do not expect the same surface on Grok Bot's iPhone client.
Do not assert that Gems have a scheduler, a routine object, or a weekday clock. Confirm any automation Google currently attaches to a Gem on Google's pages. Public writeups about Gemini sometimes mix Gems with other Gemini features. Mixing them in your head will make you believe Inbox already runs at 07:00 because the Gem is named Inbox.
Pin the weekday job to Grok Bot scheduling on one bot, then live with the caps. Fifty routines is a trap if you treat one bot as a department. Twenty run records is not an audit log. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording. If you needed a named Gem you open when you sit down, you never needed the routine.
Measure Grok Bot risk on cookies and home-directory files, never on Gem names
On Grok Bot, blast radius is files and sessions. An Inbox Triage bot that may only draft still sits on the same machine as a Lead Scout that can see the same browser. Chief of Staff Briefing is valuable because last week's file lives on that computer. A hostile prompt in mail is not contained by the briefing bot's name.
On Gems, blast radius is whatever Google currently lets that Gem see. Confirm that list. Do not print a connector catalogue as fact. Do not assume a Gem can send Gmail because you use Gmail, and do not assume it cannot because a 2025 blog said Gems stay inside the chat. Open Google's page the day you connect anything.
Connect the minimum accounts on the Grok side. Prefer read-only where the job only reads. Put money on a different account from research. When a bot is done, rotate the sessions yourself. Deleting the bot is not cleanup. Confirm what Google still stores for a Gem you have not opened in months.
Enter Grok Bot through Cursor Pro or a SuperGrok link, never through a guessed Gem tier
Published Grok Bot prices sit below. This article will not invent Gem pricing, a Gemini plan gate, a Workspace SKU, or a list of apps a Gem can reach. Recheck those on Google. Public writeups compare Gems to Custom GPTs. Treat that as a picture, not a contract.
| Path | Grok Bot on this plan? | Note |
|---|---|---|
| Cursor Hobby | No | Free Cursor does not include the bot runtime |
| Cursor Pro, 20 dollars a month | Yes | Cheapest paid path, checked 23 September 2026 |
| Cursor Pro+, 60 dollars a month | Yes | More weekly usage than Pro |
| 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 | Never stacks with a Cursor plan |
| SuperGrok Heavy, Cursor Ultra, Cursor Teams, one-time trial | Eligible | Confirm live prices. Ignore a viral 300 dollar Heavy figure |
| Gemini Gems | Confirm on Google | Do not paste a Gemini screenshot into this comparison |
Once you are eligible, the bill is not a ceiling. xAI has not published a Grok Bot-specific spend cap. Subscriptions include a weekly usage allowance, then on-demand billing from model and token cost. No published dollar figure for that allowance. No model picker on the bot surface. If both a Cursor and a SuperGrok subscription are present, Grok Bot uses whichever has more usage. See Grok Bot Cost. A cheaper Gemini door, if it exists on your account, is a good reason to keep watched drafting as Gems. It is a bad reason to staff unattended mail on a chat preset.
Follow the founder who already had a Gem named Inbox through four weeks
Same person. Same mailbox. Two objects. Watch what exists on day 30.
| When | Gem named Inbox | Named Grok bot on the shared computer |
|---|---|---|
| Day 1 | Open the Gem, paste this morning's pile. Instructions already know the buckets | Name Inbox Desk, paste a charter, connect mail as in Grok Bot Gmail |
| Day 8 | Same Gem name. You still start the chat. Last Tuesday's output lives in Gemini only if Google kept it | A routine fired. Last week's file is on the computer. The stop line is still in the charter |
| Day 15 | A colleague uses a different Gem. Two chats, no shared desk unless Google says otherwise | A second research bot can see the same browser. The Inbox name did not wall it off |
| Day 30 | The name Inbox still exists. Unattended 07:00 never happened unless some other Gemini feature did it. Confirm that feature | A named bot, a month of files, a blast radius you can name. Deleting the bot would not log the browser out |
Day 15 is where the Gem story and the Grok story stop rhyming. Independent named helpers that cannot see each other's logins are not what one Grok Bot account sells, and a second Gem name is not proof Google sold that wall either. If you wanted a standing file at 07:00, the Gem kept asking you to show up. A Grok approval gates the proposed action. It does not unwind work that already happened. Keep the irreversible verb out of the charter so it is never proposed.
Match the Tuesday gap to the machine that never existed, not to a bad prompt
When the week goes wrong, name the machine before you rewrite the Gem instructions.
| Symptom | Likely cause | Fix |
|---|---|---|
| The Gem named Inbox did not sort mail at 07:00 while you slept | A Gem is a named helper you open, not a documented Grok-style routine | Put the clock on one Grok bot, or keep being present |
| You staffed three Grok screens because you had three Gems | Screens are not Gems and not vaults | One account computer. Split accounts if you need a wall |
| You deleted a Grok bot and the mailbox is still signed in | Deletion does not wipe files or sessions | Sign out and rotate the session yourself |
| Two Grok bots used the same mailbox cookies | Shared computer, by design | One account is one domain. Split accounts for a wall |
| Grok Bot never appeared on Android or a Linux laptop | An install guide from before September 2026, or an ineligible plan | Install the official Android or Linux app, then check the plan |
| Last week's brief is missing after you migrated from the Gem | The Gem never stored that file on the Grok computer | Copy the artefact yourself, then run the bot against the folder |
If the job is "open the supplier portal every Monday", verify that Gemini currently allows that from a Gem. Grok Bot can keep a session warm on the shared computer. That warmth is the blast radius. If Tuesday failed because you were not at the keyboard, you did not have a prompt problem. You had a machine problem.
Concede the week where a named Gem is the whole job and a cloud desk would be waste
The honest objection is that Inbox already exists as a Gem, so a Grok bot is a pricier label for the same habit. For a large class of jobs, that objection wins.
It wins when you are present. Tone of voice, a coding helper, a career-coach Gem, a brainstorm partner: Google's own examples. You open the Gem, you talk, you leave with text. Creating Inbox Desk on a shared computer for that job leaves sessions you did not need.
It wins on friction. Opening a Gem is closer to continuing Gemini than naming a bot and living with overflow that has no per-bot cap. If Google currently includes Gems on a plan you already pay for, confirm that, and keep the Gem for talk.
It loses when the name has to survive on a desk you are not looking at. Unread mail every weekday, daily lead ranking, a Monday brief that diffs last week: those jobs need last week's file, a clock, and a stop line that still holds at 07:00. A Gem can fake that if you paste the pile yourself every morning. Most people skip a week, and the send verb creeps back in because it was never pinned to a machine.
It also loses when the stall is a four-minute export, a portal with no API, or a 2FA prompt. The computer is for that stall. A Gem chat is for staying with a conversation. Sharing a persistent name does not make those stalls the same.
Keep Gemini Gems for saved talk and keep Grok Bot for overnight files
You can keep both. Stop using one name as proof you bought the other machine.
Keep Gemini Gems (once you have confirmed them on your plan) for saved instructions and a conversation you start. House style. A coding helper. A coach. Drafting you watch. Confirm each Gem's permissions on Google. Do not assume a Gem can hold a mailbox session, and do not assume it cannot.
Keep Grok Bot for a name, a charter, a stop line, and a desk that still has last week's file. Run a short roster. Connect the fewest logins that still do the job. Write the verb that must never happen. Every bot shares the computer. Deletion is not cleanup. Overflow has no per-bot cap, only the account's On-demand monthly limit. There are Linux desktop and Android apps as of September 2026, and the iOS app also runs on iPad (iPadOS 18 or later).
Paste this only after you have admitted the Gem never owned the folder. Change the paths. Do not connect a mailbox until the stop list is true.
You are Inbox Desk, not a Gemini Gem.
WHAT YOU OWN
Every weekday by 07:00 Europe/London, read the connected mailbox
and write /inbox/YYYY-MM-DD.md plus /inbox/latest.md.
Three buckets: must-read (cap seven threads), waiting on me,
and noise as a count. Each must-read line: sender, subject,
one-line stake, recommended human action.
WHAT GOOD LOOKS LIKE
Money, access, and legal threads are quoted and stopped.
If two threads contradict, keep both versions and name the gap.
Do not average the gap away. Yesterday's file at
/inbox/latest.md is in scope for "what slipped".
WHERE YOU STOP
Never send, archive, label, forward, or delete mail.
Never create calendar events. Never contact a sender.
If a login expired or a thread cannot be sourced, write
BLOCKED with the missing piece and halt. Do not invent mail.
IF YOU ARE UNSURE
Stop and ask. Inventing a reply is not allowed.
That charter is wasted on a Gem you only open while watching the screen. It is the working document for a bot you intend to leave on the shared computer. Inbox Desk never sends. Name the verb that would embarrass you, then keep the bot off that verb. A Gem instruction that says the same thing is still an instruction inside Gemini, not a desk.
Fail the migration if last week's brief is missing from the shared computer
Prove the split with checks that can fail. If they pass on the Gem alone, you did not migrate. You renamed a chat.
Open the Grok Bot computer after a weekday routine. If /inbox/latest.md is missing, the Gem still owns your memory and the bot is theatre. If the file exists and you never sat at the keyboard, the computer did the job the Gem could not do while you slept.
Create a second Grok bot on the same account. If it can see the mailbox cookies the first bot used, you have not bought a second expert as a vault. You bought a second screen. That check should fail your isolation story. It should pass your reading of how Grok bots actually work.
Delete a throwaway bot after a test login. If the vendor portal is still signed in, deletion did not clean the desk. Rotate the session. A Gem you delete may or may not drop uploads: confirm on Google, then do not use that answer as a Grok Bot cleanup plan.
From the phone app (iPhone or Android) you can approve steps and pause or resume a routine, but not edit it. Edit Gems on your phone if Google still allows that. Grok Bot now runs on Android and iPad as a companion, but editing and testing a routine need a Mac, Windows or Linux desktop. Move standing mail to a desktop you actually use, or do not staff the bot.
Keep reading: What Is a Grok Bot? The Plain Explanation for Non-Engineers, Grok Bot vs ChatGPT Work: Persistent Bots or a Task Surface, How Grok Bots Actually Work, Without the Dedicated-Computer Myth.
Frequently Asked Questions
Is a Gemini Gem the same thing as a Grok Bot screen?
No. A Gem is a named helper inside Gemini: saved instructions and, on Google's current Gems page, files you can upload. A Grok Bot screen is a work surface on one persistent cloud computer assigned to your user account, not to the bot. Screens are not security boundaries and they are not Gems. Confirm what Google isolates between Gems. On Grok Bot, cookies, sessions, files, and command-line credentials are shared across bots. Do not staff three screens because you already have three Gem names.
Does each Grok Bot get its own cloud computer?
No. xAI assigns one persistent cloud computer to the user account. Bots share it. Each bot receives a screen on that machine, which is a work surface, not a vault and not a Gem. Cookies, sessions, files, and command-line credentials are shared. The docs say not to use separate bots as a security boundary. Deleting a bot does not remove those shared files or browser sessions. If you need isolation, use a different account, not a second named bot.
Can I keep my inbox Gem and add a Grok Bot for the same mailbox?
Yes, if you split by machine, not by nickname. Keep the Gem for talk you start: tone, a draft you watch, a classification you paste back. Put unattended weekday mail on a named Grok bot with a written stop line, a routine, and last week's file on the shared computer. Do not point both at send. Confirm on Google whether the Gem can act outside the chat. Grok Bot's computer is one security domain for every bot on the account. Two send buttons is a process failure, not a feature of either name.
How much do Gemini Gems cost next to Grok Bot?
Grok Bot's cheapest paid path is Cursor Pro at 20 dollars a month. Cursor Hobby omits it. An individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription can be linked instead. Cursor Pro+, Cursor Ultra, Cursor Teams, and a one-time trial are also eligibility paths. There is no per-bot Grok Bot spend cap: weekly allowance, then on-demand up to the account's On-demand monthly limit. Gemini Gems prices, plan gates, and whether Gems sit on a plan you already pay for belong on Google's pages. Confirm both the day you buy. Do not invent a Gem SKU from a screenshot.