Is your code repository “running naked”?

Grok Build CLI has been exposed for default behavior that packages your entire local Git repository and uploads it to the cloud—possibly including files you never asked it to read.
Let’s have the junior sister explain it in the simplest way: what a CLI is, why it needs to read your code, what exactly happened in this controversy, and whether you can still use it now.
1️⃣ What is a CLI?
CLI = Command Line Interface (command-line interface). It’s that black-box style way of operating where you type commands in the terminal.
2️⃣ What is the Grok Build CLI?
It’s xAI’s terminal-based AI coding assistant. You don’t need to open a web page or an IDE—just type grok in your terminal, and it can help you read code, modify code, plan projects, and run commands.
3️⃣ Why does AI need to read your code repository?
Because it’s a coding agent, and to complete complex tasks it must understand the whole project:
- Relationships across multiple files
- Project architecture and dependency relationships
- Git commit history (so it knows what was changed before)
- Supporting parallel work with sub-agents
The official claim is: to give the AI “complete context,” so it can work like a real engineer—not just look at the single file you currently have open.
4️⃣ The core of the controversy is “how it reads”:
Researchers who captured network traffic found that the Grok Build CLI “by default packages and uploads your entire local Git repository” to xAI’s cloud (including files never read by the AI + the full git history).
Even if you explicitly say in the prompt “do not read any files,” it still uploads the entire repository.
Also, if it reads your .env file, the keys inside it would be sent as well.
This “default full upload of the repository” mechanism is “not clearly explained” in official documentation, which is the main reason for the discussion.
5️⃣ Event timeline:
• July 10–11: Security researchers found the above behavior by capturing network traffic
• July 12: Related analysis spread on Reddit and X
• Early morning of July 13: xAI quickly pushed a server-side configuration update that limited the repository-wide upload behavior
So far, the official Grok account has replied, acknowledged that this mechanism exists, and said it has been adjusted based on feedback.
Core evidence Gist:

6️⃣ Current usage recommendations:
- For normal personal projects: you can keep using it, but it’s recommended to enable Plan Mode
- For projects containing sensitive information, company code, or real secrets: don’t use it for now
- Make sure to use .gitignore to strictly exclude sensitive files and directories
This incident also serves as a reminder:
In the AI era, data is very easy to “run naked.” When using AI coding tools, never ignore what data behind the scenes it reads and uploads.