2026-08-27 · Comparison

Grok Bot vs Microsoft Copilot: Two Different Kinds of Help

Microsoft printed the word Copilot on several products, and a grok bot vs copilot search treats that family name as one assistant you can score against a named cloud teammate. That mashup is how a sales lead who already lives in Outlook and Teams buys a second computer outside the tenant, and how a founder who needs overnight research on a site with no API buys a coding assistant that never leaves the editor.

Copilot is not one product. Copilot in Microsoft 365, Copilot Studio, GitHub Copilot, and Windows Copilot are different objects. Confirm names, plans, and capabilities on Microsoft's current pages. This article will not invent Copilot prices. Grok Bot is one object: named bots on one persistent cloud computer assigned to your user account. They can keep working after the laptop closes. They share cookies, sessions, files, and command-line credentials. A screen is not a VM. The decision is workplace graph plus Microsoft tenancy versus a persistent xAI and Cursor cloud computer with a shared blast radius. Pick by where the work already lives. Start at What Is a Grok Bot?.

Split Microsoft Copilot into the four products a buyer actually means

If someone says they already have Copilot, ask which object they mean before you compare anything to Grok Bot. The family name is the trap.

Copilot in Microsoft 365 sits inside Outlook, Teams, Word, Excel, PowerPoint, and related surfaces Microsoft currently lists, described as help grounded in the Microsoft Graph. Confirm apps, license, and grounding on Microsoft's current Microsoft 365 Copilot pages.

Copilot Studio is a builder for agents you publish inside Microsoft's ecosystem, often into Teams. Confirm connectors, grounding, publishing targets, and any browser or computer-use claims on Microsoft's current Copilot Studio pages. A builder in a tenancy is not a named roster on an xAI cloud computer.

GitHub Copilot is a coding assistant in supported editors. Confirm plans and IDEs on GitHub's current Copilot pages. Autocomplete in VS Code is not overnight portal research, and it is not a standing Lead Scout.

Windows Copilot, or Copilot in Windows, is OS-level help on a Windows PC. Microsoft has moved this name more than once. Confirm the live Windows experience on Microsoft's current Windows pages. Help on this desktop is not a cloud teammate that keeps working after the lid closes.

If the person cannot point at one row, they have a brand, not a comparable Copilot.

Treat Grok Bot as one object: named bots on one shared cloud computer

Grok Bot is a roster of named bots on one persistent cloud computer that xAI assigns to your user account. You do not pick the model. You do not get a computer per bot. You do not get a Linux desktop client. The box is a managed Linux VM the Bot runs on as a non-root user. That is hosting, not a client you install on a Linux workstation.

Each bot gets its own screen. The screen is a work surface. xAI's docs tell you not to use separate bots as a security boundary. Browser cookies, signed-in sessions, files, and command-line credentials are shared. Deleting a bot deletes that bot and its routines. It does not remove shared-computer files or browser sessions. Hosted MCP sign-in tokens stay with Cursor's backend, not on the computer.

The product launched in beta on 11 August 2026. Eligibility widened on 21 August 2026. Supported clients are macOS (Apple silicon and Intel), Windows (x64 and Arm64), and 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). 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.

A routine assigns a workflow to one bot (max 50 per bot). The app keeps the 20 most recent run records per routine. Deleting a bot deletes its routines. Nothing is team-level. Teach-by-demonstration lasts up to ten minutes, captures no microphone audio, produces a draft skill, works for browser workflows only, and is unavailable on iPhone. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording. A chief of staff briefing bot and an inbox triage bot look like two hires. They share one cookie jar. Isolation: one computer, many screens. Claude Code, SKILL.md, and CLAUDE.md compatibility belong to Grok Build, never to Grok Bot. See Grok Bot vs Grok Build.

Decide between a Microsoft workplace graph and a persistent cloud computer

Feature checklists go stale when Microsoft renames a surface. The question that survives is where the work has to live for the job to finish.

If the artefact already sits in a Microsoft tenant (mail in Outlook, files in SharePoint, meetings in Teams), the matching help is the Copilot object allowed to read that graph, assuming your tenant actually has it. Confirm the SKU on Microsoft's pages before you assume the graph is in play.

If the artefact sits behind a login on a site with no API, and the job has to continue after the laptop closes, the matching help is a persistent cloud computer with a browser. That is Grok Bot's shape, and its blast radius: every other bot on the account can see the same session.

Naming a second Grok Bot does not create a second tenancy. This is also not the Claude Cowork comparison. Cowork, as public writeups describe it, is a desktop operator on local files. Copilot in Microsoft 365 is help inside a workplace graph. Different opponent, different machine: Grok Bot vs Claude Cowork.

