3 ms·
TLDR: 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
by kardianos 3mo ago
TLDR: 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.
- AntonyGarand 3mo agoNot only files it wanted to access, but uploaded the whole directory. Relevant read: https://news.ycombinator.com/item?id=48877371 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.
- drakythe 3mo agoI'm not seeing the information about it having been run at $HOME, where are you seeing that?
- stronglikedan 3mo agoYeah, this is a lesson about learning how to use tools safely, not about tools abusing the user. The person that posted this probably blames the hammer when he hits his thumb.
- denysvitali 3mo agoNo. Ran `grok` in `$HOME` and the CLI uploaded the whole home content. This is not the LLM going rogue or reading all files.
- cheema33 3mo ago> TLDR: Ran grok in $HOME. Surprised agent read content of folder. Did it really need to read all of $HOME and everything under it?