Grok Build CLI Accused of Uploading Entire Repos
WesEklund · x · 2026-07-13
A post refuted the claim that "this is by design," citing external analysis indicating that the Grok Build CLI uploads the entire repository as a git bundle to the backend, rather than just the files actually read in the current session.
Key risks include:
- The entire repo might be uploaded even if prompted to "not read any files"
- It may contain complete history and all tracked files
- Even files like .env could be included
The author advises against using it on sensitive or private repositories, recommending isolated environments, strict .gitignore configurations, and testing first. They also mentioned that the team is working on improving transparency and options.
More from coding & agent
- Coding agents are heading toward an AI-writes, AI-reviews, human-approves workflow — aftahi_ai · 2026-07-22
- oMLX 0.5.2 adds Mac menu-bar stats, low-bit decode kernels, and faster downloads — awnihannun · 2026-07-22
- GitHub review bot hits its PR limit and forces a 39-minute cooldown — DanielLockyer · 2026-07-22
- Max reasoning effort appears to be mobile-only in Codex Remote, not desktop — GabGarrett · 2026-07-22
- A Reddit demo argues online stores should expose carts and pricing through MCP — gelembjuk · 2026-07-22
- Open-source AI SDK provider routes Vercel apps through a local Codex subscription — lgrammel · 2026-07-22