Claude Code: Starting August 14, auto mode will be the default permission mode

jddj•7 minutes ago

The majority of the times I reject a tool call it's because I can tell the agent is about to go off piste. Eg. adding packages to work around some non-problem is a common one.

I guess I could try to actively interrupt it in those moments, but that seems less effective.

More power to those who want to use it like that though, I guess. Perhaps by throwing in extra agentic guardrails, or whatever the idea may be. I don't think it's the best route to a good product or business but let's see.

bigwheels•about 3 hours ago

https://xcancel.com/ClaudeDevs/status/2085794862608318627

ameliaquining•about 2 hours ago

Announcement post is https://claude.com/blog/auto-mode-default-in-claude-code, link should probably point there instead of the tweet.

kelnos•about 1 hour ago

Doesn't auto mode also auto-accept code changes? Assuming their data is good, I'd be fine trying an auto mode for permission prompts (as the article says, I do eventually get prompt fatigue and stop examining them too deeply). But I absolutely don't want it changing code without my permission.

ameliaquining•42 minutes ago

Most users of coding agents do want the agent to edit their code, and don't want to have to click something before every edit. If you want something different, that's why it's a setting.

graceful6800•44 minutes ago

It will indeed change code. It will also happily do stuff like write into your user's SSH config and leave you with permanently broken SSH until you find and fix it.

dexterlagan•42 minutes ago

Hmmmm. OK. So yesterday I was accepting all these prompts in the manual mode for a solid hour, then I switched to Auto. Side project, nothing critical (creating ComfyUI workflows with CC and Opus). Walked away from the puter, got notified it was done. It did a good job, and by sheer luck it didn't delete a database or format my drive. But I felt a bit uneasy. Can we trust them now? I don't think I'd switch to Auto for a professional project. Not a chance. But for side projects? Yeah maybe - and only once I'd have validated whatever plan mode had come up with. Setting Auto as default? That's not cool. I'd set Plan mode as default.

Had a conversation with a friend who's struggling with code, and recently got into AI tools. The one thing that kept him from using Claude Code? Auto mode. My friend was convinced it didn't ask permission before touching his codebase by default.

Anthropic: careful. We the people trust Claude Code more than some other harness precisely because it asks you before doing anything. If you go full auto, there will be collateral damage. And yeah, I know, you can roll back. But some newcomers aren't familiar with that kind of stuff. Don't do it bro. Let us switch to Auto when we feel safe.

mccoyb•17 minutes ago

my opinion: "trust" is an interesting word to use for a piece of closed source probabilistic software that changes daily (sometimes multiple times), whose lead dev reports they rewrite something like 90% ("almost all", I believe, from recent interview) of the codebase after every new model release

Computer0•about 1 hour ago

"Auto mode runs a classifier on every tool call, which uses a small number of extra tokens.

As of today, that classifier overhead no longer counts toward your usage limits on Pro, Max, and Team plans. This change will come to Enterprise plans and API users once auto mode is the default for those users, too"

That seems like a good change if making this the default.

beybol•about 3 hours ago

It will require more attention to settings.local.json :)

exabrial•about 1 hour ago

Great. Can we have thought traces back?

Claude Code: Starting August 14, auto mode will be the default permission mode

⚡ Community Insights

Discussion (11 Comments)Read Original on HackerNews