Skip to content- Watching for: An xAI statement or a CLI update that scopes uploads and honors the "Improve the model" opt-out; independent reproduction of the wire capture; whether the uploaded data is used for training; any CVE or advisory.
Notes
- 2026-07-16: Researcher (cereblab) mitmproxy wire capture of Grok Build CLI grok 0.2.93 reports the CLI uploads the full working repository (every tracked file plus complete git history) to GCS bucket
grok-code-session-traces via POST /v1/storage, independent of what the agent reads. On a 12 GB test repo the storage channel moved 5.10 GiB vs 192 KB on the model-turn channel, and planted never-read files were recovered from the uploaded git bundle; .env secrets were unredacted. Disabling "Improve the model" did not stop upload (/v1/settings still trace_upload_enabled: true). Author states it does not prove xAI trains on the data. HN front page (487 pts), secondary coverage (GIGAZINE, byteiota). 2026-07-13: a separate account (HN 48892468) claimed the entire home directory was uploaded, widening the scope (single account, unverified). 2026-07-14: the author retested and reported the storage channel now uploads nothing, /v1/settings flipped to trace_upload_enabled: false / disable_codebase_upload: true server-side (not a client patch); no xAI statement. Covered 2026-07-14 Top stories (lead, developing). 2026-07-15: xAI open-sourced Grok Build as xai-org/grok-build under Apache-2.0 (~845k-line Rust workspace, external contributions rejected, issues disabled), stated it can now run fully local-first against user inference, reset usage limits for all users, and claims retained user data was deleted and retention disabled by default; Simon Willison notes disabled upload code still present in the tree and tools adapted from Codex/Claude. Covered 2026-07-16 Top stories (confirmed, Agentic coding). Watch for full removal of the upload paths, independent confirmation of the data-deletion claim, and local-inference forks.
Stories