Grok Build Open-Sourced as Default Retention Is Turned Off

On July 16, a wave of posts focused on updates to xAI-related coding/agent tool Grok Build. Multiple posts said Grok Build and its CLI repository had been made public and that usage quotas were reset for all users; on the same day, @SpaceXAI officially confirmed a privacy change: data retention is now off by default, and previously retained coding data will be deleted. The combination matters because it opens the implementation to developer inspection while also reigniting discussion about how the tool handles user code.

What was opened

According to posts from tetsuoai and others, the release was not limited to a thin wrapper: it included core Rust code for the TUI and agent runtime under the Apache 2.0 license. ns123abc said developers can now inspect pieces such as the agent loop, file tools, planning, the interactive TUI, terminal rendering, compaction, and the way goals and subagents are organized. Multiple posts also said the coding agent, CLI, and harness were all published, and that usage quotas were reset the same day.

What developers noticed

ns123abc described the release as open-sourcing agent infrastructure rather than just shipping another model feature. Via billyuchenlin, Simon Willison's initial look at the newly opened Grok Build CLI put the codebase at about 844,000 lines of Rust and highlighted a self-contained component that renders Mermaid diagrams in the terminal using Unicode characters. Those details shifted attention toward the engineering stack behind the product, not only its model behavior.

Privacy changes and debate

@SpaceXAI said the CLI had already supported disabling data upload, and that during the early beta, retention was on by default for non-ZDR users. The account said default retention is now disabled and that all previously retained coding data will be deleted. xiaohu linked the open-sourcing to earlier outside criticism that the tool uploaded users' codebases; however, within the provided material, the official, directly confirmed points are the retention-default change and the deletion of previously retained coding data.

2026-07-16 ~ 2026-07-17 · 35 related posts

Full story(3 episodes)→

2 near-duplicate retellings: ns123abc · nickcraske