Fix Grok Bot installed from Install > AI failing with HTTP 404 (omarchy/grok-bot 0.18.0 is too old)
I read issue omacom/omarchy#8070 in full with comments and both cited pull requests. The issue supports the cause. Its body states Omarchy 4.0.0-1, names https://pkgs.omarchy.org/stable/x86_64/grok-bot-0.18.0-1-x86_64.pkg.tar.zst, and says 0.18.0 404s against the computer API because backend_min_version is 0.24.0 and Linux has no in-app updater. The reporter's first attempt, omarchy#8075, switched the menu to the AUR and he closed it himself as the wrong layer, which is exactly the record's line that the menu entry is correct and the package was stale. The issue itself is closed as NOT_PLANNED with the comment Opened in error. Closing., so the record's note that nobody reported back in the thread is right. On the pull requests the record has the merge state right where the issue body does not: omarchy-pkgs#198 Update grok-bot to 0.24.0 merged on 2026-08-24T19:52:10Z, while #201, the one the issue body links as the fix, is closed unmerged. The whole cause paragraph is a restatement of #198's body, including the 0.24.0 floor, the noVNC token change at 0.20.0 and Unknown platform: linux-x64-user, and its diff confirms the packaging claims: pkgver 0.18.0 to 0.24.0, install -Dm755 "${srcdir}/grok-bot.sh" "${pkgdir}/usr/bin/grok-bot" with ln -s grok-bot "${pkgdir}/usr/bin/sand", and grok-bot.desktop installed. Both are still in the PKGBUILD on master today. Note the cause and the test evidence come from one person, the reporter and PR author, not from an independent confirmation.
Two things in the fix are wrong as of 2026-09-11. First the version. I fetched https://pkgs.omarchy.org/stable/x86_64/omarchy.db and it carries grok-bot-0.29.0-1, not the 0.24.0-1 the record reports, and the PKGBUILD on master is pkgver=0.29.0. The 0.24.0 figure was a dated observation and reads as a current claim on a published page. Second the plain Arch branch is false. The AUR does carry this app: grok-bot-bin and grokbot-linux-port-bin are both 0.47.0-1 and maintained, and the plain grok-bot AUR package is orphaned, flagged out of date, and pinned at 0.20.0-1, which is below the 0.24.0 floor and therefore still broken. That last one is a trap the record sends a reader straight into by saying the package exists only in the Omarchy repository. I rewrote the fix for both and added the ALPM guard and partial upgrade warnings, since the record gave a bare omarchy update with no note on what not to substitute.
Confirmed on this Omarchy 4.0.2-1 workstation: /etc/pacman.conf line 28 defines [omarchy] with Server = https://pkgs.omarchy.org/stable/$arch, so stable is the ring this machine tracks. /usr/share/omarchy/bin/omarchy-update-system-pkgs runs sudo env LC_ALL=C OMARCHY_UPDATE_PACMAN=1 pacman -Syu --noconfirm, so omarchy update really does sync and upgrade. The menu entry at /usr/share/omarchy/default/omarchy/omarchy-menu.jsonc line 235 now reads omarchy-install-and-launch 'Grok Bot' grok-bot grok-bot rather than calling omarchy-pkg-add grok-bot directly, but that wrapper execs a shell running omarchy-pkg-add grok-bot, so the symptom's description still holds and I left it alone. I could not exercise any of this: grok-bot is not installed here, pacman -Q grok-bot finds nothing, I have no sudo, and I have no account to authenticate a client against the computer API, so the 404 itself and the PR's upgrade test are taken from the source.
Symptom
Grok Bot installed through the Omarchy menu (Install > AI > Grok Bot, which runs omarchy-pkg-add grok-bot) does not work. The 0.18.0 client's local daemon restart-loops and every request to Grok Bot's computer API returns http_404. There is no in-app updater on Linux. Reported on Omarchy 4.0.0-1 on 2026-08-24.
Cause
Named by the reporter and confirmed by the merged package bump. Cursor floors the Grok Bot desktop computer API at client 0.24.0 (backend_min_version) and changed the noVNC token scheme at 0.20.0, so the 0.18.0 build in the Omarchy package repository can no longer talk to the service. The Omarchy menu entry is correct. The package it installs was stale.
Fix
The fix is omarchy-pkgs PR #198, merged 2026-08-24, which repackages Grok Bot 0.24.0. The stable package repository has moved on since: https://pkgs.omarchy.org/stable/x86_64/omarchy.db carried grok-bot-0.29.0-1 when fetched on 2026-09-11, and the PKGBUILD on master is at 0.29.0. Anything at 0.24.0 or above clears the backend_min_version floor, so an ordinary update is enough.
**Omarchy 4:**
omarchy update
That syncs and upgrades against the [omarchy] repository, which /etc/pacman.conf points at https://pkgs.omarchy.org/stable/$arch. Do not run pacman -Syu directly, because Omarchy's ALPM guard blocks it, and never pacman -Sy grok-bot, which is a partial upgrade. To take just this package now, sync and upgrade in one transaction:
OMARCHY_ALLOW_DIRECT_PACMAN=1 sudo pacman -Syu grok-bot
If Grok Bot was never installed, or you removed it, install it through Install > AI > Grok Bot, or directly:
omarchy-pkg-add grok-bot
0.24.0 renamed the binary from sand to grok-bot. The package keeps /usr/bin/sand as a compatibility symlink and ships grok-bot.desktop, so launcher entries keep working. Both are still in the PKGBUILD at 0.29.0.
**Plain Arch:** the Omarchy repository is not the only source. The AUR carries maintained builds, grok-bot-bin and grokbot-linux-port-bin, both at 0.47.0-1 on 2026-09-11:
yay -S --noconfirm aur/grok-bot-bin
Avoid the plain grok-bot AUR package. It is orphaned, flagged out of date, and sits at 0.20.0-1, which is below the 0.24.0 floor, so it has the same http_404 failure the Omarchy 0.18.0 package had. Building the official Linux .deb yourself also works. PR #198 pins https://downloads.cursor.com/grokbot/stable/<commit>/linux/x64/Grok_Bot_<version>.deb, and that PKGBUILD is the reference for the Wayland wrapper flags and the sand compatibility symlink.
Verify
pacman -Q grok-bot
ls -l /usr/bin/grok-bot /usr/bin/sand
pacman -Q prints grok-bot 0.24.0-1 or newer. The PR's own test on Omarchy/Hyprland: after pacman -U over a live 0.18.0, the app reported appVersion=0.24.0, the local daemon stayed up, and no new http_404 appeared in its logs. Nobody in the issue thread itself reported back after the bump.
Sources
- https://github.com/omacom/omarchy/issues/8070
- https://github.com/omacom/omarchy-pkgs/pull/198
- https://github.com/omacom/omarchy-pkgs/pull/201
- https://pkgs.omarchy.org/stable/x86_64/omarchy.db
- https://github.com/omacom/omarchy/pull/8075
- https://github.com/omacom/omarchy-pkgs/blob/master/pkgbuilds/grok-bot/PKGBUILD
- https://aur.archlinux.org/packages/grok-bot
- https://aur.archlinux.org/packages/grok-bot-bin
- https://aur.archlinux.org/packages/grokbot-linux-port-bin