What xAI's Grok build CLI sends to xAI: A wire-level analysis
Summary
Analyzes the data that xAI's Grok build CLI sends back to xAI, examining network traffic for privacy implications.
Similar Articles
Grok Build CLI uploads your whole repo — full git history + .env secrets — to xAI's cloud, and the opt-out doesn't stop it (wire-captured)
A security analysis reveals that the Grok Build CLI tool uploads entire repositories, including full git history and .env secrets, to xAI's cloud, and the provided opt-out mechanism does not actually prevent this behavior.
xai-org/grok-build, now open source
xAI faced backlash after its Grok CLI tool was found to upload entire directories to its servers. In response, xAI deleted retained data, disabled default data retention, and open-sourced the entire Grok Build codebase under Apache 2.0 to regain user trust.
Grok uploaded my user directory to xAI's servers
A user claims that Grok, an AI model from xAI, uploaded their entire user directory containing SSH keys, password database, documents, and media to xAI's servers, raising serious privacy concerns.
@vista8: Had AI analyze and deconstruct the source code of Grok Build, full document here https://xiangyangqiaomu.feishu.cn/docx/OAoYdiZ1eoc2HTxmmZ3clWIPnLf…
User utilized AI (Codex) to analyze and deconstruct the newly open-sourced Grok Build source code, and shared the full analysis document.
Grok Build open sourced under Apache 2.0 license
Grok Build, a terminal-based AI coding agent from xAI, has been open sourced under the Apache 2.0 license. It runs as a full-screen TUI that understands codebases, edits files, executes shell commands, and more.