xAI open-sources Grok Build CLI, a massive Rust codebase with privacy concerns
xAI’s Grok Build dump gives Rust maintainers a rare look at an 85-crate, 1M-plus-line workspace. It also lands after backlash over uploaded repositories and secrets.
xAI open-sourced Grok Build on May 25, 2026, and the release is worth a look for Rust developers who care about real workspace design, not just another flashy CLI. xAI says the code is Apache 2.0 and describes Grok Build as SpaceXAI’s coding agent and TUI, with source that shows everything from context assembly to tool-call dispatch. For anyone building a large Rust agent, it is a working reference for how internal tooling, dependency boundaries, and build orchestration can be arranged across a sprawling repository.
The scale is the first thing that jumps out. The codebase landed in a single squashed commit and is described as more than 1 million lines of Rust across 85 crates. Community estimates pushed that even higher, to about 1.3 million lines across roughly 70 to 79 crates, with one widely repeated observation that about half the repository is tests. That is useful in a practical way because it shows how much of a modern Rust agent stack can be carved into crates, but it also shows how fast test organization becomes a maintenance problem when the workspace gets that large.
That problem showed up immediately. Early users reported compilation and test failures tied to Cargo versus Bazel differences in test handling. Elliot Arledge pointed out that Bazel’s per-target test builds tolerate a pattern that Cargo does not when a dependency is never compiled in test mode. For maintainers, that is the kind of failure mode that matters more than any launch headline, because it tells you where your build graph is lying to you and where your test coverage is not actually exercising what you think it is.
The open-source release also landed after a privacy fight that had already damaged trust in the CLI. Simon Willison tied the release to severe backlash after users realized the tool was uploading code. A wire-level analysis from Cereblab found that the CLI uploaded full Git repositories, including full history and secrets, to xAI storage on Google Cloud. That same analysis said xAI later disabled upload server-side with a disable_codebase_upload: true flag and added a /privacy opt-out, but treated that opt-out as a retention setting rather than a block on what gets sent.
That leaves Grok Build in an unusual place for Rust readers: it is not just a large public codebase to inspect, it is a live case study in what happens when a Rust agent stack has to survive build-system friction and privacy scrutiny at the same time.
This article was produced by Prism’s automated news system from verified source data, official records, and press releases, then run through automated quality and moderation checks before publishing. The system is built and supervised by the people who set the standards it runs under. Read our full AI policy.
Did this article answer your question?
