Auto Mode by Claude Code - Let Claude make permission decisions on your behalf
by•
Claude Code’s new auto mode lets Claude approve file writes and bash commands for you. A classifier checks each action: safe ones run automatically, risky ones get blocked and handled differently. Use in isolated environments.
Replies
Best
Hunter
📌
Claude’s latest “Аuto Мode” might be the smartest update yet by @Claude by Anthropic.
It bridges the gap between AI thinking and action by letting Claude handle file writes, commands, and workflows on your computer. With permission and without constant approvals. Safe actions run automatically, risky ones get blocked and handled differently.
Set it once, let Claude manage repetitive tasks, scripts, or reports, and free your attention for higher-level work. Perfect for devs, operators, and founders who want AI to actually do, not just suggest.
Available on Team plan now; Enterprise and API coming soon.
Umair is right on, the 90% rubber stamping was never the real friction, it was just the visible friction. The actual problem is the 10% where you need to understand what Claude is trying to do and why before you can make a good call. If the classifier just blocks those with a generic message and no context, you've traded one interruption for a worse one.
What I'd want from auto mode is not just safe/blocked but a third state: "proceeding but flagging this for your review." Something that lets the session continue without stopping but surfaces the decision for you to audit after. That way you're not context-switching mid-flow but you're also not flying completely blind on the edge cases.
Use Claude Code daily and the constant approvals do break the flow, especially on long agentic sessions. The right trust model here isn't yes/no per action, it's more like a pilot and autopilot relationship. Autopilot handles the cruise, the pilot takes over when conditions get genuinely tricky. Curious how the classifier is trained and whether it improves over time on the user's specific codebase patterns.
Report
The permission classifier framing is interesting. It's essentially teaching the model to internalize your risk tolerance rather than defaulting to ask. I'm curious how it handles drift over time - if your codebase or usage patterns change, does the classifier retrain, or is it more of a snapshot of your initial preferences?
Report
What happens when the classifier isn't confident? Does it block and ask, or does it default to one side? The "handled differently" phrasing in the description is a bit vague for something that could have real consequences if it gets it wrong.
Report
the classifier is doing the same thing i already do mentally when i hit yes/no on approvals. 90% of the time its obviously safe and im just rubber stamping it. nice that they automated the rubber stamp but the real problem was never the safe actions, its the 10% where claude wants to do something genuinely weird and you need context to judge it. curious if the classifier catches those or just lets them through with a generic "blocked" message
We've been auditing Claude Code and the new 'Auto Mode' architecture. The standout feature is the Guardian Classifier—it’s the most elegant solution we’ve seen to the 'permission fatigue' problem, allowing for true delegation without sacrificing system security.
For developers curious about the 'Project Scope' guardrails or how this fits into the 2026 agentic landscape, we've published our full technical audit here:
The 'Coffee Break Test' is officially passed! Looking forward to seeing how this evolves.
Report
Looking forward to trying this soon, once it rolls out publicly. I think this will be a huge time saver / quality of life improvement. Most of the approval decisions that Claude asks for right now are trivial (variations of "find" and "grep" commands, etc.). But while Claude is busy working, I often context switch away to some other work, and I constantly have to go back and forth just to see if Claude is stuck waiting for an approval. This feature should take care of the vast majority of these.
Replies
Claude’s latest “Аuto Мode” might be the smartest update yet by @Claude by Anthropic.
It bridges the gap between AI thinking and action by letting Claude handle file writes, commands, and workflows on your computer. With permission and without constant approvals. Safe actions run automatically, risky ones get blocked and handled differently.
Set it once, let Claude manage repetitive tasks, scripts, or reports, and free your attention for higher-level work. Perfect for devs, operators, and founders who want AI to actually do, not just suggest.
Available on Team plan now; Enterprise and API coming soon.
Tobira.ai
@byalexai This is huge! Finally no more constant "Yes" clicks.
Super curious, does Auto Mode eat a ton of extra tokens, or is it pretty efficient?
BrandingStudio.ai
Umair is right on, the 90% rubber stamping was never the real friction, it was just the visible friction. The actual problem is the 10% where you need to understand what Claude is trying to do and why before you can make a good call. If the classifier just blocks those with a generic message and no context, you've traded one interruption for a worse one.
What I'd want from auto mode is not just safe/blocked but a third state: "proceeding but flagging this for your review." Something that lets the session continue without stopping but surfaces the decision for you to audit after. That way you're not context-switching mid-flow but you're also not flying completely blind on the edge cases.
Use Claude Code daily and the constant approvals do break the flow, especially on long agentic sessions. The right trust model here isn't yes/no per action, it's more like a pilot and autopilot relationship. Autopilot handles the cruise, the pilot takes over when conditions get genuinely tricky. Curious how the classifier is trained and whether it improves over time on the user's specific codebase patterns.
The permission classifier framing is interesting. It's essentially teaching the model to internalize your risk tolerance rather than defaulting to ask. I'm curious how it handles drift over time - if your codebase or usage patterns change, does the classifier retrain, or is it more of a snapshot of your initial preferences?
What happens when the classifier isn't confident? Does it block and ask, or does it default to one side? The "handled differently" phrasing in the description is a bit vague for something that could have real consequences if it gets it wrong.
the classifier is doing the same thing i already do mentally when i hit yes/no on approvals. 90% of the time its obviously safe and im just rubber stamping it. nice that they automated the rubber stamp but the real problem was never the safe actions, its the 10% where claude wants to do something genuinely weird and you need context to judge it. curious if the classifier catches those or just lets them through with a generic "blocked" message
Triforce Todos
This sounds amazing, finally an AI that actually does things instead of just talking about them
I use Auto mode since it came out and it is great.
Sounds great. Curious how the classifier works. Happy to spend tokens doing the classification, but how safe is it?
Aura Water: Private Hydration
Phenomenal launch, Anthropic team! 🚀
We've been auditing Claude Code and the new 'Auto Mode' architecture. The standout feature is the Guardian Classifier—it’s the most elegant solution we’ve seen to the 'permission fatigue' problem, allowing for true delegation without sacrificing system security.
For developers curious about the 'Project Scope' guardrails or how this fits into the 2026 agentic landscape, we've published our full technical audit here:
👉 Article Link
The 'Coffee Break Test' is officially passed! Looking forward to seeing how this evolves.
Looking forward to trying this soon, once it rolls out publicly. I think this will be a huge time saver / quality of life improvement. Most of the approval decisions that Claude asks for right now are trivial (variations of "find" and "grep" commands, etc.). But while Claude is busy working, I often context switch away to some other work, and I constantly have to go back and forth just to see if Claude is stuck waiting for an approval. This feature should take care of the vast majority of these.