July 11, 2026
Your repo called — it feels exposed
What xAI's Grok Build CLI Actually Sends to xAI
Users freak out after tests suggest Grok sends way more of your project than expected
TLDR: A detailed test claims xAI’s Grok coding tool can send whole project files, secret config files, and project history back to xAI by default. Commenters turned that into a full trust drama, with some calling it outright theft and others struggling to defend why any tool would need that much data.
The real fireworks here are not just in the testing, but in the comment section meltdown that followed. The report claims xAI’s Grok coding tool didn’t just send the little bits of code it needed to answer a question — it allegedly sent entire project files, secret settings files, and even past project history back to xAI’s servers by default. In plain English: critics are reading this as, “You asked for help, and the app may have packed up the whole house.” That instantly turned the discussion into a trust war, with one stunned commenter boiling it down to: “haha so they just stealing entire codebases?” Ouch.
And the community absolutely ran with that energy. Several reactions were less “hmm, interesting” and more full sirens, pitchforks, and Elon side-eye. One person called it “extremely concerning,” saying this was exactly why they avoided the tool despite liking its price and quality. Another went full meme mode, joking that maybe this is how the so-called “everything app” gets built: why make everything yourself when you can just take it? Brutal.
Not everyone was purely outrage-posting, though. One calmer voice suggested there could be a practical reason: if the system has the whole codebase, it can inspect it faster without repeatedly asking your computer for files. But even that defense came with a shrug — basically, maybe there’s a reason, but is it a good one? The vibe across the thread was clear: less product launch, more trust crisis with punchlines.
Key Points
- •The article claims captured traffic showed Grok Build CLI transmitted read file contents, including a `.env` canary secret, unredacted to xAI through both `/v1/responses` and `/v1/storage`.
- •It says the CLI uploaded the entire repository and git history via `POST /v1/storage`, even when the prompt told the agent not to read any files.
- •The article reports a test on a 12 GB repository where `/v1/storage` transferred 5.10 GiB while the model-turn channel transferred 192 KB, which the author presents as evidence of bulk codebase upload.
- •It identifies the storage destination as a Google Cloud Storage bucket named `grok-code-session-traces`, based on binary strings and captured metadata.
- •The article states uploads were enabled by default and remained enabled after disabling “Improve the model,” while also noting this does not prove xAI trains on the transmitted data.