Important to clarify that this was not the Grok agent deciding to read the files.

I don't think the LLM had anything to do with this decision at all. It looks like the Grok tool starts a session by deterministically kicking off a full upload of the user's current repository (and maybe their directory if not version tracked? Not clear if this user had previously run "git init" in their home directory) to Grok's servers.

One possible "innocent" explanation could be that xAI then run vector embedding on every file to help later provide the right context. I don't think thats a worthwhile tradeoff here, especially since other popular coding agents get by just using grep/ripgrep run locally.

That is not an innocent explanation, any more than someone breaking into your house to adjust your thermostat.

Yeah sounds like semantic indexing that cursor (pending acquisition by spacex/xAI) does.

https://cursor.com/docs/agent/tools/search

Also decent embeddings models could run locally and just trickle through the user folder if that was so necessary.

This should be the first comment here.

Too many replies here are done before reading it. It is not "just another agent does the agent thing". It is a deliberate choice of the Grok Build team to have a toggle from the server to let the program to upload your entire codebase to a Google Cloud Storage bucket. It is not an agent decision, the program is written by the Grok team, can be dissembled and seeing the logic wild-open.

Jesus ... I feel a Bill Hicks sketch coming on ...

[flagged]

[flagged]