Alternative installation methods: version direct links, silent install, and Linux packages
The previous lesson covered the main path: open the download page, get the latest version, install it. But when you want to pin a specific tested version, install unattended on a batch of computers, or have upgrades follow the package manager on Linux, the main path falls short—this lesson covers the three alternative paths the official documentation provides for scripted retrieval of the Grok Bot installer: version direct links, Windows silent install, and Linux packages. 8 minutes to walk through them all.
What you'll be able to do after this lesson
- Use a single
curlcommand with the official release source to find the current version number and installer URL (2026-11-20 tested: 1.2.3) - Download a specific version of the Grok Bot installer using the versioned direct-link template (all macOS / Windows platforms)
- Complete a Grok Bot silent install:
Grok_Bot_{version}_Setup.exe /S, and know that it installs into%LOCALAPPDATA%\Programs - Install
.deb/.rpmpackages on Linux (signed repository configured automatically) or run the AppImage directly - Upgrade Grok Bot on Linux with
apt/dnfcommands, and useapt-mark holdto control upgrade timing
Your current predicament
- The company requires everyone to install the same tested version, but the download page always only shows the "latest version"
- IT needs to install Grok Bot on dozens of Windows machines—you can't have someone click "Next" on every single one
- On Linux, all software goes through apt / dnf, except Grok Bot, which requires downloading an AppImage, dropping it on the desktop, and managing updates yourself
When to use this technique
When you need to:
- Pin and download the exact version you tested, instead of always the "latest version"
- Fetch URLs with a script and bulk-download installers
- Bulk deployment on Windows with an unattended installation process
- Install via the package manager on Linux and control upgrade timing yourself
And you don't want to:
- Open the download page and click through manually on every computer
- Have the version jump to new releases uncontrolled after installation—Linux deb / rpm is the only installation method where upgrades are decided by your package manager
🎒 Prerequisites
- Completed the 1.3 installation: 5 minutes to get the desktop version installed—the main path is already working, and this lesson is entirely about alternative paths
- Know your platform and architecture: macOS (Apple silicon / Intel), Windows (x64 / Arm64), Linux (x64 / Arm64)
- Able to run commands in a terminal (Terminal on macOS / Linux, PowerShell or cmd on Windows)
- For company deployments: confirm which deployment tool you use (Intune, Jamf, Configuration Manager, Ansible, etc.) and prepare a pilot device
Core idea
The problem with the main path: the download page only lists the "current installer," and the app checks for updates on its own after installation. The alternative paths solve two things—version control (install the version I tested) and bulk installation (unattended).
The official documentation provides a "release feed" for scripted downloads: one JSON URL per platform, https://api2.cursor.sh/updates/api/download/stable/{platform}/sand, containing version, commitSha, downloadUrl (Linux additionally has debUrl / rpmUrl).
Comparison of the four paths:
| Path | How to get the installer | Who manages upgrades after installation | Who it's for |
|---|---|---|---|
| Download page (previous lesson) | cursor.com/download/bot | App checks for updates automatically | Individual users who always use the latest version |
| Version direct links | Look up the version in the release feed + direct-link template | App checks for updates automatically | Those who want to pin a specific version |
| Windows silent install | Download the Setup via direct link .exe + /S | App checks for updates automatically | IT bulk deployment |
Linux .deb / .rpm | debUrl / rpmUrl from the release feed | your package manager | Linux users / ops |
Linux also has an AppImage format, whose upgrade mechanism works like macOS / Windows—the app checks on its own—so when managing fleets of machines, the official recommendation is to prefer packages over AppImage.
One fact you must know first: the desktop app's update check cannot be turned off. The official documentation states clearly: for macOS, Windows, and AppImage installs, there is no device policy, installation parameter, or dashboard setting that can disable the update check; if your version is more than 14 days old and a newer version exists, the app will block you with a full-screen Update required. So "pinning a version" pins which version you install, not which version the app stays on. The only exception is the Linux deb / rpm: the app does not upgrade itself; new versions arrive via the package manager.
Follow along with me
The three routes are independent of each other: individuals pinning a version follow step 1–2, IT installing on Windows follows step 3, and Linux users follow step 4–5. Step numbers are consecutive to make cross-referencing easy.
Step 1: Look up the current version and download URLs from the official release source
Why: The download page always only offers the "latest version"; both scripted downloads and version pinning require getting the "current version number + exact file URL" first, and the official release source provides it all at once.
curl -s https://api2.cursor.sh/updates/api/download/stable/darwin-arm64/sandReplace {platform} in the URL with your platform:
{platform} | Platform |
|---|---|
darwin-arm64 | macOS, Apple silicon |
darwin-x64 | macOS, Intel |
win32-x64-user | Windows x64 |
win32-arm64-user | Windows Arm64 |
linux-x64 | Linux x64 |
linux-arm64 | Linux Arm64 |
You should see: a full line of JSON (2026-11-20 tested, macOS Apple silicon):
{"downloadUrl":"https://downloads.cursor.com/grokbot/stable/darwin-arm64/1.2.3/Grok_Bot_1.2.3.dmg","rehUrl":"https://downloads.cursor.com/remote-releases/a5927fa2ba82336a29f9343babd28b4c903abbb0/vscode-reh-darwin-arm64.tar.gz","version":"1.2.3","commitSha":"a5927fa2ba82336a29f9343babd28b4c903abbb2"}The response may also contain other fields (such as rehUrl in the test); they aren't needed for installing the desktop app, so below we only look at the fields we need.
Field reference:
| Field | Meaning |
|---|---|
version | the current version number (2026-11-20 tested 1.2.3, subject to what you see when you query) |
commitSha | The commit this build corresponds to; the Linux download URLs contain it |
downloadUrl | Installer URLs: macOS .dmg, Windows Setup .exe, Linux AppImage |
debUrl / rpmUrl | Linux only: URLs for the .deb and .rpm packages |
- I got
versionanddownloadUrl, and I know which{platform}to query for my platform
Step 2: Download a specific version of the Grok Bot installer using the versioned direct link
Why: Every macOS and Windows version keeps a fixed-format direct link. Replace {version} with the version you want and you can download it — this is the foundation of "pinning a tested version".
# macOS,Apple silicon
https://downloads.cursor.com/grokbot/stable/darwin-arm64/{version}/Grok_Bot_{version}.dmg
# macOS,Intel
https://downloads.cursor.com/grokbot/stable/darwin-x64/{version}/Grok_Bot_{version}_x64.dmg
# Windows x64
https://downloads.cursor.com/grokbot/stable/win32-x64/{version}/Grok_Bot_{version}_Setup.exe
# Windows Arm64
https://downloads.cursor.com/grokbot/stable/win32-arm64/{version}/Grok_Bot_{version}_Setup.exeFor example, download the macOS Apple silicon installer for 1.2.3 (the URL is the value of downloadUrl from the release source):
curl -LO https://downloads.cursor.com/grokbot/stable/darwin-arm64/1.2.3/Grok_Bot_1.2.3.dmgYou should see: the download starts for an installer whose file name contains the version number, such as Grok_Bot_1.2.3.dmg.
⚠️ Linux: don't apply this template
Linux packages are not under the version-number path, but under the commitSha path (https://downloads.cursor.com/grokbot/stable/{commitSha}/linux/x64/ or .../linux/arm64/). Don't assemble the URL yourself — copy the full URL from the Linux release source's downloadUrl, debUrl, rpmUrl; step 4 has a tested example.
💡 The right way to pin a version
The official documentation doesn't state how long old-version direct links are kept, and a pinned build is only available while it's still supported. To pin a version, store the tested installer in your own software repository or MDM package storage, and deploy from your own copy going forward — every new device then gets the same build.
- The installer download finished, and the version number in the filename matches what I wanted
Step 3: Silently install Grok Bot on Windows (/S)
Why: During bulk deployment, you can't have someone clicking "Next" on every machine. Grok Bot's Windows installer supports the silent flag /S — this is the official documentation's deployment guidance for IT.
Run in the directory containing the installer (PowerShell or cmd), replacing the version number with the one you downloaded:
Grok_Bot_1.2.3_Setup.exe /SThree details you must know:
| Detail | Explanation |
|---|---|
| Per-user install | Installs into the current user's %LOCALAPPDATA%\Programs, not the machine-wide Program Files |
| Deploy in the user context | Because it's a per-user install, MDM pushes must run in the user context; it cannot run as SYSTEM |
| Pilot first | The official documentation requires testing the install on one pilot device before a full rollout |
You should see: no installation wizard pops up; after a short wait, Grok Bot appears in the Start menu, with program files under %LOCALAPPDATA%\Programs.
- The silent install succeeded on the pilot device, and Grok Bot opens from the Start menu
💡 No MSI / PKG
The official FAQ states clearly: the released installers are only macOS .dmg, Windows Setup .exe, and Linux .deb / .rpm / AppImage. If your management tool requires MSI or PKG format, wrap the .exe / .dmg inside the format it requires.
Step 4: Install the deb / rpm package on Linux (or run the AppImage directly)
Why: deb / rpm is the only Linux install method where "upgrades follow the package manager" — the official documentation also recommends packages over AppImage for managed fleets of machines.
Get the package URL from the Linux release source (use linux-x64 for {platform}; on Arm64 machines use linux-arm64, and the URL path becomes /linux/arm64/). 2026-11-20 tested (1.2.3, x64):
# AppImage(downloadUrl)
https://downloads.cursor.com/grokbot/stable/a5927fa2ba82336a29f9343babd28b4c903abbb2/linux/x64/Grok_Bot_1.2.3.AppImage
# deb(debUrl)
https://downloads.cursor.com/grokbot/stable/a5927fa2ba82336a29f9343babd28b4c903abbb2/linux/x64/grok-bot_1.2.3_amd64.deb
# rpm(rpmUrl)
https://downloads.cursor.com/grokbot/stable/a5927fa2ba82336a29f9343babd28b4c903abbb2/linux/x64/grok-bot-1.2.3-1.x86_64.rpmNote the filename: the deb / rpm package name is lowercase grok-bot — that's the package name used in the upgrade command in step 5.
Pick the install method matching your system:
| Your system | Which package to install | How to install |
|---|---|---|
| Debian / Ubuntu | .deb | Install with your existing configuration management tool (Ansible, Puppet, Chef); for a single machine, use the system package manager to install the downloaded file |
| Fedora / other RPM systems | .rpm | Same as above |
| Any distribution | AppImage | Download and run directly, same as the previous lesson |
The official deployment documentation targets enterprise bulk scenarios and doesn't provide single-machine install commands; after installing, focus on the verification point below.
You should see: after installation completes, the signed repository file appears —
- Install
.deb:/etc/apt/sources.list.d/grok-bot.sources(signed apt repository) - Install
.rpm:/etc/yum.repos.d/grok-bot.repo(signed repository)
With these in place, when the device runs routine package upgrades it will also pick up new versions of Grok Bot — the upgrade command in step 5 relies on exactly this repository.
- The corresponding repository file appears (deb →
grok-bot.sources; rpm →grok-bot.repo)
Step 5: On Linux, upgrade Grok Bot with apt / dnf
Why: a Grok Bot installed via deb / rpm does not upgrade itself — the app does not install updates; new versions arrive through the package manager. This is its biggest difference from the macOS / Windows / AppImage installs.
Upgrade commands (the Update required full screen shows the same two, with a Copy command button):
# Debian / Ubuntu(deb 安装)
sudo apt update && sudo apt install --only-upgrade grok-bot
# Fedora 或其他 RPM 系统
sudo dnf upgrade --refresh grok-botYou should see: the package manager pulls the new grok-bot version and completes installation; after restarting Grok Bot, the version number in the account menu under Support → About changes to the new version.
To control "when to upgrade," the official docs offer two methods:
| Method | Operation | Effect |
|---|---|---|
| Hold the package | apt-mark hold grok-bot | The package is held; release it when you want to upgrade |
| Disable the repository | For deb, set Enabled: no in grok-bot.sources; for rpm, set enabled=0 in grok-bot.repo | New versions no longer arrive automatically; you distribute tested packages yourself |
Two details: the package rewrites these repository files on every install / upgrade and preserves your choices; if a held package's version gets too old, you will still see the Update required full screen — so don't hold for too long, and upgrade before the version loses support. If you hit Update required after disabling the repository, the screen will prompt you to instead download and install the latest package, with a link attached; restart Grok Bot after installing.
- After the upgrade commands finish, Support → About shows the new version number
Checkpoint ✅
- I can use the official release source to find the current version number and installer package URL (verified in 2026-11-20 as 1.2.3)
- I know the version direct-link templates for macOS / Windows; Linux package addresses live under the commitSha path, copied from the release feed
- Windows silent install
/SI tried it on a pilot device, and it installed into%LOCALAPPDATA%\Programs - On Linux, after installing deb / rpm, the corresponding signed repository file appears
- I can upgrade grok-bot with
apt/dnf, and I also know the two control methods:apt-mark holdand disabling the repository
Pitfall warnings
❌ Assuming "pinned version" = "the app stays on that version"
The official docs state clearly: for macOS, Windows, and AppImage installs, no device policy, installer argument, or dashboard setting can turn off update checks. Pinning a version only decides which version you install; after installation the app still checks for and prompts about new versions, and if the version is more than 14 days old with a newer version available, you get blocked by the Update required full screen. To control the upgrade pace yourself, only Linux deb / rpm works.
❌ Running the Windows silent install as the SYSTEM account
/S installs per user, into %LOCALAPPDATA%\Programs; running it as SYSTEM installs to the wrong place. The official requirement is to deploy in the user context, and to test on one pilot device before pushing fleet-wide.
❌ Assembling Linux direct-link version numbers yourself
macOS / Windows direct links use the {version} path, while Linux packages live under the {commitSha} path. Don't apply the macOS template to Linux — copy the full address from the Linux release feed's downloadUrl / debUrl / rpmUrl, and record the full URL together with the version number (official recommendation).
❌ Looking for MSI / PKG installers
Official FAQ: the released installers are only .dmg, Setup .exe, .deb / .rpm / AppImage — no MSI, no PKG. If your management tool requires these formats, wrap the .exe / .dmg into the format it requires.
Advanced tips (optional)
Company-wide bulk deployment: on macOS, push .dmg with Jamf Pro, Kandji, or Intune; on Windows, push .exe with Intune or Configuration Manager; on Linux, install packages with Ansible, Puppet, or Chef. Network allowlisting, SSO assignment, and admin controls are all covered in Enterprise IT deployment.
Check a device's current version: app account menu → Support → About; the dialog shows Version; Copy version info copies the version, release channel, and operating system in one click.
Version requirement quick reference: the minimum versions features require (e.g., Vault needs 0.75.2+) are in Versions and updates.
Lesson summary
✅ You can use a single curl command against the official release source to find the current version and the Grok Bot installer package URLs for each platform (verified 2026-11-20 as 1.2.3).
✅ You can download a specific version using the version direct-link templates (macOS / Windows); for Linux packages, get the exact address under the commitSha path from the release feed's debUrl / rpmUrl.
✅ You can silently install on Windows: /S, per-user install into %LOCALAPPDATA%\Programs, deploy in the user context, pilot first.
✅ You can install deb / rpm on Linux (signed repository configured automatically) or run the AppImage directly, and upgrade with apt / dnf.
Key information recap:
| Item | Key point |
|---|---|
| Official release feed | https://api2.cursor.sh/updates/api/download/stable/{platform}/sand |
{platform} Value | darwin-arm64 / darwin-x64 / win32-x64-user / win32-arm64-user / linux-x64 / linux-arm64 |
| macOS / Windows direct link | https://downloads.cursor.com/grokbot/stable/{platform}/{version}/Grok_Bot_{version}… |
| Linux package URL | …/stable/{commitSha}/linux/x64/ or …/linux/arm64/, copy from the release source |
| Windows silent install | Grok_Bot_{version}_Setup.exe /S, per-user install into %LOCALAPPDATA%\Programs |
| Linux upgrade | sudo apt update && sudo apt install --only-upgrade grok-bot / sudo dnf upgrade --refresh grok-bot |
| Current version | 1.2.3 (2026-11-20 tested from the official release source) |
Next lesson preview
The installation and upgrade paths are all covered. Wherever you get stuck—login loop, install failure, won't open—the next lesson is dedicated to fixing it: Getting Started Troubleshooting: Login Loop, Install Failure, Won't Open.
You will learn:
- Official self-check steps when sign-in gets stuck and doesn't complete, and fixes for the login loop (clear cookies, incognito window, wait 30–60 minutes)
- What to do when the app hangs on startup
- Update required where to click when the full screen appears
If everything goes smoothly, you can also jump straight to 1.5 Your First Bot and assign it its first task.