Skip to main content
AI RADARSecurity
462•07/14/2026, 15:30•2 min read

Grok Build CLI Caught Uploading Entire User Repositories to Cloud

Grok Build CLI Caught Uploading Entire User Repositories to Cloud
Executive TL;DR30s read

Independent researchers discovered that Grok Build CLI uploads entire user git repositories to Google Cloud, raising concerns about data privacy.

Grok Build CLI Caught Uploading Entire User Repositories to Cloud

Independent researchers passed the system through a proxy interceptor and found that the client packages the entire tracked git repository along with the full commit history and uploads it to a Google Cloud Storage bucket named grok-code-session-traces.

This occurs regardless of which files the agent actually opened during its operation. For instance, on one of the test repositories with a size of 12 GB, the model request channel transmitted about 192 KB of traffic (which directly relates to the task), while the upload channel to storage transmitted approximately 5.1 GB. Files that the agent is explicitly forbidden to open also end up in the cloud.

SpaceXAI's response came only a few days later. They stated that they are "deeply concerned about user privacy" and that code and execution logs are never retained for accounts with Zero Data Retention enabled, while others were urged to use the /privacy command.

Musk separately stated that SpaceXAI will completely delete all previously uploaded data as a precaution. However, xAI has yet to explain why uploading the entire repository is the default setting.

Why it matters

Analysis

This situation highlights the importance of data privacy in modern technology. Data leaks can have serious consequences for users, making it crucial for companies to adhere to high security standards.

Discuss in community

Share your questions and insights with developers

Join Telegram
+5 Points
← Back to news feed

Related in Ecosystem

Practical guides, core terminology, and agent skills