logoalt Hacker News

grey-area • today at 6:59 AM • 7 replies • view on HN

Biggest questions here, which I think need answering:

Should Claude have access to user details? I’d say no, unless explicitly entered manually into a chat.

Should Claude have access to anything outside of the sandboxed project files without explicit permission? I’d again say no.

Should Claude have internet access without a clear log of all requests made?

Instances of Claude should be heavily sandboxed and kept away from user data, far more so than they are now. The impression given by the desktop UI is that the LLM only has access to things explicitly added to a project.

This impression is not true, as evidenced by Claude pulling data from other sessions outside a project even when not instructed to (I’ve seen this a few times), and in this case pulling your email (from account details, user contacts? I wonder where it got that info?).

None of this information should be available to Claude, by design, not by instruction. Using text instructions to try to limit these machines is an incredibly flawed approach and should not be necessary for important info. Anthropic should have the model access completely locked down by controls at the os level over file access, not open by default. That is how to fix this.

If a user wants to open access that should be an explicit choice from them, with a warning about possible consequences.


Replies

jstanley • today at 8:35 AM

> Should Claude have access to user details?

This is hard to avoid. All it needs to do is make a git commit and look in the git log and it will find out who you are.

➕ show 2 replies
wodenokoto • today at 11:52 AM

> Should Claude have access to anything outside of the sandboxed project files without explicit permission? I’d again say no.

This is definitely a question that sounds straightforward but isn't. Like, when I ask antigravity to commit to git, it gets an error because ~/.gitconfig is outside the sandbox.

➕ show 1 reply
daitangio • today at 8:38 AM

I am developing a project to sandbox AI coding agents at very basic level: https://github.com/daitangio/take-ai-control

I would also like to add a list of allowed site, closing all the others, but it is quite complex from docker.

It is not safe like a isolated VM, but it is a good trade-off to avoid letting a model to wipe out all your home directory or looking into other files in your disk.

As always feedback is wellcomed

➕ show 2 replies
rplnt • today at 7:53 AM

I usually run claude sandboxed, but had to do something on Windows and didn't want to be bothered. Opened a project, asked something generic about it and in the first response Claue tells me it tried to fetch all URLs it found it in it and what errors were in responses. Cool stuff.

dachris • today at 8:32 AM

Yes, they need to be heavily sandboxed. On my machine, LLMs are constrained to docker containers for me, no exceptions.

Launch script checks that I can't accidentally run them with a working dir too far out (i.e. user folder).

csomar • today at 3:39 PM

The models are very aggressive in finding the info they need. I had one find some API key somewhere so that it can make requests. Sloppy on my part of having API keys not related on the hard drive but was not expecting the model to burn my harddrive in a lookup for api keys.

YetAnotherNick • today at 7:29 AM

No question needs answering. If you want to run claude code inside sandboxed environment, it's not that hard and there are lot of options including official[0].

[0]: https://code.claude.com/docs/en/sandboxing

➕ show 2 replies