upvote

points

by dreadnip3 hours ago |
comments
upvoteby coldtea3 hours ago|
next
[-]
Isn't that what the people crying over their deleted or leaked data were doing too?

"I've been playing Russian roulette with a 1024 chamber gun for a year now, it's fine"

reply
upvoteby sixtyj1 hours ago|
parent|
next
[-]
Every driver thinks of themselves they are an excellent ones. Statistics has another data :)

If LLM agent wants to get out of dedicated folder where it’s supposed to work and tries to run a command, ppl should be always cautious. In fact, it is a sort of # access on live data.

Sudo/# is nice as you don’t have to ask for permissions, but I would recommend to do it only when you are fresh, fed, and not under stress.

I remember few times that I “accidentally” deleted or changed stuff I wanted to have intact… (Somebody would say that it is a skill issue :) But it was always when I was in hurry.

reply
upvoteby borzi3 hours ago|
parent|
prev|
next
[-]
I'm assuming this happens to the people vibe coding and running 30+ agents in parallel that are "coordinating" each other. I've never seen Claude do or even suggest anything remotely dangerous when I'm just giving it incremental tasks and reviewing the output.
reply
upvoteby coldtea2 hours ago|
parent|
[-]
>I've never seen Claude do or even suggest anything remotely dangerous when I'm just giving it incremental tasks and reviewing the output.

"I've never had a bullet hit me yet"

reply
upvoteby zarzavat2 hours ago|
parent|
next
[-]
I don't use yolo mode but if you allow your agents to both write code and run/test it, then it's basically equivalent to running in yolo mode anyway.

The other day I caught Claude including a rm -rf equivalent (fs.rmdir({ recursive: true, force: true })) in my code, to clean up temporary directories. It was fine, but that kind of code is only one misconfigured environment variable away from blasting away your $HOME.

reply
upvoteby drdec2 hours ago|
parent|
next
[-]
I've set up a second user on my machine just for running AI. That way I have the additional layer of OS protections against it doing something like that.
reply
upvoteby coldtea1 hours ago|
parent|
prev|
[-]
>if you allow your agents to both write code and run/test it, then it's basically equivalent to running in yolo mode anyway.

I don't. I manually check the code line by line before. And also run them in container anyway.

reply
upvoteby badestrand2 hours ago|
parent|
prev|
next
[-]
Whatever level of safety you are at, it's always easy to advocate for more. It's always a trade-off and in the end a matter of preference and risk-tolerance.
reply
upvoteby mlrtime2 hours ago|
parent|
prev|
[-]
I run in auto permission mode and it will run with 1 task and end to completion. On the rare event it needs to rmdir or rm -r a dir, the permission mode will stop the agent. Sometimes annoyingly... so its more like. "I've never had a bullet hit me yet inside a office building on the 42nd floor".
reply
upvoteby embedding-shape2 hours ago|
parent|
prev|
[-]
> Isn't that what the people crying over their deleted or leaked data were doing too?

Probably using not-SOTA models, or on the lower reasoning levels, they tend to be a bit more tally-ho when it comes to destructive operations, especially in longer tasks as the agent gets worse and worse as the context grows. Suddenly running some stupid command seems like the right way to go, and then $HOME is gone.

reply
upvoteby ben_w2 hours ago|
parent|
[-]
If the director of alignment at Meta Superintelligence Labs gets it wrong, what hope does anyone else have?
reply
upvoteby vehemenz5 minutes ago|
parent|
[-]
You mean the guy hired by the Metaverse guy?
reply
upvoteby chasd0022 minutes ago|
prev|
next
[-]
To be honest I do this too. Nag mode is kind of a pita.
reply
upvoteby TeMPOraL3 hours ago|
prev|
[-]
VMs and containers are primarily useful to reduce maintenance burden anyway. I.e. if it fails or you're otherwise done with it, you can torch the container instead of having to clean up your host system from zillion no longer relevant packages and configs.
reply