I've been using Docker containers but I'm not sure if that's a foolproof solution.
Cloudtops only have access to credentials for my personal instances. Instances can be wiped and brought back up in about half an hour from a script. Any deployment to staging/prod is done with other tooling that doesn't run through AI, and only looks at checked-in code.
If my AI went completely haywire, it could hose my personal instances and a single cloudtop. It would take about 15 minutes to de-provision the old cloudtop and provision a new one. After that I'd kick off 45 minutes of git cloning, and in parallel run the scripts to wipe my personal instances and reset them to good. After an hour I'd be back to a clean workable state.
I've had to do this twice, but neither time was due to AI, both were due to bad updates my cloudtops got.
Sometimes I just want to work on local files though, and with Claude code there isn't really a good way to sandbox it while also having access to claude-in-chrome.
Problem with one website? Change settings for the entire OS.
Problem with one file? Delete the entire folder.
AI is super dangerous when giving advice on OS management. Giving it the keys to your computer is s*icidal.
https://reddit.com/r/google_antigravity/comments/1xpbc54/ant...
"A computer can never be held accountable, therefore a computer must never make [an important] decision." -- IBM manual, corrected
Someone hooked up their computer to a random number generator that can destroy it, and their computer got destroyed. The weird part is not why the RNG foot-gun shot someone in the foot again...