Third-party tool
Grok Bot on Linux: official packages vs community port
What job it does
Community Linux packaging / port for people who want a desktop build outside or ahead of official channels — reference only once official packages exist.
Platforms
Linux (community). Prefer official deb / rpm / AppImage from x.ai/bot when available. FAQ fetch day 2026-09-04 lists Linux x64 and Arm64 as official platforms.
Install
First choice: download from https://x.ai/bot More downloads. Use Nichokas/grokbot-linux-port only as a community alternative after reading its README, version, and known rejection cases (very old unofficial builds such as 0.18 were refused during setup).
How it differs from the official app
Official packages come from x.ai/bot and update through the app. Community ports/AUR/COPR/Wine wrappers are not staff-supported. Empty ListMachines / local-exec issues on Linux are documented in this site’s troubleshooting playbooks — fix those before blaming packaging.
Use official packages first
On fetch day 2026-09-04 the xAI FAQ listed Linux x64 and Arm64 as official platforms, with deb, rpm, and AppImage under More downloads on x.ai/bot. That is the supported path. Pick the file that matches both your distro and uname -m: x86_64 is x64, aarch64 is Arm64. Install, open the app, and sign in with Cursor the same way as on Mac or Windows. The app checks for updates; you can also use Settings → Beta → Check for Updates. If the official package launches and the computer provisions, stop here — you do not need a community port. The step-by-step desktop order is on the install lesson.
When a community port is actually useful
Use Nichokas/grokbot-linux-port only after the official package fails on your distro, or when you are reading history about older unofficial builds. Very old community builds such as 0.18 were refused during setup. Do not mix an official install and a port in the same prefix and then wonder which binary is talking to the backend. Wine wrappers, random AUR/COPR copies, and reconstructed 0.18 trees are not staff-supported. Read the port README for the version it targets, then confirm that version is still accepted. If ListMachines is empty or local-exec fails, fix those with this site’s troubleshooting playbooks before you blame packaging.
Linux-specific limits that packaging cannot fix
The cloud computer still cannot attach local stdio MCP, whether you installed from x.ai/bot or a port. Remote HTTP MCP and the cloud browser remain the integration surface. Execution on Local Computer is a different permission: it runs on the Linux box in front of you after you approve it, and it is not a substitute for putting the Bot on a company VPN — staff have warned that installing a VPN client on the Bot computer can take the box offline. Device limits still apply: a Grok Bot login can count as a Cursor device, and the cloud workspace may count as another. Prefer official Recover / Update over Reset when the computer is briefly unreachable. After an Update Computer, apt packages and daemons are gone even if /workspace files survived — keep a short install list in a file and have the Bot rebuild it.
Risks
Non-official builds can be outdated, unsigned, or rejected by backend version checks. Do not mix community and official installs blindly. Local stdio MCP still cannot attach from the cloud computer regardless of packaging.
License and source
License. As declared in the upstream repository README
Open GitHub source Prefer official install Symptom-based fixes
Third-party tools can touch a local session. They do not replace Require Approval, secrets cards, or Recover/Update in the official desktop app.