Follow the sales lead whose work already lives in Outlook and Teams

Take a sales lead at a company that already runs Microsoft 365. Calendar in Outlook, deal chatter in Teams, pipeline notes in a Microsoft file. Tuesday's job is: leave the meeting, draft a follow-up, and not drop an overnight thread.

If that tenant has Copilot in Microsoft 365, the matching help is inside the apps the lead already has open. Draft in Outlook. Recap in Teams. Pull context from the Graph Microsoft currently exposes to that license. Confirm those verbs on Microsoft's current pages for your SKU.

Grok Bot can still touch that world, but as a second computer. You sign Outlook into the shared cloud browser, or you connect whatever hosted MCP path is available that week. Hosted MCP tokens stay with Cursor's backend. A browser login does not. Once Outlook is a cookie on the Grok Bot computer, every bot on the account can use that session. A research bot you add on Thursday can open Friday's mailbox.

Grok Bot wins for this sales lead only if a job the Graph cannot see has to keep running after the lid closes: a customer portal with no Microsoft connector, a pricing page that needs a login, a sheet that has to land before 07:00 while the laptop is in a bag. If the job is "draft the follow-up in the mailbox we already use," evaluate Copilot in Microsoft 365 first. Staffing inbox triage on Grok Bot adds a named bot and a shared cookie jar outside the tenant. Write never-send before you paste the login. GitHub Copilot is not this paragraph. Windows Copilot is not this paragraph unless the question was help on the PC in front of them.

Follow the founder who needs overnight research on a site with no API

Now take a founder whose bottleneck is a site with a login and no API: a partner directory, a grant portal, a supplier catalog. The useful run takes forty minutes. The laptop closes at 23:00. The research still has to exist at 07:30.

Copilot in Microsoft 365 does not become a persistent cloud browser because the founder also has a Microsoft account. Confirm on Microsoft's pages whether your license can sign into an arbitrary site overnight and write a ranked file while the device is off. Do not assume it can. Do not assume Copilot Studio can either, unless Microsoft's current Studio pages say so for the runtime you would actually use.

GitHub Copilot and Windows Copilot will not run that portal overnight. For a ChatGPT task surface, see Grok Bot vs ChatGPT Work.

Grok Bot is the matching shape: a named lead scout that researches and ranks, never contacts anyone, never creates an account, and never uses an Outlook session already in the same browser. Day one is a messy sheet. Day thirty is dated files and a second bot that can see the portal login if you added one.

If you are both people, you can keep both stacks. Do not sign Outlook into the same Grok Bot computer that holds the portal session unless you accept one blast radius.

Confirm every Microsoft Copilot claim on Microsoft's current pages

Microsoft moves Copilot names, SKUs, and surfaces. Treat every Microsoft sentence on this page as a pointer. Before you budget, copy plan names, app lists, and any computer-use or Studio runtime claims from Microsoft's current pages for the object you named. If a competitor prints a Copilot price next to Cursor Pro at $20 a month, discard the Copilot number and keep the Grok Bot number only if you re-check the Grok Bot FAQ.

Grok Bot facts here were checked on 2026-08-25, and the plan facts again on 2026-09-23, against the Grok Bot FAQ and computer and apps. SpaceX acquired xAI (announced 2 February 2026). SpaceX acquired Anysphere, the company that makes Cursor (closed 14 August 2026). Do not invert that chain. See why Grok Bot needs a Cursor account.

Measure Grok Bot blast radius in sessions and files, never in bot names

The expensive mistake in grok bot vs copilot is staffing three Grok Bots, believing you bought three computers, then signing Outlook into one of them. Cookies, sessions, files, and CLI credentials are common. A mail cleanup assistant that may only propose deletions still sits on the same machine as a churn watch bot that can open the same browser. Deleting Churn Watch does not sign Mail Cleanup out.

Approvals stop a proposed action. They do not reverse work already completed or unsay a cookie. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording. If you needed an immutable mailbox log, that is a tenant story. Prefer least privilege bots and approval rules and reversibility before you connect mail. Confirm Microsoft's blast radius on the Copilot object's current pages. Connect the minimum accounts on Grok Bot. Put the portal login on a different account from the mailbox if those jobs cannot share a blast radius. When a bot is done, rotate the sessions yourself.

Budget Grok Bot from published Cursor and SuperGrok paths only

