Live data from Hacker News

Auto mode is now the default in Claude Code

claude.com

41–50 of 334 posts

Re: Auto mode is now the default in Claude Code

#41
Worth mentioning as I think at least a few of the commenters are mixing them up: auto mode is different from --dangerously-skip-permissions / YOLO mode. In auto mode, there's a classifier that runs before any command is executed and theoretically blocks any dangerous commands from running. I've found it to be quite annoying and overly zealous, but probably pretty effective.

Re: Auto mode is now the default in Claude Code

#42
Before auto mode came out, I had a script that ran before every permission request, it called Haiku with a prompt with a list of safe and unsafe command examples and asked it to classify as safe/unsafe and log it so I can review it later. It worked really well for me until auto mode came out, at which point I preferred the provider's built-in classifier versus maintaining my own.

I've been using auto mode ever since the feature was released. Apart from a very few occassions where the classifier blocked a safe command, I have faced no issues and continue using it as my default mode. It's great!

Re: Auto mode is now the default in Claude Code

#44
post #29
post #16

"We spent the last several months testing whether auto mode is as safe or safer than an average user clicking through prompts." Yeah, might make sense from their perspective, but no thank you. I also do click through at times without reading everything, but I like to stay in control, learn about the new code and change direction if it goes off track. This would just burn more tokens because I have to throw away much…

At this stage with the latest models with "increased persistence" and the sheer amount of supply chain attacks, you'd be insane not running these tools in a sandbox.

Exactly. Claude in a VM is the way to go.

Re: Auto mode is now the default in Claude Code

#46

Has anyone had Claude Code or Codex approve a harmful/damaging command in auto mode? I have been using Codex with auto-approve mode for a couple months and haven't had a single incident (or at least haven't noticed). Maybe as capabilities get better and better and they are less likely to do something dumb like wiping ~/, we can just trust them? I guess this argument works unless we worry about agents doing something…

Just yesterday it lost my git stash (I had recovered it from a backup). I think for code operations it's ok but as soon as file removal is involved (like git) the auto mode is destined to make a mistake and you only need to learn this once.

Re: Auto mode is now the default in Claude Code

#47
post #29

Earlier quoted context omitted.

At this stage with the latest models with "increased persistence" and the sheer amount of supply chain attacks, you'd be insane not running these tools in a sandbox.

Exactly. Claude in a VM is the way to go.

A VM hosted by someone else. Somethig on your personal notebook or the proxmox server in your garage is still too risky.

Re: Auto mode is now the default in Claude Code

#48
post #35
post #6

it's a good default because you really do get prompted incessantly without it. and since plenty of people are going to be using auto mode anyway, might as well make it as widely-used as possible so that you can focus on making auto mode safe.

> making auto mode safe They literally can’t. Terrible default.

In some time it would look like the obvious default and we would wonder how we even worked with the old one

Re: Auto mode is now the default in Claude Code

#49

Their findings about auto mode catching more dangerous commands, and most permission requests being accepted without scrutiny is interesting. I can totally see how that happens. On the other hand, soooo many of the tool uses it asks permission for are custom commands to replace functionality I should be able to trust once instead. e.g. instead of having a trustable Find tool, or using its already-trusted Read tool, i…

[deleted]
Post reply on HN