If you are running these agents outside of something like Coder or Codespaces I think you are doing it wrong.
Grok CLI uploaded the whole home directory to GCS
191–200 of 434 posts
Re: Grok CLI uploaded the whole home directory to GCS
#192So many of the replies are saying that they should've restricted access using .md files and whatnot. Is really any guarantee that they even follow those? It seems like even if you ask pretty please don't touch those files, there's a chance they will. So many people have just willingly installed spyware on their computers and big tech calls this the next big thing.
I don't understand why the AI world does this. We don't need new security. We have security at home. It starts with sudo -u restricteduser myagent Your OS knows how to restrict access to things, you don't have to trust a pinkey promise from a vendor.
Does this have the affordances to work well with a pretty standard agentic coding setup (e.g. claude code/codex) on macos?
I don't really have a good mental model of how ports/files/etc get exposed/permissioned across users. Containers and sandboxing seem much more common than agent-user accounts. Networking seems a little more complicated in the general case.
I roughly went the route of running apple's container-cli (separate vm/kernel per instance I believe) and mount the relevant home directory/projects and bind ports. Seatbelt/linux sandboxing seems simpler sometimes, but has its complications too.
Re: Grok CLI uploaded the whole home directory to GCS
#193TLDR: 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.
No. Ran `grok` in `$HOME` and the CLI uploaded the whole home content. This is not the LLM going rogue or reading all files.
Re: Grok CLI uploaded the whole home directory to GCS
#194The real solution to these kind of problems is sandboxing. I use podman through a bash script to launch a container whenever I want an agent to work on one of my repos. When done I just generate git patches and port back everything generated. In this way I'm not afraid of letting the agents totally lose on my computer.
Intricate sandboxing is a real solution in the same way bulletproof backpacks are a real solution to school shootings.
Re: Grok CLI uploaded the whole home directory to GCS
#195Important 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 server…
[flagged]
Re: Grok CLI uploaded the whole home directory to GCS
#196There are a distressing number of people in this thread who think that the agent should just be expected to do this. Yes, it is good to be paranoid, but also, the agent should never do this. Indicates horrific engineering practices at xAI.
What should it do then? The whole point of LLMs is that you can stop writing rigorous rules in a programming or config language with hard-to-learn syntax, and can resort to natural language instead. You pay for that with the chance for misunderstandings rising to similar levels as in human interaction. That's the tradeoff. Always has been, always will be.
Have the comments been combined with another story? Because this isn't about a LLM reading and sending contents of the file to be processed, but the agent framework uploading every single file in /home/user to a random server.
Re: Grok CLI uploaded the whole home directory to GCS
#197I am genuinely fascinated by this. I don’t like piling on especially with security vulnerabilities, but man how many red flags do you need to ignore? They won’t stop abusing us until we stop using their products.
> They won’t stop abusing us until we stop using their products. I don't use AI at all in my daily life. Work however will demand you use it. AI is not here to help people.
Not gonna argue about the utility of AI, but isn't the statement "AI is not here to help people" completely meaningless? AI itself is not "here" for anything; the problem is big tech doing big tech shit as always, not the current technology they're doing it with.
Re: Grok CLI uploaded the whole home directory to GCS
#198There are a distressing number of people in this thread who think that the agent should just be expected to do this. Yes, it is good to be paranoid, but also, the agent should never do this. Indicates horrific engineering practices at xAI.
How could it possibly work without something effectively the same as this happening? Either you run the LLM locally or you send it your files. Am I missing something?
Re: Grok CLI uploaded the whole home directory to GCS
#199Is the Grok CLI a 2 terabyte install? Did Elon dropship you an 8U rack of B200s? No? Well the model weights, the GPUs, and the context obviously all have to be in the same place, so “sending your project to them” is literally the only thing that could possibly happen, unless you think agents work by fucking magic . This is the biggest case of PEBKAC in history, maybe ever. This is the kind of confusion that Charles B…
That's not how any other coding harness/agent works. Why confidently comment on stuff you know nothing about?
Re: Grok CLI uploaded the whole home directory to GCS
#200This sort of stuff is precisely why running local models has to be the future. It's absolutely insane that we just send our code to the cloud like this, and we basically have to trust these companies with it.