Grok BotGuide

Linux

Grok Bot Linux setup failed

Grok Bot Linux setup failed on very old unofficial builds because those builds were rejected. The supported packages now are the official deb, rpm, and AppImage on x.ai/bot.

A community port, an AUR copy, or a Wine wrapper is not staff support. Fix the official package before you blame your network.

Official packages versus the community port

Why the native method fails

The native method is to keep a 0.18 tree that a forum post once offered, or to Reset the computer because setup says it cannot be reached. Staff said Can't reach your computer on Linux Grok Bot 0.18.0 was not the network. That old build was rejected. In that same reply they listed supported platforms as macOS, Windows, and iOS, and said a formal Linux desktop was not available yet. The xAI FAQ fetched for this handbook on 2026-09-20 lists Linux x64 and Arm64, with deb, rpm, and AppImage under More downloads. Both statements are in the record. The one to follow for a new install is the later FAQ: use the official package. A rejected 0.18 binary will still fail setup, and Reset cannot make the backend accept it.

Mixing an official install and a community port in the same prefix leaves two binaries and no way to see which one is talking to the account. Uninstall the extra one before you collect logs.

Steps

  1. Open x.ai/bot, then More downloads. Pick deb, rpm, or AppImage for the distro, and match the CPU. uname -m of x86_64 is the x64 build. aarch64 is Arm64. Sign in with the Cursor account that holds the plan. There is no separate Grok Bot account.
  2. The app checks for updates on its own. Settings, Updates, Check for Updates replaces the desktop app. It does not reset the cloud computer. The computer control is Update under Grok Bot's Computer, same as on Mac and Windows.
  3. Empty ListMachines, or local execution failing, on Grok Bot 0.30.0 for Linux is a known defect. Staff said a fix was already merged for a later desktop update. The interim workaround they gave: an unlocked system keyring, gnome-keyring or KWallet, fully quit leftover Grok Bot processes, then relaunch. Do not treat that as a packaging bug in the deb.
  4. If the official package launches and the computer view opens, stop. You do not need the community port. Use Nichokas/grokbot-linux-port only after the official package fails on that distro, and only after you read the README for the version it targets. Wine wrappers and random third-party repacks are outside staff support.

Limits

Local stdio MCP is unreachable from the cloud computer on every platform, including an official Linux package. Remote HTTP MCP or the cloud browser is the integration path. Execution on Local Computer is a different permission: it runs on the Linux machine in front of you after you approve it. It is not a way to put the Bot on a company VPN. Staff warn that installing a VPN client on the Bot computer can take the machine offline.

Always allow for local execution is desktop-only and can still fail to cover every shell, which is the local-computer page. Device limits still apply: a Grok Bot login can count as a Cursor device, and the cloud workspace may count as another, toward Too many computers. After Update Computer, apt packages and daemons are gone even if files in /workspace survived. Keep a short install list in a file. This page does not publish distro-specific install commands beyond the package types the FAQ names.

FAQ

Staff said Linux was not supported. Is that still the install advice?

That reply was about rejected 0.18 builds. The xAI FAQ fetched 2026-09-20 lists Linux x64 and Arm64 as official. Use the package on x.ai/bot, not the old unofficial build.

ListMachines is empty on 0.30.0. Do I reinstall the deb?

Staff called it a known bug with a fix merged for a later desktop update. Interim: unlock gnome-keyring or KWallet, quit leftover processes, and relaunch.

Can I attach a local MCP server from the Linux box?

Not a stdio or localhost server. The cloud computer cannot reach it. Use public HTTPS MCP, or the cloud browser.

Will a community AUR package get staff help?

No. Prefer the official deb, rpm, or AppImage. Community ports are not staff-supported, and very old ones were rejected at setup.

Does updating the Linux app reset the computer?

No. Check for Updates restarts the app. Update under Grok Bot computer is the separate control, and it removes installed packages on the computer.

Related

  • Linux packages — Official packages versus the community port.
  • Install — The same Cursor login as Mac and Windows.
  • Local computer — Keyring, daemons, and Always allow.
  • DNS error — If the official build is fine and the hostname will not resolve.

Sources

  • Get started
  • Linux 0.18 rejected
  • Linux local execution
  • Local MCP