alt Hacker NewsI would personally feel a lot better with a container first approach, like attaching an LLM to QubesOS windows, so the non-deterministic chaos monkey can only effect what you want them to effect
This is easy enough with dev containers but once you let a model interact with your desktop, you should be really damn confident in your backup, rollback, and restore methods, and whether an errant rm rf or worse has any way to effect those.
IME even if someone has a cloud drive and a local external drive backup they've never actually tested the recovery path, and will just improvise after an emergency.
A snapshotted ZFS system pushing to something like rsync.net (which also stores snapshots) but I don't know of any timemachine-in-a-box solutions like Apple offers (is there still a time machine product actually? Maybe it's as easy as using that, since a factory reset Mac can restore from a time machine snapshot)
People are using these tools to write code, complete tasks, etc. your worry is that what... It will rm -rf /* something?
I am not trying to be funny but the Claude itself is smart enough to catch destructive actions and double check. Its not going to wake up and start eating your machine, googling a random script and running it which what a lot of people do in many cases leads to worse outcomes, here at least you can ask the model what might happen to my computer.