Disasters tend to not happen until they happen.

If having something like that happen to you will be a disaster, don't be so non chalant about using it that way.

This is like saying you've never worn a seatbelt and still haven't been in an accident. So you'd like to know the series of turns that led to someone else's accident.

How much do you babysit claude, and how much do you just "let it do its thing"?

I haven't had anything as severe as OP, but I have had minor issues. For instance, claude dropped a "production" database (it was a demo for the hackerspace, I had previously told claude the project was "in development" because it was worried too much about backwards compatibility, so it assumed it could just drop the db). Sometimes a file is dropped, sometimes a git commit is made and pushed without checking etc despite instructions.

I'm building a personal repo with best practices and scripts for running claude safely etc, so I'm always curious about usage patterns.

I have similar usage habits. Not only has nothing like this ever happened for me, but I don’t think it has ever deleted anything that I didn’t want to be deleted, ever. Files only get deleted if I ask for a “cleanup” or something similar.

Almost the same experience except that it sometimes for force pushed (semi) destructive git versions and once replaced a whole folder with a zip file without the git history. Only a few hours lost though;)

I guess if you have Time Machine backups you can always use that if it nukes things.

The peril of a bear trap is not in those one places and knows about.

It is in those one does not.