SpaceXAI open-sources Grok Build under an Apache 2.0 license, after the tool uploaded user repositories to SpaceXAI's Google Cloud bucket, causing a backlash
xai-org/grok-build, now open source (via) xAI's grok CLI tool faced severe community backlash yesterday when it became apparent …
Simon Willison's WeblogSimon Willison
Context & Ripple Effects
Grok Build was introduced in early beta as xAI’s agentic coding and workflow CLI, initially tied to SuperGrok Heavy access. The company had already positioned open-sourcing as part of Grok’s broader product strategy, including earlier model releases.
That posture is now being tested at the tool level: reports that the CLI uploaded user repositories to a Google Cloud Storage bucket prompted a community backlash, followed by halted uploads and a commitment to delete prior uploads. Releasing the code under Apache 2.0 makes the client behavior inspectable and modifiable after the incident.
First-order effects
Developers can inspect, audit, fork, and redistribute Grok Build under Apache 2.0 rather than relying solely on xAI’s representations about how the CLI handles repository data.
xAI must address trust damage from the upload behavior while prior uploads are being deleted and the tool’s data-handling path receives more public scrutiny.
Second-order effects
Teams evaluating Grok Build will likely make source review and network-behavior checks a prerequisite for adoption, raising the practical bar for agentic coding CLIs that touch private repositories.
Open-source availability can enable community patches or forks that alter data flows, but it also makes any remaining questionable defaults easier to identify and compare with competing developer tools.
Third-order effects
If repository-upload incidents recur across coding agents, provenance, outbound-data controls, and independently auditable clients could become core purchasing criteria rather than secondary privacy features.
The episode underscores a tension in AI developer tooling: open source can improve verifiability after a failure, but it does not by itself establish safe defaults or restore trust in hosted services.
The trend: Agentic developer tools are moving toward a trust-and-audit model in which repository access and telemetry behavior are as consequential to adoption as model capability.
In response to user questions about privacy: Since launch, Grok Build has fully respected zero data retention (ZDR). All users have always had the ability to disable data upload in the CLI. When data upload was disabled, this choice was respected. In the early beta, data
We've open-sourced Grok Build and have reset usage limits for all users. Open sourcing Grok Build allows anyone to support making a reliable and robust harness. Check out our code, including the Git repo for the Grok Build CLI. https://x.ai/...
I poked around in the just open sourced Grok Build CLI tool - 844,000 lines of Rust code! - and dug up a few interesting highlights, including a “self-contained terminal renderer for Mermaid diagrams” that renders them using Unicode box-art! — simonwillison.net/2026/Jul/15/ ...
SpaceXAI's Grok programming tool was uploading its users' entire codebase to cloud storage | Elon Musk says that all previously uploaded data will be deleted
'SpaceXAI's Grok Build AI coding tool was spotted packaging and uploading entire code repositories, “including files it was told not to open and secrets deleted from history."' www.theverge.com/ai-artificia...
we pinky swear we will delete the data we hoovered up in a country too corrupt to pass or enforce privacy laws whose regulators have been disemboweled 😇🥸