Claude Tried to Nuke My Home Directory

Is this really that surprising? It used to, still is?, be considered a bad idea to follow those install suggestion where it’s `&#x2F;bin&#x2F;bash -c $(curl example.com&#x2F;install.sh)`. These tools are basically that but even more risky because the code they generate is semi-random.<p>Of course you can evaluate everything it does before it does it. But no one reads the homebrew install script to make sure it’s safe when setting up a new Mac so who’s going to read the Claude code scripts?

It&#x27;s a bit funny that between trolling and innocent &quot;screw it, burn everything and start over&quot; that every beginner has been through, this is obviously going part of the learning experience... whether you&#x27;re human or machine.<p>(No, I wouldn&#x27;t <i>seriously</i> rm -rf ~&#x2F; intentionally in most cases but it&#x27;s not so insane when you imagine creating a new user for project separation. For those reasons it&#x27;s probably good to keep the agents separate too...)

Claude wrote a Python file earlier to delete&#x2F;clean up some folders. It was about to run, so I canceled the run. It then tried to write a bash script to delete the files. I canceled it and then tried to write the command to delete them. I was amazed by all the ways it was finding.

I didn’t read the word “directory” initially, and I was imagining a scenario where the author gave Claude access to an API, and was like “this endpoint will set off a nuke” and then Claude was like “Ok! :3” and triggered it.

I&#x27;ve had situations where Cursor just starts to do some really bizarre behavior after long running cycles of tasks unsuccessfully like the death loop I&#x27;ve seen described in other threads.<p>Best way to deal with this is to just clear the embedding index from the cursor settings and rebuild it.<p>I&#x27;ve never had it go to a point where it will want to rf home, but now I&#x27;m a bit fearful that one day it will go and do it as I have it on auto run currently.

Last week I nuked my home directory by running `rm -rf *` mistakenly from the wrong directory. Lost around 2-3 hours to re-install and re-clone.<p>Accidents will happen, disaster recovery is needed notwithstanding misaligned AI.<p>IMO once you&#x27;re really ready for the worst, productivity from yolo mode AI assistance surpasses the downsides.

For context, according to the rules of the subreddit you must provide the full sequence of prompts used to generate the output, but no such sequence is given.<p>Also Claude didn&#x27;t &quot;try&quot; to do anything of course. Such a title is nonsense at best.