Grok CLI uploaded the whole home directory to GCS
1–10 of 434 posts
Re: Grok CLI uploaded the whole home directory to GCS
#2TLDR: Ran grok in $HOME. Surprised agent read content of folder.
On the other hand, I specifically had grok try hard NOT to read a known key in the project dir (it only saw the first part using a tool, to verify it was present). So there's that.
Re: Grok CLI uploaded the whole home directory to GCS
#3I feel this is worse than running rm -rf on a root directory. Just saying.
Re: Grok CLI uploaded the whole home directory to GCS
#4You should assume by default for any AI agent that it will read anything. Even if you manually allow/deny and "restrict" it to a subdirectory I would still hold that assumption. Claude reads your ~/.bash_history too so when you ran something it can use that same command.
Re: Grok CLI uploaded the whole home directory to GCS
#5https://xcancel.com/a_green_being/status/2076598897779020159
Posting a complaint about Elon on Elon's platform and tagging him is ballsy. He tends to limit visibility of accounts who do that.
Re: Grok CLI uploaded the whole home directory to GCS
#6TLDR: Ran grok in $HOME. Surprised agent read content of folder. On the other hand, I specifically had grok try hard NOT to read a known key in the project dir (it only saw the first part using a tool, to verify it was present). So there's that.
Not only files it wanted to access, but uploaded the whole directory.
Relevant read: https://news.ycombinator.com/item?id=48877371
> The practical takeaway for users: your entire codebase leaves (uploaded) your machine unencrypted on each Grok Build invocation, not just files you ask it to read, and no visible setting stops it.
Re: Grok CLI uploaded the whole home directory to GCS
#7TLDR: Ran grok in $HOME. Surprised agent read content of folder. On the other hand, I specifically had grok try hard NOT to read a known key in the project dir (it only saw the first part using a tool, to verify it was present). So there's that.
I'm not seeing the information about it having been run at $HOME, where are you seeing that?
Re: Grok CLI uploaded the whole home directory to GCS
#8why do people give these LLMs full access to everything and then complain when it does somethign stupid? that is what sandboxes are for.
Re: Grok CLI uploaded the whole home directory to GCS
#9I feel this is worse than running rm -rf on a root directory. Just saying.
Much worse, instead of the data gone it's a data leak.
Those ssh keys can be used to access private servers
Re: Grok CLI uploaded the whole home directory to GCS
#10why do people give these LLMs full access to everything and then complain when it does somethign stupid? that is what sandboxes are for.
Other ones aren't this invasive with user data.