Anthropic are really confident in Claude Code's auto mode, to the point that they are making it the default setting for new sessions in most Claude Code plans starting on August 14th.
https://simonwillison.net/2026/Aug/8/auto-mode/
check post at origin
Auto mode sounds less like security and more like outsourcing judgment to the same AI you’re supposedly trying to constrain. If users are bad at spotting malicious prompts, the answer shouldn’t be: great, let’s remove them from the loop entirely. That’s not safety. That’s automated permission laundering.
So if I remember correctly, what happens with auto mode is they run a second smaller LLM called the “classifier” to evaluate the tool uses of the main one.
I’ve used auto mode at work now for many months, and it approves most things because most things Claude does are reasonable.
Once or twice I have seen it reject Claude. I can’t remember the exact scenario, but I had asked Claude to diagnose an issue but not fix it yet, and when later on it tried to make the change the classifier rejected it, giving the reason that what it was trying to do did not match my request.
In my opinion, the trick to using auto mode safely here is to:
I just assumed it was to increase token use and create a windfall for Anthropic
I like auto mode but you need something like “If the auto mode classifier denies your request stop and ask the human, do not attempt to work around it “ in your CLAUDE.md. Without it it has a tendency to try rather creative solutions to work around the denial, which kind of misses the point.
My denials always have a reason like “FUCK YOU I already told you not to do that dumb shit! NO EDITS WITH SED” which tends to keep it in check.
Anthropic is batshit crazy if they think automode is ready for default-on-always when their clankers constantly fuck up. Did they survey the dumbest 1100 people that don’t check the output carefully? The numbers in this article do NOT inspire confidence.
The issue is the whole UX behind it. I have yet to see someone review the 30th prompt of “grep” - there is no same default or middle ground.
For example whitelist read actions or harness side limitations to the project folder.
This is just lazy - again. “Users don’t use or very bad security feature so they just want us to disable it”.
If a pilot of a plane told me that they catch any critical errors they make 89% of the time, I would NOT get on that fucking plane.
Anthropic or not, the recent streak of supply chain and also targeted attacks got me packing into VM.
Now I run all devtools and install packages only inside the VM and either connect Zed / VSCode via ssh or run terminal ide inside the VM.
No host mounts whatsoever, all communication Host to Guest strictly through git.
Yeah but if I were buying cheap corn and they said 89% of the ears were good, I would still buy the corn. So is AI airplanes or corn?
That’s not entirely the same thing. It says it catches 89% of HARMFUL actions. That means that 11% of the time it doesn’t.
That’s more like if the corn had a parasite on it that could give you explosive diarrhea 11% of the time. Would you still eat the corn?
Also, in my example, I didn’t say the harmful actions of the pilot resulted in a crash. However, that doesn’t mean it couldn’t. How many of those 11% of the time are the “woops I deleted the production database” stories we hear all the time?
The OpenAI talk at DefCon shows what can happen when you let these things run without any human intervention.
The solution is, obviously, even less human intervention. 🤦🏻♂️
Honestly I’ve been using auto for the past year and it hasn’t bitten me once. It generally still pauses if there’s a big decision to be made, and small decisions that were made are shown.
yeah same here, the worst it can do is get in some weird loops to resolve an issue which can normally be resolved by better prompting or pointing it in the correct direction. But it is pretty good with file handling and usage of temp folder. I usually let it do auto but ask it not to implement anything before having a discussion with me so it generally does stuff in scratchpads in temp. One thing annoying about Claude is though when you open the session in a folder to work on a small script it generally goes as “ok let me read everything recursively staring from four parents up to get the context.” Probably can be handled with better config files but I just generally handle couple of initial request manually and then once it is in analysis mode I let it go auto
I just say yes to everything anyway. Not my money, not my choice to use it, not my responsibility. You give me a machine gun, I ain’t firing single rounds.
That’s called vibe coding.
“Claude is better than humans to detect errors Claude makes, therefore, you will use Claude”
A brand new FAFO machine, great!