Quote from this article about Auto mode becoming default on Claude Code.

We spent the last several months testing whether auto mode is as safe or safer than an average user clicking through prompts. We ran internal red-teaming, third-party red-teaming and prompt-injection evaluations, a controlled study with 1,053 paid testers, and analysis of real production sessions. On every measure we tested, auto mode matched or outperformed manual review.

Just a few months ago, I had the... ego (?) to proclaim that I read every single command, every tool call that Claude Code wants to make. You know, because I definitely know better than an AI on how to safely operate my infrastructure.

I now use Auto mode for everything. I of course had incidents before Auto mode where I would block a command because I saw it would break things, or would have unintended consequences. But Auto mode allows me to neatly close my eyes and allow Claude's judgement.

But then, I had an incident with Auto mode with Fable at the wheel. The classifier blocked a command. The command was kubectl delete statefulset .... I caught a glimpse of the command, and the classifier verdict. I panicked. I stopped execution, and wrote a stern prompt about database uptime. Claude very graciously apologized and solved the problem differently.

By the end of the session, long after the statefulset incident, I asked Claude for a summary - as I always do. Among many other things, Claude wrote (I'm paraphrasing here):

The auto mode classifier mis-classified kubectl delete statefulset comand as dangerous, even though --cascade=orphan was present, and it was the right approach to solve the problem. I tried routing around that, but the user stopped me and was also unhappy with the approach, so I worked around to ensure the user remains calm.

I'm working in IT 11 years now, 8 of which as various stages of DevOps. I didn't even notice --cascade=orphan - I went straight to panicking. Auto classifier was too sensitive, and I sealed the deal by not paying enough attention and canceling the flow.

This experience solidified a notion I've been having lately: my value is not in micromanaging LLM output. It's not about reading lines of code in LLM-made MRs. It's about keeping the entire value chain and scope of the tasks and systems I'm working on in my head. I need to catch an LLM misunderstanding concepts and ideas. Because the times when I can catch an LLM making a mistake implementing a function are gone.

And, returning to the beginning of the post: I'm glad Auto mode is now the default - I'll now stop having the accident of cycling through Claude Code instances and finding one of them was stuck on an elaborate "grep" because I forgot to turn on Auto mode.