AI/TLDR

xAI · 2026-07-15 · major

Grok Build open-sourced — xAI ships the Rust source under Apache-2.0

xAI released the Rust source for Grok Build, its terminal coding agent, under Apache-2.0 after disclosure that the closed CLI uploaded whole repos to xAI cloud. Developers can now audit the code and run it fully off xAI's servers.

xai-org/grok-build GitHub repository page for SpaceXAI's Rust coding agent

xAI's Rust TUI coding agent is now Apache-2.0 — devs can audit it, run it local, or fork it.

Quick facts

MakerxAI
LicenseApache-2.0
LanguageRust
Repoxai-org/grok-build
Runs onGrok 4.5
InterfacesTUI, headless CI, Agent Client Protocol
Installcurl -fsSL https://x.ai/cli/install.sh | bash

What is it?

Grok Build's full Rust source is now on GitHub at xai-org/grok-build under Apache-2.0. The repo ships the same fullscreen terminal UI, headless mode, and Agent Client Protocol integration that power xAI's coding agent behind Grok 4.5.

How does it work?

The codebase is a Rust workspace built via cargo run -p xai-grok-pager-bin (the binary is grok). It documents keyboard shortcuts, slash commands, MCP servers, skills, plugins, hooks, headless entry points, and sandboxing. First-party code is Apache-2.0; third-party crates keep their original licenses in THIRD-PARTY-NOTICES.

Why does it matter?

Grok Build was the only closed-source CLI among major-lab coding agents until the Cereblab wire-level teardown showed it uploaded whole repos and .env secrets to xAI cloud. Publishing the source lets developers verify what runs and route inference off xAI's servers — something the audit on the closed binary could not do.

Who is it for?

Developers who need to run an AI coding agent local-first, and security teams auditing what leaves their machine.

Frequently asked questions

Why did xAI open-source Grok Build now?
xAI open-sourced Grok Build on 2026-07-15 after security researchers showed the closed-source CLI had synced entire git repos, including .env secrets, to a Google Cloud bucket regardless of the user's privacy setting. Publishing the Rust source lets developers audit exactly what leaves their machine.
Can Grok Build now run fully local?
Yes. With the source open under Apache-2.0, developers can build Grok Build themselves, point it at a self-hosted or third-party inference endpoint, and take xAI's servers out of the loop. The prebuilt binaries at x.ai/cli/install.sh still call xAI's API by default.
What data did xAI say it deleted?
xAI stated that all Grok Build repo uploads previously synced to its cloud were wiped and that server-side retention was disabled going forward. Server-side usage limits were also reset for all users. The deletion claim has not been independently audited.
How does Grok Build compare to Claude Code and Codex CLI?
Grok Build is a Rust TUI that drives Grok 4.5, similar in shape to Claude Code and OpenAI's Codex CLI. The differentiator is that Grok Build is now the only major-lab coding agent shipping first-party source under Apache-2.0 — Claude Code and Codex CLI remain closed.

Try it

curl -fsSL https://x.ai/cli/install.sh | bash

Sources · 3 outlets

Tags

  • xai
  • grok
  • grok-build
  • coding-agent
  • cli
  • tui
  • rust
  • open-source
  • apache-2
  • agent-client-protocol
  • local-first

← All releases · Learn AI