Grok Bot Is a Cloud Teammate. The Local CLI Runs the Site
Grok Bot, launched August 11, is a cloud teammate with its own VM. The local grok CLI is what can actually operate a production checkout like helloai.
xAI is selling two desktop agents this month, and they are not the same product. Grok Bot, launched as an early beta on August 11, 2026, is a macOS, Windows, and iOS app whose Bots share a persistent cloud computer with a browser, filesystem, and terminal. Grok Build is the local grok command: Grok Build 1.0 left beta on August 7, the changelog is at 1.0.5 as of August 15, and the marketing page now says it is powered by Grok 4.6. Calling both Grok Bot is how you confuse a rented VM with the checkout you actually ship from.
Grok Bot's pitch is always-on teammates. Official docs say jobs keep running when you close the laptop, Bots can use apps with no API, and they can watch a workflow once and save it as a routine. Several Bots share one user-scoped cloud computer at /workspace — a convenience and a security boundary. Access is SuperGrok Plus and Heavy, or Cursor Pro+, Ultra, and Teams, signed in with a Cursor account. There is no Linux desktop app. Local-computer execution is a separate setting that defaults to ask-every-time; the computer itself is still in the cloud. That is closer to Claude Cowork than to a repo-native CLI.
A site like helloai.com is a git checkout: data files, tests, a commit, and deploy keys that should not sit on a shared Bot VM. Grok Build is built for that shape. Install is one curl on macOS, Linux, and Windows. It has plan mode, subagents, worktrees, AGENTS.md, skills, hooks, MCP, git, and headless grok -p for scripts. The Apache 2.0 tree is xai-org/grok-build. Claude Code and Codex CLI already occupy this niche. Grok Build is xAI's entry, not a new category.
The trade-offs are not subtle. Cloud Bots work at 3 a.m. and can click a CRM with no MCP server. They require cloud data storage, refuse Cursor's Legacy Privacy Mode, and share logins across every Bot on the account. Local CLIs stop when the session stops unless you wrap them in CI, and they will git push if you let them. Neither is local inference: both call Grok 4.6 in xAI's cloud. The locality is the harness. The weights still leave the building.
This week Grok 4.6 hits two weeks on the public API at $2/$6 with a 500K window. Code Arena WebDev lists grok-4.6-high at 1629, a hair above Claude Fable 5 at 1626; text overall is still Preliminary at 1461. Grok Bot is two weeks old. The useful question for a site like this is no longer whether xAI has a frontier model. It is whether you want the teammate on a computer you rent, or the agent in the directory you already deploy from.