Earlier quoted context omitted.
more like it allows them to steal your trade secrets, app designs, internal business knowledge, or even just replicate whatever code/app/tool/process you had. what was your private code, becomes their code now.
Possibly, but people were worried about this with cloud hosting when it first came out, and it turned out to be a total nonissue.
What xAI's Grok build CLI sends to xAI: A wire-level analysis
11–20 of 251 posts
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#12"It uploads the whole repository — every tracked file's content plus git history — independent of what the agent reads" Holy cow!!!! I mean I kinda expected Elon would do something like this to try to catch-up.. but this is extremely concerning. This is precisely the reason, even though their pricing is competitive and grok-4.5 is actually good enough, I chose not to go with them.
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#13Earlier quoted context omitted.
more like it allows them to steal your trade secrets, app designs, internal business knowledge, or even just replicate whatever code/app/tool/process you had. what was your private code, becomes their code now.
Possibly, but people were worried about this with cloud hosting when it first came out, and it turned out to be a total nonissue.
But AI is literally all about stealing and reselling content under the protection of "AI did it" and "whoopie, we'll take a slap on the wrist". It's reasonable to assume all of the frontier companies are doing this to the maximum extent they can get away with.
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#14Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#15One reason to want to upload the entire codebase is that it allows them to have the model inspect the codebase during "thinking" without going back to the client to do real tool calls. It's not a really great reason, because what's the downside of going back to the client? But that's the best reason I can think of.
more like it allows them to steal your trade secrets, app designs, internal business knowledge, or even just replicate whatever code/app/tool/process you had. what was your private code, becomes their code now.
Running any query in Claude or Codex could result in the AI reading/uploading any file in your codebase.
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#16One reason to want to upload the entire codebase is that it allows them to have the model inspect the codebase during "thinking" without going back to the client to do real tool calls. It's not a really great reason, because what's the downside of going back to the client? But that's the best reason I can think of.
more like it allows them to steal your trade secrets, app designs, internal business knowledge, or even just replicate whatever code/app/tool/process you had. what was your private code, becomes their code now.
This is why I keep a separate repo for important parts that I do not want competitors to get access to, and only use ai on dumb parts which I don't care if get leaked tomorrow.
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#17"It uploads the whole repository — every tracked file's content plus git history — independent of what the agent reads" Holy cow!!!! I mean I kinda expected Elon would do something like this to try to catch-up.. but this is extremely concerning. This is precisely the reason, even though their pricing is competitive and grok-4.5 is actually good enough, I chose not to go with them.
Does OpenAI also have access to all github repos via partnership with microsoft?
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#18Earlier quoted context omitted.
more like it allows them to steal your trade secrets, app designs, internal business knowledge, or even just replicate whatever code/app/tool/process you had. what was your private code, becomes their code now.
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.
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
#19Now, where are the people afraid of the Chinese AI companies, who claim they are going to copy their very precious code...?
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#20will this endup in their "macrohard" (automate any business) project? will this endup in their "everything app"? guess you do not need to build "everything" yourself, when you can steal it.
If I had no morals and was running one of these companies I would be stealmaxxing before anyone notices the scale of the grift and regulations start getting in the way.
I'm not saying they are doing this, but that's what the incentives are lined up for.