This is one of the reasons why native proprietary coding agent runners like claude-code, codex, grok-build etc are so dangerous for privacy… you just don’t know what “secret sauce” they’ll add in the next update… It’s much safer to use something like opencode and use models via their API… however, the tradeoff is that it will never perform as well as it does in their native agent runners…
What xAI's Grok build CLI sends to xAI: A wire-level analysis
31–40 of 251 posts
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#32This is one of the reasons why native proprietary coding agent runners like claude-code, codex, grok-build etc are so dangerous for privacy… you just don’t know what “secret sauce” they’ll add in the next update… It’s much safer to use something like opencode and use models via their API… however, the tradeoff is that it will never perform as well as it does in their native agent runners…
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#33This is one of the reasons why native proprietary coding agent runners like claude-code, codex, grok-build etc are so dangerous for privacy… you just don’t know what “secret sauce” they’ll add in the next update… It’s much safer to use something like opencode and use models via their API… however, the tradeoff is that it will never perform as well as it does in their native agent runners…
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#34This has to be the most successful mass surveillance campaign of all time
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#35Earlier quoted context omitted.
If you’re worried about this why are you using a third party AI in the first place? Running any query in Claude or Codex could result in the AI reading/uploading any file in your codebase.
key point: Grok is not even using the files they upload. they send home entirety of codebase that they do not even use for user AI queries. and why use cloud AI for coding? how is this even a question in 2026? if you don't, you can't compete with somone who does use it.
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#36Earlier quoted context omitted.
Does OpenAI also have access to all github repos via partnership with microsoft?
It would be _extremely_ surprising if private repos were available via that contract. Corporations wouldn't use GitHub at all if anyone other than those given direct access had read/copy permission.
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#37Earlier quoted context omitted.
Does OpenAI also have access to all github repos via partnership with microsoft?
It would be _extremely_ surprising if private repos were available via that contract. Corporations wouldn't use GitHub at all if anyone other than those given direct access had read/copy permission.
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#38I will say, a majority of the code I'm writing now is fully through an online LLM. If a company wanted to reconstruct a project I'm working on, they could just replay all of the tool calls from their logs, if they decide to retain the data (I did this locally once to recover a project that I mistakenly clobbered in Git).
Still, this is a big overstep IMO. At the very least, they should make it clear in their terms of service and privacy policy, and not hidden through legalese. Not all usage of Grok Build will be through their enterprise plan which offers ZDR.
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#39The simplest way to disable uploading your repo is disabling it in the config. [harness] disable_codebase_upload=true
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#40[flagged]