If having something like that happen to you will be a disaster, don't be so non chalant about using it that way.
Yes, nobody should.
The very idea that a quite recent and still maturing technology, that is known to hallucinate ocassionally and frequently misunderstand prompts and take several attempts to get it back on the right track, is ok to be run outside a container with "rm" and other full rights, is crazy talk. Comparing it to driving a car where you'r full in control? Crazy talking chef's kiss.
People aren't saying "I'm never using Claude Code again" just like they aren't saying "I'm never driving again". That's not what the post or most of the discussion is about.
Leave CC permission checks on or run in a sandbox. At a minimum, understand there are risks even if you haven't personally encountered them. See https://en.wikipedia.org/wiki/Faulty_generalization
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 knew the risks and accepted them, but it is more than capable of doing system actions you can regret.
It is in those one does not.