Grok Bot access is a subscription check, not a Grok Bot SKU you add at checkout. The table is the eligibility list, checked 2026-09-23 against the FAQ. Cursor Pro at $20 a month is the cheapest paid path. There is no Grok Bot-specific spend cap, only the account-level On-demand monthly limit: weekly allowance, then on-demand from model and token cost, with no published dollar figure for the allowance. There is no model picker. See Grok Bot cost, spend cap and token burn, and the Grok Bot free trial. Do not invent Copilot prices.

A company can pay for GitHub Copilot and Microsoft 365 Copilot and still lack Grok Bot, or pay for Cursor Pro+ and still lack Copilot in Outlook. Those are different bills. A grok bot vs copilot grid with one Copilot column is already wrong: "can it read mail?" is Graph access in a tenant, or a cookie on a shared Grok Bot computer. Both can be yes. They are not the same yes.

Keep Microsoft Copilot when the artefact already sits in the tenant

Stay in Microsoft when the work is already in the workplace graph and the compliance story has to stay in the tenant: the sales lead whose mail and Teams threads are the product, the team that cannot put customer mail on a vendor VM, the shop whose admins will not approve a second cloud computer with no audit view outside an Enterprise contract, the engineer who actually needed GitHub Copilot in the editor, the person whose files must not leave this Windows PC.

Confirm the matching Copilot object on Microsoft's current pages, then use it for that artefact. Do not staff a Grok Bot as a political workaround. You will still have the tenant plus a shared cookie jar. Supported clients are macOS, Windows and Linux on desktop, plus iPhone (iOS 18 or later) and Android (9 or later) companion apps; the iOS app also runs on iPad (iPadOS 18 or later). A Linux workstation has been a Grok Bot desktop since September 2026. Details: Grok Bot supported platforms.

Keep Grok Bot when the door is a login and the laptop has to close

Buy Grok Bot when the job is a standing named role on a computer that stays awake, and the door is a site or a workflow Microsoft's current Copilot objects do not cover for you.

That is the founder on the portal with no API. It is a Monday ranking of inbound leads from public pages plus a CRM tab that is not in Microsoft Graph. It is a briefing bot that diffs last week's file. It is a routine that fires while you are on a train, with pause and resume on iPhone (iOS 18+). It is not GitHub Copilot, and it is not Windows help on a sleeping PC.

Staff few bots. Connect few accounts. Put inbox triage and lead scout on the same account only if they may share sessions. Inbox triage never sends. Lead scout never contacts. Routines belong to one bot and die with it. See Grok Bot scheduling, is Grok Bot worth it, and Grok Bot and Gmail. Do not assume a Gmail pattern transfers to a Microsoft shared mailbox.

Answer the claim that Copilot Studio already ships the agent you wanted

The strongest case against this page is simple: Copilot Studio already lets you build an agent, ground it on Microsoft Graph, and publish it into Teams, so a named Grok Bot is a second runtime you do not need.

That case wins when the work is the tenant: the agent must stay inside Microsoft's compliance boundary, talk to the same SharePoint corpus, and appear where the company already works. Confirm builder limits, licensing, and publishing on Microsoft's current Copilot Studio pages. This page will not print a Studio price or a connector count. It also wins when the buyer wanted GitHub Copilot and searched grok bot vs copilot by accident. Buy the editor product.

It loses when the job is a login Microsoft does not connectorize and a clock that continues after the lid closes. A Studio agent is not, by default, a persistent xAI cloud computer with a shared browser. If Microsoft currently ships a Studio runtime that drives arbitrary logged-in sites overnight, that will be on Microsoft's pages. Check. If it is there for your license, Studio may cover the founder case too. If it is not, the founder still needs the cloud computer.

It also loses when you needed a roster of named stop lines on one desk, and you accept that the desk is one security domain. If Studio wins, it should win because of tenancy, not because you thought each Grok Bot had a VM.

Windows Copilot does not become Studio. GitHub Copilot does not become a portal scout. Copilot in Microsoft 365 does not become a computer that clicks a site with no API unless Microsoft's current pages say that for your SKU.

Paste a research charter that assumes other bots share the same browser

A charter that pretends the scout has a private machine will use whatever login is already in the jar, including Outlook if you signed it in for the sales job. Paste this for the founder case, then replace the brackets. Do not connect a portal until the stop list is true.

IDENTITY
You are Night Portal Scout for [COMPANY]. You research [SITE URL], which has
no public API. You are one named bot on a shared cloud computer assigned to
the user account, not to you. Other bots on this account can see the same
browser cookies, signed-in sessions, files, and CLI credentials. Your screen
is a work surface. It is not isolation. Do not use an Outlook, Teams, or
mailbox session even if one is already signed in.

