2026-08-27 · Tutorial
How to Download Grok Bot on Mac, Windows, Linux, iPhone or Android
Correction, 4 September 2026. When this page was written the Grok Bot docs listed no Linux desktop app and no Android app, and described the iPhone app as pause and resume only. The docs now list a Linux desktop app (x64 and Arm64, as a .deb, an .rpm or an AppImage) and an Android companion app for Android 9 or later, and the phone app can create bots, message them, approve steps, take over the computer and pause routines. On 4 September iPad was still not supported. The current platform list is on Grok Bot supported platforms and the Android app has its own page. As of 23 September 2026 the iOS app also runs on iPad (iPadOS 18 or later).
The Windows installer ran cleanly on Arm64, you signed in with the Cursor account you already pay for, and Grok Bot still looks like it never shipped.
That sequence is the normal failure. Search intent for download grok bot is transactional: a file, a store listing, a progress bar. The product fails one screen later, when the Cursor login that opens the editor refuses the bot because the plan is Hobby, the free one, or a SuperGrok subscription nobody linked.
This page is the download path with the eligibility gate in front of it. It is not the supported platforms reference list. It is not the argument for Grok Bot on Linux even though the cloud computer is Linux. Read those when you need the grid or the VM mix-up. Read this when you are about to click Get, and you need to know whether Get will open a product or an empty room.
Official desktop path: x.ai/bot. Official phone path: the iOS App Store search for Grok Bot, on an iPhone running iOS 18 or later, or Google Play on Android 9 or later. Do not follow a GitHub release, a Telegram zip, or a "Grok Bot for Linux" wrapper. Those are other software wearing this name.
Confirm the plan before you download grok bot, not after sign-in
The installer does not check whether you may use the product. It checks whether the binary can land on the disk. Sign-in is the real gate, and it runs against a Cursor identity, not against a clever download mirror.
Eligible plans, from the Grok Bot FAQ: every paid Cursor plan (Pro, Pro+, Ultra), Cursor Teams, and a linked individual SuperGrok, SuperGrok Plus or SuperGrok Heavy, plus a one-time trial (teams and enterprises). Eligibility widened on 21 August 2026 (xAI announcement). Launch-week posts that still describe a Mac-only Ultra product are stale.
Closed doors with similar names: Cursor Hobby, SuperGrok Lite, and SuperGrok Team or Enterprise, which cannot link. An individual SuperGrok subscription grants usage once you link it from the Grok Bot plan screen. Cursor Pro at $20 a month is the cheapest documented paid path for one person (Cursor pricing, checked 23 September 2026). Do not print a SuperGrok Heavy dollar figure. Holding Hobby plus a SuperGrok you never linked does not add up to an eligible identity.
| What you do first | What you learn | What you still do not know |
|---|---|---|
| Download, then sign in | Whether the binary launches | Whether the empty screen is a bug |
| Open the invoice, then download | Whether this identity is on the list | How the first bot should be bounded |
| Start a trial, then download | Whether you have a sampler | How large the credit is (unpublished) |
| Upgrade to Pro+, then download | That the paid door is open | That you still have no per-Bot spend cap |
The right first move is the invoice. Two minutes with the plan name beats forty minutes of reinstalling an Arm64 build that already worked.
Open x.ai/bot for desktop, or search Grok Bot on the iPhone App Store
There are two official clients, and they are not interchangeable.
Desktop: go to x.ai/bot and take the macOS, Windows or Linux build. macOS covers Apple silicon and Intel. Windows covers x64 and Arm64. Arm64 is first-class, not a stub (Grok Bot FAQ).
iPhone: App Store search for Grok Bot, iOS 18 or later. The phone app can pause or resume a routine and approve steps, but not edit one. Editing and testing a routine still need the desktop app; the phone can now show run history and delete a routine (mobile). A browser tab is not a third client. If a phone is your only device, you can download grok bot in the store sense and still be unable to edit or test a routine.
| Surface | Official door | After a healthy install you can | After a healthy install you still cannot |
|---|---|---|---|
| macOS (Apple silicon or Intel) | x.ai/bot | Create, edit, test, schedule, read history, delete | Pick a model, set a Grok Bot spend cap, see an audit view |
| Windows x64 | x.ai/bot | The same desktop jobs as macOS | The same missing controls |
| Windows Arm64 | x.ai/bot | The same desktop jobs as x64 | Prove eligibility. The binary does not do that |
| iPhone, iOS 18+ (also iPad, iPadOS 18+) | App Store search for Grok Bot | Approve steps, take over the computer, pause and resume, read run history, delete a routine | Edit or test a routine, teach by demonstration |
If the vendor page and the App Store disagree with a screenshot you saw on X, trust the vendor page. The product launched in beta on 11 August 2026 and the access list moved ten days later. Screenshots age faster than binaries.
Refuse unofficial builds even when search ranks them above the vendor
"Download grok bot" is a query unofficial pages love. They offer a zip, an Electron shell, a "Linux client", a mirror hosted on a file box, or a repo that asks you to paste a Cursor session into a community wrapper.
This site will not name those projects. Naming them is a link. A star count is not a substitute for docs.x.ai. If the file did not come from x.ai/bot, the iOS App Store listing, or Google Play, it is not the product this article is about.
Sign-in is a Cursor identity. A wrapper that captures that login has the account the cloud computer is assigned to. Do not debug a missing Linux package by handing that identity to a third party.
Grok Build went open source on 16 July 2026. An "open Grok" repo is a developer product. If the tree talks about SKILL.md or CLAUDE.md, you are not looking at Grok Bot. See Grok Bot vs Grok Build.
Match the plan name on your invoice to the eligibility list
Open the billing page you already pay. Read the product name, not the dollar amount you remember. Adjacent SKUs are designed to be confused.
| Name on the invoice | After you download and sign in | What to do instead of reinstalling |
|---|---|---|
| Cursor Hobby | The client can launch. Grok Bot is not included | Start the one-time trial, or move to an eligible paid plan |
| Cursor Pro, $20/mo | Eligible: the cheapest documented individual paid door | If it is not, you are on the wrong account or Privacy Mode (Legacy) is on |
| SuperGrok (individual) | Eligible once linked from the Grok Bot plan screen | Link from the right Cursor account. The link is permanent and does not stack with a Cursor plan |
| Cursor Pro+, $60/mo | This identity should be eligible | If it is not, you are on the wrong account or Privacy Mode (Legacy) is on |
| Cursor Ultra, $200/mo | Eligible | Do not buy Ultra only to get a "better bot." There is no model picker |
| Cursor Teams (self-serve) | Eligible: every member has access | Confirm you signed into the team identity, not a leftover Hobby login |
| Cursor Teams, Premium seat | Eligible, but no Premium seat is required | Same identity check. A higher seat can raise weekly usage; access is the same |
| SuperGrok Plus | Eligible once linked | Link the Grok account that holds Plus to the Cursor sign-in you use, not to a second Cursor Hobby |
| SuperGrok Heavy | Eligible, on the FAQ list | Confirm current price on the vendor page. Do not trust a roundup |
| One-time trial | Eligible as a sampler, limited usage | A lab, not a week of unrestricted agents |
Prices checked 25 August 2026 against cursor.com/pricing, Cursor team pricing, and x.ai/pricing. The live page wins.
Identity traps: a leftover Hobby Google login next to a Teams work login, or Privacy Mode (Legacy), which blocks Grok Bot on every plan (teams and enterprises). No installer repairs that setting. The Cursor account explainer covers the ownership chain.
Follow Priya from a Windows Arm64 installer to a blank product
Priya is product ops. Her machine is a Surface Laptop 7, Windows on Arm64. She already has Cursor Hobby because the editor is a decent notes app and she does not ship code. Thursday she searches download grok bot, opens x.ai/bot, and the installer runs without a complaint. Arm64 is listed. She reads that as "so I am in."
She signs in with the same Google SSO she uses for Hobby. The client opens onto an empty state that looks like a failed sync, or a line that this plan does not include Grok Bot. Arm Windows has burned her before: other apps shipped x64 and looked empty. She uninstalls, bookmarks a forum "ARM download," reinstalls the official build, and messages a teammate on Cursor Pro+ and Windows x64: "Grok Bot is broken on Snapdragon." He sends a working roster screenshot. Neither of them opens billing.
Friday morning the invoice still says Hobby. Hobby is not on the FAQ list. The Arm64 installer was never the defect. The identity was never entitled.
| Clock | What Priya does | Story she tells | What is true |
|---|---|---|---|
| Thu 18:05 | Installs from x.ai/bot on Arm64 | If the installer runs, I have the product | The installer only proves the OS is supported |
| Thu 18:12 | Signs in with Hobby Google SSO | Cursor already knows me, so bots should appear | Cursor knows a Hobby user. Hobby excludes Grok Bot |
| Thu 18:40 | Hunts an Arm-specific unofficial build | Official Arm support must be a stub | Official Arm64 is first class. She does not need a stub |
| Thu 19:10 | Compares with a Pro+ teammate on x64 | Snapdragon is the split | The split is the invoice, not the chip |
| Fri 09:20 | Reads Hobby on the bill, then the FAQ | I wasted an evening on a broken app | She wasted an evening on an ineligible identity |
The fix is boring: start the trial, move the identity to Pro, Pro+, Ultra or Teams, or link SuperGrok. She does not need a different Windows build. Inbox Triage and Standup Scribe are still drafts after the door opens.
Tell an empty home screen from a failed download
People collapse four failures into "the download did not work." Only one of them is a download.
| What you see | Likely cause | What would actually change it | What will not |
|---|---|---|---|
| Installer will not run | Wrong OS version: iPhone or iPad below 18, Android below 9 | A supported machine, or an OS update | A community wrapper |
| Installer runs, app will not launch | Local block: OS policy, broken package, store region | Retry from x.ai/bot or the App Store, check OS version | Changing Cursor plans |
| App launches, sign-in works, no Grok Bot | Ineligible plan or Privacy Mode (Legacy) | Trial or eligible plan, or turn that mode off | A second installer |
| App launches, roster exists, jobs fail later | Charter, connections, or usage, not the binary | A bounded first bot and a read of the run | Re-downloading the client |
Priya was row three wearing row one's costume. Arm64 support exists so that row one is not her problem. The costume is convincing because the empty state has no invoice number on it.
If the app will not launch, stay on the official file. If it launches and the product is missing, stop touching the binary: billing, then the FAQ list, then Privacy Mode (Legacy), then the wrong Cursor user. A failed download is a file problem. An empty product is an entitlement problem. Mixing them is how unofficial builds get a customer.
Linux, Android and iPad have official clients now
There is a Linux desktop app as of September 2026 (.deb, .rpm or AppImage). There is an Android app as of September 2026 (Android 9 or later), and the iOS app also runs on iPad (iPadOS 18 or later). The FAQ says so. In August the teams page answered "Is there a Linux desktop app?" with no; that answer is gone (teams and enterprises).
Do not confuse the Linux client with the Linux computer. The cloud computer is a managed Linux VM. The bot runs as a non-root user. That is the worker, not a .deb. The argument lives on Grok Bot on Linux. The grid lives on supported platforms. If your only machine is a Pixel or an iPad, you can finish the download and still not edit or test a routine. A borrowed Mac can be a control surface. Wine and a Windows VM are Windows clients with extra steps; on Ubuntu, take the .deb instead. Android has a companion app as of September 2026. iPad runs the iPhone app. Unofficial software is still not a plan.
Install the iPhone client as a remote pause, never as a workshop
An App Store install is a real download grok bot action. It is also the easiest way to think you have a pocket desktop.
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 (mobile). Teach by demonstration is unavailable on iPhone (skills, routines and automations).
Download the iPhone app if a desktop client (macOS, Windows or Linux) already exists, or will exist, somewhere you may use. As your only client it is a pause control for routines you cannot create. Approvals do not reverse work already completed (approvals, security and privacy). A late pause does not un-send mail. Do not connect Gmail on download day because the phone "will be the kill switch." Read least privilege for bots first.
Write the first bot on paper before the installer finishes
The download is about to give you a create button. The create button is how people attach Gmail, Slack, and a bank in the same sitting, because the empty roster feels like unfinished setup.
Write the job before the binary is done hashing. One role. One deliverable. A boundary that forbids send, pay, and publish. Paste it after eligibility is real, not as a reward for the installer.
Name: Download Day Clerk
Job: One public-source brief, then stop
You answer one question I name, using public pages only. Every
material claim has a URL. If you cannot open a source, write
blocked and stop. Do not continue browsing after the brief exists.
You run on the account computer, not on this laptop. Other bots
on this account can see files and browser sessions you create.
Never store tokens in files. Never sign into mail, chat, banks,
or admin consoles. Never create accounts.
Boundary: never send email, never post, never purchase, never
delete, never change IAM. If a task needs one of those, fail the
task and write the reason. Pause is not undo.
If I have not confirmed this identity is on a paid Cursor plan,
Cursor Teams, a linked individual SuperGrok, or the one-time
trial, do not start. Say ineligible and wait.
Change the question. Keep the refusals. Catalog shapes that already have the stop line: Inbox Triage, Chief of Staff Briefing, Lead Scout. None of them require you to connect a mailbox on the evening you fetched the client.
A routine belongs to one bot (max 50, 20 recent run records, deleted with the bot). Nothing is team-level. Keep the charter in a file you own.
Keep Gmail and payments off the computer on download day
All bots on the account share one persistent cloud computer assigned to the user, not to a bot. Each bot gets a screen. Screens are not security boundaries. Cookies, sessions, files, and CLI credentials are shared. Deleting a bot does not remove those leftovers (computer and apps, approvals, security and privacy).
Download day is when people "just connect Gmail to see if it works." That login lands in the shared browser. Every future bot can use it. A trial you abandon still leaves the session unless you revoke it. See Grok Bot and Gmail and the safety checklist. The installer succeeding is not a reason to hand the VM your mail.
Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording. Do not connect a payment surface to "test plugins," and do not print a plugin count from a news post. Connect nothing until the Clerk brief finishes without a login wall. Hosted MCP tokens stay with Cursor's backend. Files on the computer do not.
Prove the download with checks that can fail
A check that cannot fail is a pep talk. Run these until one of them hurts.
| Check | How you run it | What failure means |
|---|---|---|
| Official file only | The desktop binary came from x.ai/bot, or the phone app from an App Store search for Grok Bot | You are about to sign into other software. Stop |
| Invoice name is on the FAQ list | Hobby, SuperGrok Lite, and a SuperGrok nobody linked are treated as no | Fix billing, link SuperGrok, or start the trial before another install |
| Privacy Mode (Legacy) is off | Workspace setting, not the download UI | No client on any OS will help until that mode changes |
| The client OS is actually supported | macOS, Windows, Linux (x64 or Arm64), iPhone, iPad or Android | An old OS version is not a persistence issue. It is a no |
| After sign-in, you can create a bot on desktop | One named Clerk, no connections | If you cannot, this is entitlement or identity, not Arm64 |
| A sibling bot can see a file the Clerk wrote | Create a note from bot A, list it from bot B | You were about to treat screens as isolation. Do not |
The sibling-file check belongs before Gmail, not after. See it while the file is a sentence, not a session cookie. The isolation model is on one computer, many screens.
If every row passes, the download worked. You still have no model picker, no Grok Bot-specific spend cap, and a weekly allowance with no published dollar figure. Do not invent the allowance. Do not schedule a fleet because an icon appeared.
Answer the objection that downloading first is the cheap experiment
The strongest objection to this page is speed. The objector says the installer is free, the App Store listing is free, and you will know in four minutes whether Grok Bot "works on this machine." Checking plans first is ceremony. Priya should have installed, seen the empty state, and learned.
Parts of that are true. Confirming Arm64 support by running the official Windows build is a real test. Confirming that x.ai/bot serves a file is a real test. For someone already on Pro, Pro+, Teams, or a linked SuperGrok, download first is harmless.
The objection fails for the people who type the query. They are often on Hobby, or on a SuperGrok they never linked, because those are the plans they already hold for the editor or for chat. For them, a successful installer plus a failed entitlement looks like a broken product. Broken-product stories send people to unofficial builds, to Arm-specific mirrors, to Linux wrappers. The cheap experiment externalizes its cost onto the account.
Two minutes on the invoice beats an evening of architecture theories. The free trial is the sampler if you are not ready for Pro. Use that door on purpose. Do not discover you needed it after you blamed Snapdragon.
If you are already eligible, skip the lecture. Official door, the identity that holds the plan, a bounded Clerk, Gmail on another day.
Name the cases where a clean install still cannot help you
A perfect download cannot buy missing product. iPad only: the iOS app runs there (iPadOS 18 or later), but editing and testing a routine need a desktop. Linux and Android have had clients since September 2026. Borrow a desktop, wait, or change runtimes. Privacy Mode (Legacy): the binary is decoration. Per-bot credential isolation: one computer per account, screens are not a boundary. Audit view of bot actions: Enterprise only. Model picker: none, for members or admins. Grok Bot-specific spend cap: none, only the account-level On-demand monthly limit. Weekly allowance, then on-demand, with no published dollar figure (cost, spend cap). SKILL.md and CLAUDE.md: Grok Build, not this download.
If those are deal-breakers, a successful installer is still a failed purchase. Decide before the progress bar, while you can walk away without a shared-computer login on the account.
Send platform lookup and the Linux-computer confusion to the articles that own them
If you came here to see whether Windows Arm64 is real, or whether iPad will run the iPhone build: the grid is Grok Bot on Windows, Linux and iPad.
If you came here because the docs say Linux and your laptop is Linux: the split between client and cloud computer is Grok Bot on Linux.
If you came here because Cursor asked you to sign in and you do not write code: the ownership chain is why Grok Bot needs a Cursor account.
This article's job is narrower. Download grok bot from x.ai/bot or the iOS App Store search. Confirm trial, Pro, Pro+, Ultra, Teams, or a linked SuperGrok first. A clean Arm64 install is not proof of access. Put a boundary on the first bot before create feels like setup. See what a Grok Bot is and is Grok Bot worth it.
Keep reading: Grok Bot on Windows, Linux, Android and iPad: What Works, Grok Bot on Linux: There Is a Desktop App Now, Why Grok Bot Needs a Cursor Account, and How To Get Access.
Frequently Asked Questions
Can I download Grok Bot if I am on Cursor Hobby or Cursor Pro at twenty dollars?
You can fetch the official desktop binary and you can sign in. On Hobby, that is not the same as being eligible. Cursor Hobby, the free plan, does not include Grok Bot; every paid Cursor plan does, from Cursor Pro at $20. An individual SuperGrok counts only after you link it from the Grok Bot plan screen. The FAQ list is every paid Cursor plan, Cursor Teams, and a linked individual SuperGrok, SuperGrok Plus or SuperGrok Heavy, plus a one-time trial for individuals. If the app opens and the product still looks empty, read the invoice before you hunt an Arm64 mirror. The installer already did its job.
Where is the official download, and are GitHub or mirror builds safe to use?
Desktop clients come from x.ai/bot. The phone client comes from an iOS App Store search for Grok Bot on iPhone, iOS 18 or later. GitHub trees, Telegram zips, and "Grok Bot for Linux" wrappers are other software. This page will not name them and will not treat a star count as a substitute for docs.x.ai. Sign-in is a Cursor identity. Do not paste that identity into a community client because search ranked it above the vendor. Grok Build being open source does not make a random repo into Grok Bot.
Why did the Windows Arm64 installer work if I still cannot use Grok Bot?
Because Windows Arm64 is a supported desktop. The binary launching means your OS is on the list, not that your plan is. People on Cursor Hobby hit this constantly: the Surface install looks professional, Google SSO works, the roster never appears, and Snapdragon gets the blame. Compare the plan name to the FAQ. Start the trial, move to Pro, Pro+, Ultra or Teams, or link SuperGrok. Reinstalling will not promote Hobby. Unofficial Arm builds are how that confusion gets expensive.
Can the iPhone App Store listing replace a desktop download?
No. The iPhone app pauses and resumes routines, reads their run history and deletes them, and it can message Bots, approve steps and take over the computer for a login. Editing and testing a routine still need the desktop app client. Teach by demonstration is unavailable on iPhone. If a phone is your only device, you can complete a store install and still be unable to create the routines you would pause. Use the App Store listing as a remote stop button after a desktop client exists. A late pause also does not undo a send that already happened, so do not treat the phone as the reason it was safe to connect Gmail on download day.