Grok Build Exposed for Uploading Entire Codebases
charliermarsh · x · 2026-07-14
XBToshi pointed out that Grok Build has severe issues: during local use, it silently uploads entire repository data, Git commit history, and potentially sensitive files like .env.local and .dev.vars to the cloud.
According to the repost, tests showed that even without any tool-calls, about 12GB of repository data was sent to the cloud, with at least 5GB going to Google Cloud. The author described the behavior as "malware-like background code collection" and advised against using it for sensitive repositories.
More from coding & agent
- Dev builds interactive 3D product experience with GPT-6 Astra + Hyper3D Rodin — nikola_mr64990 · 2026-09-11
- Codex tip: use Sol with Astra and Luna sub-agents to save usage — pvncher · 2026-09-11
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11
- Cognition's SWE-2 uses a KKT duality argument in RL to shift the effort Pareto curve — YouJiacheng · 2026-09-11
- First-ever Three.js Conference lands in Paris, with a panel on AI-shortened design workflows — OdinLovis · 2026-09-11
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11