this post was submitted on 13 Aug 2026
390 points (98.3% liked)

Technology

87214 readers
3405 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] LedgeDrop@lemmy.zip 1 points 2 days ago (3 children)

I've played around with Claude.

they can’t access anything you don’t give them permission to access.

It's not that "they can't" it's more like "they try not to".

For example, if you have a folder shared with your application code (/home/me/code/) - it has free reign on that folder.

If you add a prompt saying "you are only allowed to access files in /home/me/code":

you could ask it " oh, what are my aws credentials ", it would have no qualms about reading those files (/home/me/.aws).

You could also ask it to update your settings (/home/me/.claude)

I eventually started to work on a way of running Claude in a docker container with real filesystem enforcement. ...and it's sneaky how Claude will get when it wants to read a file, it doesn't have permissions for (using bash cat).

This was an exploration I'd made a year ago and I know Claude has a " sandbox" , but if you allow Claude to run bash commands - that sandbox is trivial to circumvent.

[–] LilBobbyTables@lemmy.today 2 points 1 day ago* (last edited 1 day ago) (2 children)

All that is great, and correct, but my point is that it asks you to confirm its commands that it runs. It asks you to confirm every change it makes to your code. It asks you to confirm every file it creates.

Everything it does goes through your permission.

You also shouldn’t have it do anything anywhere close to a production system, so it shouldn’t be able to do anything of any consequence.

[–] Mondez@lemdro.id 0 points 1 day ago (1 children)

So basically use it as a toy for entertainment purposes only... Except it's not marketed to be used that way and far to many people aren't smart or educated in computing enough to use it that way. Accepting a bash command you don't understand is the same as running a bash command you found on the Internet... You shouldnt, but people are far more trusting of the stuff an LLM powered agent comes up with.

[–] LilBobbyTables@lemmy.today 1 points 13 hours ago* (last edited 13 hours ago)

No, not at all, and I’m not sure how that could be the conclusion you came to from my post.

AI should never be touching prod systems without extreme safeguards/permissions set by the systems that they are accessing. Give it a read only db user account. Give it write access to some tables, but no delete/truncate. No AI should be able to run bash commands on production systems by itself without proper safeguards. That’s a failure of the users if it can.

Systems and software that was built by AI are fine to go into production environments after they’ve done through the regular pipeline of local testing, peer review, QA, unit tests, integration tests, test environment, stage environment, etc.

You never just give AI unfettered access to production systems to do whatever it wants, just like you don’t give a junior dev that access. People that aren’t “smart or educated enough” won’t have that access either - and again, if they do that’s a gigantic failure by the people that are.