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
- Musk hails Grok Bot as 'incredibly competent chief of staff' as user automates inbox triage — elonmusk · 2026-10-27
- shadcn's /improve skill paired with Grok on SuperGrok Heavy for plowing through issues — shadcn · 2026-10-27
- Paradigm Launches Envoys: Your Claude Code and Codex on Your Research Graph, Free — tensorqt · 2026-10-27
- AXL launches remote MCP server exposing 1,284 sales and marketing APIs to Claude and Codex — EdTech_Padre · 2026-10-27
- GitHub's Thomas Dohmke ships Entire, a Git forge built for agent-human collaboration — carrycooldude · 2026-10-27
- OmarchyTV hits GitHub: Omarchy-style TV launcher with AI TUI and MCP — alexcovo_eth · 2026-10-27