Grok CLI vs Grok Build — release-asset architecture probe Captured first-hand by the Cosyra team on 2026-07-20 (UTC). WHAT THIS SHOWS --------------- Two unrelated terminal coding agents both install a binary named `grok` into $HOME/.grok/bin. Their Linux ARM64 support is exactly inverted. This log is the raw evidence for that claim: HTTP status codes for each published release asset, plus repository metadata read the same day. Reproduce it yourself with the commands shown above each block. [1] GROK CLI — github.com/superagent-ai/grok-cli (community, NOT xAI) ----------------------------------------------------------------------- $ curl -s https://registry.npmjs.org/grok-dev | jq -r '.["dist-tags"].latest' 1.1.7 $ for a in grok-linux-arm64 grok-linux-x64 grok-darwin-arm64 grok-windows-x64.exe; do curl -sIL -o /dev/null -w '%{http_code} '"$a"'\n' \ "https://github.com/superagent-ai/grok-cli/releases/download/grok-dev%401.1.7/$a" done 404 grok-linux-arm64 <-- NOT PUBLISHED 200 grok-linux-x64 200 grok-darwin-arm64 200 grok-windows-x64.exe Consequence: install.sh maps `aarch64` -> `arm64` (arch case, lines 84-87) and then requests an asset that does not exist. On Termux (aarch64) the documented install cannot complete. The cause is a missing artifact, not a libc mismatch. [2] NPM PACKAGE RENAME — cite grok-dev, never @vibe-kit/grok-cli ------------------------------------------------------------------ $ curl -s https://registry.npmjs.org/grok-dev | jq -r '.["dist-tags"].latest as $v | "\($v) \(.time[$v])"' 1.1.7 2026-05-15T10:13:54.518Z $ curl -s https://registry.npmjs.org/@vibe-kit/grok-cli | jq -r '.["dist-tags"].latest as $v | "\($v) \(.time[$v])"' 0.0.34 2025-11-27T15:21:17.949Z <-- STALE, ~8 months behind [3] GROK BUILD — github.com/xai-org/grok-build (official xAI) ----------------------------------------------------------------- $ curl -s https://x.ai/cli/stable 0.2.106 $ for a in linux-aarch64 linux-x86_64 macos-aarch64; do curl -sIL -o /dev/null -w '%{http_code} '"$a"'\n' "https://x.ai/cli/grok-0.2.106-$a" done 200 linux-aarch64 <-- SHIPS ARM64, the inverse of Grok CLI 200 linux-x86_64 200 macos-aarch64 [4] REPOSITORY METADATA (gh api, 2026-07-20) ---------------------------------------------- $ gh api repos/superagent-ai/grok-cli grok-cli: 3,314 stars MIT TypeScript created 2025-07-14 pushed 2026-07-06 $ gh api repos/xai-org/grok-build grok-build: 20,734 stars Apache-2.0 Rust created 2026-07-14 pushed 2026-07-20 $ gh api repos/xai-org/grok-cli {"message":"Not Found","status":"404"} <-- xAI has no repo named "grok-cli" SUMMARY TABLE ------------- Grok CLI Grok Build Repo superagent-ai/grok-cli xai-org/grok-build Affiliation community, not xAI official xAI Created 2025-07-14 2026-07-14 (exactly 1 yr later) License (harness) MIT Apache-2.0 Language TypeScript / Bun Rust Stars (2026-07-20) 3,314 20,734 Command installed grok grok (also links `agent`) Install directory $HOME/.grok/bin $HOME/.grok/bin npm package grok-dev none Linux arm64 asset 404 — not published 200 — first-class target Both models are proprietary and billed by xAI; only the harnesses are open. Caveat recorded honestly: whether `npm i -g grok-dev` yields a working `grok` on aarch64 has NOT been tested by us. Grok CLI targets Bun and depends on @opentui/core and agent-desktop, which ship native components. We state that path as unverified rather than guessing in either direction.