ash
6b180acd39
Fail clearly when curl/jq/python3 are missing, when the feed cannot be parsed, or when the PKGBUILD rewrite does not stick. A scheduled bump still commits PKGBUILD+.SRCINFO, tags v$pkgver, and pushes; a no-op is only an already-current pkgver.
grok-bot-bin
Unofficial Arch / CachyOS package of the official Grok Bot .deb. Temporary until upstream packages for Arch.
Not affiliated with Cursor / SpaceXAI. The app binary is unchanged; this only repacks it for pacman.
Install (build locally)
git clone https://git.s1d3sw1ped.com/s1d3sw1ped/grok-bot-bin.git
cd grok-bot-bin
makepkg -si
With an AUR helper against this git URL:
paru -S grok-bot-bin --aururl https://git.s1d3sw1ped.com
# or:
yay -S grok-bot-bin # after cloning locally / using a custom AUR mirror
Simplest reliable path on CachyOS today:
makepkg -si
Install from a release package
When CI has published a .pkg.tar.zst on the Releases page:
curl -LO 'https://git.s1d3sw1ped.com/s1d3sw1ped/grok-bot-bin/releases/download/v0.35.0-2/grok-bot-bin-0.35.0-2-x86_64.pkg.tar.zst'
sudo pacman -U grok-bot-bin-0.35.0-2-x86_64.pkg.tar.zst
Download first, then pacman -U the local file (LocalFileSigLevel = Optional). Do not pass the remote URL straight to pacman if signatures are required.
Custom pacman repo (optional)
After CI publishes a repo database under Releases (or Packages), add to /etc/pacman.conf:
[grok-bot]
SigLevel = Optional TrustAll
Server = https://git.s1d3sw1ped.com/s1d3sw1ped/grok-bot-bin/releases/latest/download
Exact Server= URL may change once the first repo DB lands; makepkg -si works regardless.
Updating
./scripts/update.sh reads Cursor's linux-x64 update feed, downloads the matching .deb, and bumps pkgver / _commit / sha256sums in PKGBUILD and .SRCINFO.
Scheduled Gitea Actions will do the same and build a release package.
Notes
/usr/bin/grok-bot(andsand) is a launch shim: unlessGROK_BOT_NO_UPDATE=1, it checks the latest Gitea release and maypacman -Ua newer.pkg.tar.zstbefore exec'ing/opt/Grok Bot/…. Network/API failures still launch the installed binary.- If the app menu still launches an old binary without updating, run
/usr/bin/grok-botonce from a terminal, orsudo pacman -Uthe newer.pkg.tar.zstfrom Releases — the menu must call the PATH shim, not/opt/Grok Bot/…. - Upstream Linux builds still have no in-app updater for the Electron app itself;
scripts/update.shbumps the PKGBUILD from Cursor's feed when packaging a new upstream version. chrome-sandboxis left non-setuid because the install path contains a space; user namespaces cover sandboxing on CachyOS.