Grok Build Accused of Secretly Scraping Local Repos
adrianscottcom · x · 2026-07-13
This quote post alleges that Grok Build wasn't just a simple bug, but that it actively scraped local repository contents in the background, quietly disabling the cloud upload channel only after being exposed.
The author emphasizes two points:
- Disabling uploads doesn't erase the .env files, git history, and other data that has already been leaked.
- If the system can remotely pause data scraping, it can just as easily resume it at any time.
Therefore, they demand a transparent explanation from xAI on how they plan to handle the data that was already uploaded.
More from coding & agent
- TRL adds Score Centering, a simple fix for RLHF training instability — lvwerra · 2026-10-27
- Precompute golden answers and match at runtime for exact wording control — colinmcnamara · 2026-10-27
- Dev argues there's still alpha in working with your coding agent interactively — alex_frantic · 2026-10-27
- Researchers launch AMA on patterns for safer AI agents used by citizen developers — Loose_Rip359 · 2026-10-27
- Gradio Adds In-Chat Human-in-the-Loop So ML Intern Pauses Before Training — Gradio · 2026-10-27
- Building Halo Infinite Forge maps with local LLMs, DCjson and Blender MCP — swagonflyyyy · 2026-10-27