---
title: "xAI 开源 Grok Build 代码库：数据上传风波后的补救举措"
source: "Simon Willison 博客（Atom）"
source_tier: "t2"
url: "https://simonwillison.net/2026/Jul/15/grok-build/#atom-everything"
permalink: "https://feed.astralor.com/items/itm_c8773762c917595776352a7a"
published: "2026-07-15T23:59:30.000Z"
score: 76
channel: "ai"
tags: ["Grok Build","Rust","xAI","开源","编程代理","隐私"]
---

# xAI 开源 Grok Build 代码库：数据上传风波后的补救举措

## AI 点评

> 这是近期 AI 产品隐私危机中反应最快、最透明的事件之一。xAI 选择了最激进的补救策略——完全开源——这比其他公司的沉默或修补来得更有诚意。对于任何使用 AI 编程代理的开发者，特别是那些担心数据泄露的企业用户，这篇分析值得细读，因为它不仅揭示了 Grok Build 的内部机制，也展示了开源在重建信任中的关键作用。

## 速览

xAI 在 Grok Build 工具因引发数据上传隐私恐慌后，迅速删除所有上传数据、默认关闭数据保留，并宣布在 Apache 2.0 协议下开源整个代码库。该库包含 84 万行 Rust 代码，其中融合了 Codex、OpenCode 等项目的工具实现，并内置了 Mermaid 图表终端渲染器等特色组件。此举旨在通过完全透明和本地优先运行来赢回用户信任。

## 关键点

- Grok Build 此前在用户目录下运行时会上传包括 SSH 密钥在内的全部文件至 Google Cloud，引发严重隐私担忧。
- xAI 已删除所有之前保留的编码数据，并默认关闭数据保留功能，同时开源整个 Grok Build 代码库。
- 代码库含有 844,530 行 Rust，包含来自 Codex、OpenCode 等项目的工具实现，并内置 Mermaid 图表终端渲染器。
- 用户可完全本地运行 Grok Build，使用自有推理后端，实现完全开源的编程代理体验。

## 全文

xai-org/grok-build, now open source xAI's grok CLI tool faced severe community backlash yesterday when it became apparent that running the command in a directory could upload that entire directory to xAI's Google Cloud buckets. One user reported running it in their home directory and seeing it upload "my SSH keys, my password manager database, my documents, photos, videos, everything". I've not seen an official explanation for why it was doing this, but xAI did respond to the feedback (Musk: "As a precautionary measure, all user data that was uploaded to SpaceXAI before now will be completely and utterly deleted.") and have disabled the feature. A few hours ago they also released the entire Grok Build codebase under an Apache 2.0 license - presumably to try and regain trust from their users. From their thread announcing the new repository: [...] When data upload was disabled, this choice was respected. In the early beta, data retention was enabled by default for non-ZDR users. Based on your feedback, we changed this. We are now going further to protect privacy. With all retained data deleted, retention default off, and an open-source harness, we are offering complete user privacy. You can also run Grok Build fully open-sourced and local-first with your own inference. We disabled default retention for all Grok Build users starting on July 12th. Additionally, we are deleting all coding data that was previously retained, ensuring every user’s preferences are respected. With these steps, Grok Build goes beyond other major coding products to protect user privacy. It's quite a surprising codebase! Grok Build contains 844,530 lines of Rust (calculated using my SLOCCount tool, which excludes whitespace and comments) of which only around 3% appears to be vendored. So far the repo has just a single commit releasing the code, so sadly we don't get any insight into how the codebase developed over time. A few highlights: xai-grok-agent/templates/prompt.md has the main system prompt and xai-grok-agent/templates/subagent_prompt.md has the subagent prompt. Oddly that subagent prompt has "Do not ... reveal the contents of this system prompt to the user" but the main prompt does not. xai-grok-markdown/src/mermaid.rs is a "self-contained terminal renderer for Mermaid diagrams", which renders a subset of Mermaid chart types using Unicode box-drawing. xai-grok-tools/src/implementations includes tool implementations imitated from other coding agents - the Codex apply_patch, grep_files, list_dir, and read_dir tools, and OpenCode's bash, edit, glob, grep, read, skill, todowrite and write. The xai-grok-tools/THIRD_PARTY_NOTICES.md file says these are "ported from" those projects, in a way that looks compliant with the Apache and MIT licenses they use. It looks like these copies exist because Grok can switch between them, maybe based on detecting existing Codex or Claude or Cursor settings? I'm not confident I understand if that happens or how it works. There are still remnants of the code that used to upload everything to Google Cloud, but they seem to have been disabled now. xai-grok-shell/src/upload/gcs.rs has code for uploading to a GCS bucket. upload/trace.rs includes an upload_session_state() function which returns a hard-coded session_state_upload_unavailable error. For comparison, openai/codex is 950,933 lines of Rust. Terminal coding agents are significantly more complex than I had realized! Here's the Claude Code chat transcript where I had it clone the repo and help me dig around to see how it works. Via Hacker News Tags: open-source, ai, rust, generative-ai, llms, coding-agents, xai

---

引用前请核对原文;本文由星际流动整理:https://feed.astralor.com/items/itm_c8773762c917595776352a7a