xAI
xAI Launches Grok Build, a Terminal-Native Agent CLI to Rival Claude Code
Elon Musk’s xAI on Thursday released the early beta of Grok Build — a terminal-resident agentic CLI powered by Grok 4.3 — pitching directly at the developer surface area already contested by Anthropic’s Claude Code and OpenAI’s Codex CLI. The three-CLI race is now official.
Grok Build, announced Thursday morning and immediately available in early-access beta, is xAI’s first dedicated coding agent and its first product positioned head-on against the frontier-lab tools that have come to define the agentic-development workflow. The CLI runs entirely in the terminal — plans projects, writes and edits files, runs shell commands, and spawns subagents — and is powered by Grok 4.3, the new reasoning model that pairs xAI’s sixteen-agent “Heavy” architecture with a two-million-token context window. Up to eight Grok Build agents can run concurrently on a single workstation, sharing a project graph and coordinating through a central planner.
Pricing makes the competitive intent unmistakable. Grok Build sits inside a new SuperGrok SuperHeavy tier listed at $299 per month, with an early-adopter discount that brings it to $99 per month through the launch window. The underlying model is exposed via API at $0.20 per million input tokens and $1.50 per million output tokens — below Anthropic’s and OpenAI’s comparable tiers, and structured to make spawning eight parallel agents economically defensible rather than a luxury. xAI has not committed to a public release date for the wider SuperGrok rollout, but the company’s announcement notes that all SuperGrok Heavy subscribers will be migrated to the SuperHeavy tier at no additional cost during the migration window.
The competitive picture this creates is the cleanest three-way frontier-lab race the developer-tools market has seen. Anthropic ships Claude Code as the canonical example of the genre; OpenAI ships Codex CLI as a parallel offering tightly integrated with the broader Codex platform; xAI now ships Grok Build with an explicit reference to both. The three tools differ in session model, plugin architecture, and pricing posture, but they share the central insight that the terminal — not the IDE, not the chat window — is the surface where serious agentic coding actually happens. Developers who had been forced to pick a side or run two tools in parallel now have a third option, and the lab that owns the cheapest credible CLI is positioned to absorb the most attention from the long tail of independent developers.
Two technical bets distinguish Grok Build at launch. The first is the Heavy architecture itself: rather than scaling a single reasoning trace deeper, Grok 4.3 fans out sixteen parallel agents at the model level, each exploring a different reasoning path, with a meta-aggregator selecting the best output. That choice was already visible in Grok 4.3’s chat results; what Grok Build does is expose the same pattern at the developer-workflow level, letting users spawn up to eight CLI agents that can each in turn fan out internally. The second bet is the two-million-token context window. For repository-spanning refactors and multi-file plans, the practical headroom matters more than the headline rate; xAI is wagering that developers will pay a premium for never having to think about context boundaries during a working session.
The questions Grok Build leaves open are the ones that always determine whether a new CLI gets adopted. Plugin ecosystem maturity — both Claude Code and Codex CLI have shipped meaningful hook and plugin surfaces over the past six months — will determine how quickly third-party tooling stacks form around the new entrant. Stability at eight-parallel-agent throughput will need real-world testing before the headline number translates into trusted everyday use. And the question of whether xAI’s safety posture and content policies cause friction in enterprise procurement cycles — an issue that has dogged Grok’s consumer chat product — will play out over months, not days. But the launch itself settles the strategic question. The three frontier labs now ship terminal-native coding agents, and the competition for the developer’s default shell prompt has formally begun.