2026-08-27 · Comparison
Grok Bot vs Claude Cowork vs ChatGPT Work: Pick by Where the Work Lives
The intern's Windows box, the founder's Mac, and the overnight inbox are three different places for work to live. Buying one assistant and forcing all three jobs onto it is how you get a missing morning pack, an NDA on the wrong machine, and a board deck you restaff every Thursday.
This is a three-way picker, not a remake of the pairwise pages. Cloud teammate versus desktop operator is Grok Bot vs Claude Cowork. Named bots versus a task surface is Grok Bot vs ChatGPT Work. This page asks where the work has to live, on whose computer, and whether it still has to exist next Tuesday. Start with What Is a Grok Bot? if you need the object.
Claude Cowork and ChatGPT Work move. This page will not print their prices or freeze their feature lists as fact. Confirm Cowork on Anthropic's Cowork page and Work on OpenAI's ChatGPT Work page the morning you buy. Grok Bot facts were checked on 2026-08-25 against the Grok Bot FAQ and computer and apps. Grok Bot: named bots on one persistent cloud computer. Screens are not vaults. Cowork, as Anthropic currently describes it: closer to a local and desktop operator. ChatGPT Work, as OpenAI currently describes it: a task surface inside ChatGPT. Confirm both. Then pick by home.
Split the three products by whose computer holds the work
Ask whose machine still holds the files, the login, and the unfinished job after two lids close.
Grok Bot's computer is not your Mac and not the intern's Windows PC. It is a managed Linux VM assigned to the user account, not to a bot. Every bot is another named screen on that same machine. Cookies, sessions, files, and CLI credentials are shared. Deleting a bot does not remove those. Isolation detail is one computer, many screens, not a third retelling here.
Cowork's home is the one you re-read on Anthropic. The current product page still leans desktop-first: start there if the work lives in folders and apps on your own computer. Anthropic has also described web, mobile, and cloud continuation. Confirm those on the live page. For this tree, treat Cowork as more local, more this disk, unless the page in front of you says otherwise today.
ChatGPT Work's home is inside ChatGPT. OpenAI currently frames it as gathering context and taking action across tools, files, and desktop apps to produce share-ready documents. That is a job you start and close, not a named bot on an account computer. Confirm plan gates. Do not copy Grok Bot's shared-computer model onto Work.
Walk the founder, the intern, and the overnight inbox through one tree
You are the founder on a Mac. You hired a Windows intern whose job this month is a messy Downloads folder: signed NDAs, local standup transcripts, exports that must not wander. The company inbox has to produce a draft-only morning pack by 07:15 after both lids close. Grok Bot clients exist for both machines (macOS Apple silicon and Intel, Windows x64 and Arm64) plus iPhone (iOS 18 or later) and Android (9 or later) companion apps that can pause routines and approve steps but not edit them.
Ask two questions. Does this job still have to exist next Tuesday with last week's files and the same stop line? Whose computer is allowed to hold it?
Overnight inbox: neither laptop will be awake. That is Grok Bot. Use inbox triage: drafts only, never send. A supported Windows client is a remote control, not the computer.
Intern NDA folder: the files already sit on that disk. That is Cowork-shaped if Anthropic's current desktop grant on that Windows machine can see the folder. Confirm the grant. A standup scribe shape can live on the same disk for local transcripts.
Founder one-off board pack: the job should end when the file lands. That is ChatGPT Work-shaped if Work is on your plan. Confirm OpenAI. Creating a named Grok bot on Thursday and deleting it Friday leaves sessions on the shared computer.
| If the work lives here | Persistence you need | Pick |
|---|---|---|
| A vendor cloud VM that stays awake after both lids close | A named bot still there next Tuesday | Grok Bot on the account computer |
| This laptop's folders and apps (confirm Anthropic) | An operator on this disk, not a copy in a VM | Claude Cowork after you confirm the current desktop grant |
| A ChatGPT job that should end as a pack (confirm OpenAI) | A finished file, not a named coworker | ChatGPT Work after you confirm the current surface |
If two rows fight, residency wins. A qualifying Grok Bot plan does not move an NDA off the intern's disk.
Put standing cloud jobs on the shared account computer
Standing cloud work still has a name in October, still has last week's file, and still has to run when nobody's laptop is open. Inbox packs, a chief of staff briefing that diffs last Monday, a mail cleanup assistant that only proposes labels: those are roles.
Grok Bot is that desk. You name the bot, write the charter, connect the minimum login. One persistent cloud machine for the whole account. Each bot gets a screen. Docs: do not use separate bots as a security boundary. Inbox triage and a research bot on the same account share the cookie jar.
Routines attach to one bot (max 50, 20 recent run records) and die with it. Nothing is team-level. A standing cloud role for the intern is a second Grok Bot account, not a second bot name on yours.
Launched beta 11 August 2026. Eligibility widened 21 August 2026. Cheapest paid path: Cursor Pro at $20 a month. Every paid Cursor plan includes Grok Bot; Cursor Hobby, the free plan, does not, and an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription can be linked instead. Cursor Teams and a one-time trial also qualify. No Grok Bot-specific spend cap beyond the account On-demand monthly limit, no published allowance figure, no model picker. Weekly allowance, then on-demand.
Put the overnight inbox here. Not the intern's NDA folder. Not Thursday's one-off deck.
Keep laptop-local files on a desktop operator until the vendor page says otherwise
Local work already sits on a specific disk, and the blast radius should stay there. Copying the intern's Downloads folder to a cloud computer so you can peek from a phone is a residency decision.
Cowork is the column to check. Anthropic currently presents Cowork as the place you hand Claude real work, running on desktop, with web and mobile described as beta. The line that matters is the desktop app reaching folders and applications on your own computer. If that is still true today, the intern's Windows box is a Cowork home for local files. If Anthropic has moved the default to a cloud session on your plan, re-run the tree. Cloud continuation is not Grok Bot's named roster.
This page will not print Cowork prices. Open claude.com/product/cowork and copy from there. Check whether this intern has the desktop grant, and whether a closed lid stops the operator. A desktop operator that needs the machine awake is the wrong home for overnight mail.
Keep Grok Bot off that folder unless you have a written exception that the NDAs may live on xAI's managed VM. Naming the bot "confidential" does not change who operates the VM.
Send one-off packs to a task surface inside ChatGPT
One-off work should vanish as a role when the file lands. A board pack from a messy export. A teardown you will not repeat. A spreadsheet rebuild for Thursday and never again. Those jobs want a long run and an artefact, not a bot you delete while sessions remain.
ChatGPT Work is the column to check. OpenAI currently describes Work as an agent that can stay with ambitious tasks, gather context, and return polished documents, sheets, and slides. Read the live page for plan gates. Do not treat this recap as a contract. Do not print a Work price. Public writeups often imply a lower entry door than Grok Bot's cheapest paid path. Confirm that the day you subscribe.
Work is not ChatGPT Tasks. Tasks fires a conversation on a clock. If your question is a weekday nag, that is Grok Bot vs ChatGPT Tasks. Mixing Work, Tasks, and "ChatGPT" into one column is how people buy the wrong object three times.
A task surface fails standing jobs in a specific way. Strong pack on Thursday. Next Thursday you are the memory. The prompt drifts. The send verb creeps back in. Use Work when ending is the point.
Score persistence and residency before you score the feature grid
Feature grids go stale. Persistence and residency are properties of the job.
Persistence: does next Tuesday still need the same worker, the same stop line, and last week's file. If yes, you need a desk that remains. On Grok Bot that desk is the account computer plus a named bot. On Cowork and Work, confirm what actually remains after a session. A long run is not a desk.
Residency: whose computer may hold the bytes. Intern disk that must not leave the building: Cowork-shaped, then re-check Anthropic if the live page has moved the work into a cloud session. Reachable at 07:15 with both lids closed: Grok Bot, and you inherit the shared computer. A pack that should not linger as a standing login: Work-shaped ending.
| Grok Bot wins when | Cowork wins when (confirm live) | ChatGPT Work wins when (confirm live) |
|---|---|---|
| The job is a standing role and both laptops will be asleep | The files already sit on this disk and should stay there | The job should end as a file you will not staff as a role |
| You need a named bot, a charter, and last week's path | You need an operator in local folders and desktop apps | You need a long ChatGPT job without inventing a coworker |
| You accept one cloud computer per account, screens not vaults | You accept that a closed lid may stop local computer use until the vendor says otherwise | You accept that you are the memory next time unless OpenAI ships a standing role |
A cheaper feature list does not move a file off the intern's disk.
Count one cloud computer per Grok Bot account, even when two humans log in
The three-way trap the pairwise pages do not have to solve is people, not bots.
If the intern logs into your Grok Bot account to "just check the inbox bot," you added a second pair of hands on the same computer. One account, one persistent cloud machine. They can reach whatever you signed in. Deleting their named bot does not sign anyone out. Hosted MCP sign-in tokens stay with Cursor's backend, not on the computer. A browser login is not that exception.
Screens will not save you. Intern Desk and Founder Desk are two windows, not two offices. xAI's docs say not to use separate bots as a security boundary. Two humans are not isolated because they typed two names.
If the intern needs a standing cloud role, use a separate eligible account. Eligible does not mean Cursor Hobby or Cursor Pro at $20. If they only need local files, do not give them your Grok Bot login. Cowork on their Windows box, confirmed on Anthropic, keeps the NDAs on their disk. If they only need a one-off pack, ChatGPT Work on their own login, confirmed on OpenAI, keeps that job off your cookie jar.
Your intern can collapse two homes into one blast radius by borrowing a password.
Staff the intern on Windows without moving the founder mailbox onto that laptop
Windows is not the problem. Home is the problem.
Grok Bot supports Windows on x64 and Arm64. The intern can install the client. That client talks to the cloud computer for whichever account is signed in. Sign in as themselves: their VM. Sign in as you: your VM.
Cowork and Work on Windows are vendor-page questions. Confirm folder grants, computer use, and whether the intern's ChatGPT plan actually includes Work. Grant one folder, not the whole home directory. A free ChatGPT tab is not automatically Work.
Do not move the company mailbox onto the intern's Windows laptop so they can "own inbox" with a desktop operator. Overnight mail then dies when their PC sleeps or goes home in a bag. The inbox belongs on the account computer, draft-only. Local files stay local. One-off packs stay on a task surface.
Linux desktop, Android, and iPad (through the iOS app) are Grok Bot clients as of September 2026. If someone likes Ubuntu, install the official Linux app, not a community wrapper.
Paste a three-home routing charter the founder can reuse
You need a classifier before you need another bot. Paste this into a note you actually read when a new job appears. Replace the bracketed lines. This is not a bot that sends mail. It is a routing brief so you stop stuffing three homes into one product.
IDENTITY
You are Home Router for [FOUNDER]. You do not run the jobs. You classify
each incoming request into one home and stop. You are not a Grok bot with
a private computer. If a job later runs on Grok Bot, it will sit on the
one persistent cloud computer assigned to the user account. Screens are
not vaults.
THREE HOMES
1. CLOUD DESK (Grok Bot): standing role, lids may close, files may live
on the account computer. One computer per account. Never a second
human on this login.
2. LOCAL DISK (Claude Cowork, confirm Anthropic the morning you use it):
the file already sits on a named laptop and must not be copied to a
vendor VM until a human writes that exception.
3. TASK SURFACE (ChatGPT Work, confirm OpenAI the morning you use it):
one-off pack, deck, or teardown that should end when the file lands.
WHOSE COMPUTER
Founder Mac: client only, unless the job is local files on this Mac.
Intern Windows: intern's disk, intern's own vendor logins. Never the
founder Grok Bot account.
Overnight inbox: CLOUD DESK only. Drafts. Never send.
WHERE YOU STOP
Never send, archive, or delete mail.
Never tell the intern to log into the founder Grok Bot account.
Never copy NDA folders off the intern Windows box onto the cloud desk.
Never treat a second bot name as a second computer.
Never create a named Grok bot for a job that should end on Thursday.
If residency is unclear, ask. Waiting is correct. Copying is not.
OUTPUT
One line: HOME=CLOUD DESK|LOCAL DISK|TASK SURFACE
One line: WHOSE COMPUTER=[founder account VM|founder Mac disk|intern
Windows disk|intern own account]
One line: STOP VERB=[the action a human must still do]
The overnight inbox is safe to leave running only if it drafts and never sends. The intern is safe only if they are not on the founder account. The board pack is safe only if the job ends.
Watch week one and week four diverge by whose disk stayed awake
Run the three jobs on paper through four weeks. The fork is which computer was still on, not which model was smarter.
Week one, matching homes. Draft-only inbox bot on Grok Bot. Intern grants Cowork (confirmed) one Downloads subfolder. One Work job (confirmed) for Thursday's board pack. Inbox pack appears while both lids are closed. NDAs never left Windows. Board pack ends.
Week four, forced Grok Bot because you already pay for Cursor Pro+ at $60 a month. The intern logs into your account "so they can see the NDA bot." Those files now sit next to the mailbox session. You deleted Thursday's deck bot. The vendor portal they used is still signed in. A churn watch bot you added in week three can open that portal. No audit view outside Enterprise.
Week four, forced Cowork as a desktop operator is often described. Intern PC off. 07:15 pack missing. You are on a train with a phone that can pause a Grok bot you never staffed.
Week four, forced Work. Four strong packs, no coworker. Inbox prompt drifted. Someone asked it to send. Confirm what Work asks before send on OpenAI's pages. You are now the memory.
| Job | Week one on the matching home | Week four if you force one product onto all three |
|---|---|---|
| Overnight inbox | Draft pack exists after both lids close | Missing if you used a sleeping desktop; leftover sessions if you used a disposable Grok bot |
| Intern NDA folder | Files stay on Windows under a folder grant you can name | Files sit next to mailbox cookies if the intern used your Grok Bot account |
| Thursday board pack | Work job ends as a file (confirm OpenAI) | Named bot deleted, sessions remain, or you restaff the prompt from memory |
Day fifteen is usually when the intern asks for "just the login." Re-read the routing charter.
Diagnose the wrong-home failure before you rewrite the prompt
When the week breaks, name the home before you touch the wording. Prompt surgery does not move a file back onto the intern's disk, and it does not wake a laptop that was the computer.
| Symptom | You put it on the wrong home | Move it |
|---|---|---|
| 07:15 pack missing because both laptops slept | Desktop operator, or a ChatGPT job nobody started | Grok Bot cloud computer, draft-only |
| Intern NDAs visible to a founder research bot | Shared Grok Bot account, one computer | Intern's disk (Cowork, confirm) or intern's own account |
| You restaffed Thursday's deck as a standing bot, then deleted it | Grok Bot used as a task surface | ChatGPT Work for the one-off (confirm OpenAI) |
| Roundup said each bot is a private VM so two humans are safe | You believed names isolate people | Count computers by account |
| Work pack you cannot point at as a coworker in October | Task surface used as a role | Named Grok bot only if you accept the shared computer |
Approvals on Grok Bot control a proposed action. They do not reverse work already completed. Design the overnight inbox so send is never proposed. On Cowork and Work, confirm the live permission model on the vendor pages. If the intern needed a file while you were on a plane, that is a residency choice: either the file is allowed on the cloud computer, or it waits.
Verify the pick with checks that can fail on all three products
Do not take this page on trust the week you connect a mailbox.
Grok Bot. Create two bots. On bot A's screen, write a file with a unique string, or sign into a throwaway site. On bot B, ask it to read that path or open that site. If bot B can see it, you have one computer. Delete bot A. If the file and login remain, deletion is not cleanup. Do not hand that account to the intern until you have done this.
Cowork, on the intern's Windows box. Grant one folder. Ask it to list that folder. Confirm a folder outside the grant is out of reach. Sleep the PC and see whether the job continues. Take pass or fail from the machine and from Anthropic. If continuation has moved to a cloud session, write down where the files went.
Work. Start a one-off pack. When it finishes, try to treat it as a named coworker next week without pasting a new goal. If you have to be the memory, you confirmed a task surface. Check whether each person's plan actually includes Work.
Platform. Founder Mac and intern Windows: supported Grok Bot clients. Phone app (iPhone or Android): approve steps and pause or resume a routine, but no editing. Linux desktop and iPad (iOS app): supported too. Cowork and Work: vendor pages.
A check that cannot fail is not a check.
Answer the objection that one product should cover all three homes
The strongest case against a three-way picker is simplicity. You already pay for one of these. The intern can use whatever you use. The inbox can wait until someone is at a desk.
That case wins when all three jobs actually live in one home. No intern and no overnight mail: use the pairwise that matches the remaining fight. Only Thursday packs: ChatGPT Work (confirmed) can be the whole story. Only local files: Cowork (confirmed) can be the whole story. Only standing cloud work, and you accept one computer per account: Grok Bot can be the whole story.
It loses the moment the intern's disk and the overnight inbox are both real. "Just use Grok Bot for the NDAs" copies residency into the mailbox cookie jar. "Just use Cowork for the inbox" makes 07:15 depend on a PC that is off. "Just use Work for the standing brief" makes you the bot. An NDA on the wrong machine is worse than a second subscription you can name.
Two humans on one Grok Bot account are one computer. If you cannot afford a second account, keep the intern on local files and keep the founder mailbox off that intern. You can keep all three products. Stop using one object for the other object's job. Confirm Cowork and Work the morning you buy. Do not freeze a three-column price grid from a roundup.
Stop when the job needs a wall none of these three sell
None of these products is a wall between two humans who should not see each other's logins, not if they share a Grok Bot account, and not if you paste the intern's NDA folder into a ChatGPT job on the founder's login. Isolation is an account choice, a disk choice, or a decision not to copy the file.
Do not let any of the three send, pay, post publicly, merge, or delete without a human. Write the stop verb before you pick the home. Do not run a job that needs an immutable action log on Grok Bot: an audit view of bot actions does not exist outside Enterprise. Do not use Grok Build compatibility as a Grok Bot feature. Claude Code, SKILL.md, and CLAUDE.md belong to Grok Build.
The jobs that survive are boring on purpose: overnight drafts, local filing the intern can undo, one-off packs that end. Inbox triage never sends. Chief of staff briefing never invites. If the job fails that filter, keep it.
Keep reading: Grok Bot vs Claude Cowork: Cloud Teammate or Desktop Operator, Grok Bot vs ChatGPT Work: Persistent Bots or a Task Surface, What Is a Grok Bot?.
Frequently Asked Questions
Can one product cover the founder Mac, the intern Windows box, and the overnight inbox at once?
Only if all three jobs actually live in the same home, which they usually do not. Overnight mail that must run after both lids close belongs on Grok Bot's persistent cloud computer with a draft-only charter. Files that must stay on the intern's Windows disk belong on a local operator you have confirmed on Anthropic's current Cowork page. A Thursday pack that should end as a file belongs on ChatGPT Work after you confirm OpenAI's current surface. Forcing one vendor onto all three is how NDAs land next to mailbox cookies, or how 07:15 depends on a PC that is off.
Does each named Grok Bot get its own computer if the intern and the founder both create bots?
No. Every bot on one account shares one persistent cloud computer assigned to the user, not to a bot. Each bot gets a screen. Those screens are desks, not locks. Cookies, sessions, files, and CLI credentials are common to the account. If the intern logs into the founder's account, they sit on that same machine. Deleting a bot does not remove shared files or sessions. Isolation between two people requires two accounts, or keeping the intern off Grok Bot and on their own disk.
Can I treat Claude Cowork or ChatGPT Work prices in this article as current?
No. This page does not print Cowork or Work prices, and it does not freeze their feature lists as fact. Confirm Cowork on Anthropic's current product and pricing pages the morning you buy. Confirm Work on OpenAI's current ChatGPT Work page, including which plans and which clients actually include it that day. Grok Bot's cheapest published paid path is Cursor Pro at $20 a month, with other eligible subscriptions listed in xAI's FAQ and Cursor's plans page as of 23 September 2026. Do not copy a three-column bargain grid from a roundup.
What if I run the overnight inbox on the intern's Windows laptop instead of the cloud computer?
Then 07:15 depends on that PC staying awake, signed in, and at a desk. A desktop operator, including Cowork as commonly described, is a poor home for mail that has to move after both people close the lid. Confirm Anthropic if your plan now continues jobs in the cloud; even then you still have not created a named Grok bot on an account computer with last week's files. Put standing overnight mail on Grok Bot, drafts only. Keep the intern's local folders on the intern's disk. Do not move the company mailbox onto a laptop that goes home in a bag.