Grok Build open-sources code and resets usage limits for users

XAI open-sourced its coding agent Grok Build on July 15, 2026, after the tool was caught syncing entire code repositories to the cloud even with privacy settings enabled. The company permanently deleted all previously uploaded user data and disabled future data retention, while resetting server-side usage limits to allow local execution without cloud-imposed caps. The move addresses privacy concerns and positions Grok Build as a competitive alternative in the crowded AI coding assistant market.

Grok Build open-sources code and resets usage limits for users xAI's coding agent goes fully open-source after privacy controversy, deleting all previously uploaded user data in the process xAI just did something unusual for a company in the AI arms race: it gave away the code. Grok Build, the company’s terminal-native coding agent, is now fully open-source, with its codebase available on GitHub under xai-org/grok-build. Server-side usage limits have been reset for all users, and the tool can now run locally without cloud-imposed caps. But the headline move, open-sourcing, is really a cleanup operation dressed as generosity. The release comes after Grok Build was caught syncing entire code repositories to the cloud, even when users had privacy settings enabled. What happened and why it matters Grok Build launched in beta around May 2026 as a CLI-powered coding assistant built on xAI’s Grok model. It’s written in Rust and now runs on Grok 4.5, the model xAI released on July 8, 2026. During scrutiny of the CLI’s behavior, users discovered that Grok Build had been syncing complete repositories to the cloud. Not snippets. Not metadata. Entire repos. This happened regardless of whether users had toggled privacy settings on. Elon Musk responded with what amounted to a scorched-earth promise on data retention. His statement that “zero anything whatsoever will remain” was designed to leave no ambiguity. All previously uploaded user data has been permanently deleted, and data retention has been disabled going forward. The open-source release on July 15, 2026, is the structural fix. By letting users run Grok Build locally, xAI removes itself from the data pipeline entirely. The competitive chess move hiding inside a privacy fix The AI coding assistant space is getting crowded fast. Anthropic’s Claude has deep coding capabilities. OpenAI’s tools are embedded across enterprise workflows. Google’s Gemini is pushing into developer tooling. By resetting usage limits alongside the open-source launch, xAI is also removing the friction that typically gates adoption. Previously, heavy users would hit server-side caps that throttled their access. Now, running locally means the only limit is your hardware. Andrew Milich, who leads the Grok Build project, has positioned the tool as a “terminal-native” agent. Open-sourcing the Rust codebase means developers can now audit exactly what the tool does, modify it for their workflows, and verify that no data leaves their machine. The code is available at x.ai/open-source in addition to the GitHub repository. Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy https://cryptobriefing.com/editorial-policy/ .