WHAT YOU OWN
Each night by 07:00 [TIMEZONE], write a ranked research file at
[PATH ON THE SHARED COMPUTER] with:
  Targets reviewed: count
  Changes since yesterday: quoted, with the URL
  Ranked opportunities: [N] rows, each with source URL, one-line stake,
    and a recommended next action for a human
  Blocked: any login wall, captcha, paywall, or missing page, quoted

You do not own: email, LinkedIn, CRM writes, form submits that create an
account, purchases, or outreach of any kind.

WHERE YOU STOP
Never contact a person or a company.
Never send mail, Slack, or a form that notifies anyone.
Never use another bot's mailbox or CRM session.
Never export files off this computer.
Never treat a separate bot as a security boundary.
If a step needs a session you did not need yesterday, stop and ask.
An approval, if one appears, controls a proposed action. It does not undo
work already done.

WHEN UNSURE
If the page could be a login trap, a purchase, or a legal filing, quote it
and stop. If two bots on this account could collide on this site, stop and
name the collision.

OUTPUT
Write only to [PATH]. Do not mail the file. The human copies what they need.

The boundary is what makes it safe to leave running overnight. Research only. No outreach. No borrowing the sales lead's Outlook cookie. Put the same shared-computer paragraph in any mail bot on this account. For a human-facing pass, use the Grok Bot safety checklist.

Prove the choice with checks that can fail before you connect a mailbox

Do not take a grok bot vs copilot article on trust if you are about to paste an Outlook login or a portal password.

On the Microsoft side, name the Copilot object in one sentence you could show an admin: "Copilot in Microsoft 365 on tenant X, license Y, apps Z." Open Microsoft's current page. If you cannot find the license and the app list, you do not have a Copilot you can compare. For Studio, publish a harmless agent to a test Team and confirm it cannot see a SharePoint library you did not grant.

On the Grok Bot side, create two bots. Write a unique file or throwaway login on bot A's screen, then ask bot B to read it. If bot B can see it, you have one computer. Delete bot A. If the file and login remain, deletion is not cleanup. Remove both yourself. Then shut the laptop on the founder job and, separately, try the sales follow-up inside Outlook with Copilot in Microsoft 365 (confirm live) and no Grok Bot.

Add a second Grok Bot only after you can name what it can reach that the first bot can reach. If the answer is everything, you added a name, not a lock.

Keep reading: What Is a Grok Bot?, One Computer, Many Screens, Grok Bot vs ChatGPT Work.

Frequently Asked Questions

Is Microsoft Copilot one product I can line up against Grok Bot?

No. Copilot is a family name. Copilot in Microsoft 365, Copilot Studio, GitHub Copilot, and Windows Copilot are different objects, and Microsoft may list more on the day you read this. Confirm the specific product, plan, and capabilities on Microsoft's current pages before you compare anything to Grok Bot. Grok Bot is one object: named bots on one persistent cloud computer assigned to your user account. A grok bot vs copilot grid with a single Copilot column is already the wrong shape, even if every cell looks tidy.

Does each Grok Bot get its own cloud computer or VM?

No. Every bot on the account shares one persistent cloud computer assigned to the user, not to a bot. Each bot gets a screen on that machine. Screens are work surfaces, not security boundaries. Browser cookies, signed-in sessions, files, and command-line credentials are shared. Deleting a bot removes the bot and its routines, not the files or browser sessions. xAI's docs tell you not to use separate bots as a security boundary. Roundups that describe a private VM per bot are describing a product that is not this one.

Should a sales team that lives in Outlook and Teams switch to Grok Bot?

Evaluate Copilot in Microsoft 365 first if the mail, calendar, and Teams threads already live in the tenant. Confirm the license and the apps on Microsoft's current pages. Grok Bot is a second computer outside that tenancy, with a shared cookie jar for every bot on the account. Switch, or add Grok Bot, only when a job the Graph cannot see has to keep running after the laptop closes, such as research on a site with no API. Write a never-send boundary before any mailbox login. Do not treat GitHub Copilot or Windows Copilot as the Outlook answer.

Can GitHub Copilot or Copilot Studio replace Grok Bot for overnight portal research?

GitHub Copilot is a coding assistant in supported editors. Confirm it on GitHub's current pages. It does not replace a named bot that clicks a site with no API while the laptop is shut. Copilot Studio is a builder inside Microsoft's ecosystem. Confirm on Microsoft's current Studio pages whether your license includes a runtime that can sign into arbitrary sites overnight. If it does not, the matching object for that founder job is Grok Bot on one shared cloud computer, with a charter that forbids outreach and forbids borrowing other bots' sessions.