Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Auto mode is now the default in Claude Code

claude.com

Post reply on HN
Print view View original

91–100 of 336 posts

Re: Auto mode is now the default in Claude Code

#91

Post by natpalmer1776 »

mcmcmc wrote: post #36
levocardia wrote: post #24

Earlier quoted context omitted.

The default is set for the marginal new user, which at this point is probably not someone like you (who benefits a lot from manual mode) -- it's someone who's more "code-naive" and might get anxious about approving random bash script commands they don't recognize. Safely getting the user from prompt --> first vibe-coded app is the "user journey" now, and since auto mode seems pretty good at not letting Claude rm -rf'…

> it's someone who's more "code-naive" and might get anxious about approving random bash script commands they don't recognize. Maybe they should trust their instinct and not mess with things they don’t care to understand

It’s a brave new world.

I recall hearing similar sentiments from linux sysadmins regarding cloud infrastructure. In many respects they were and continue to be correct. In other respects, the world doesn’t care about the loss in understanding as long as things work “well enough” for the cogs of society to keep turning.

For those who do care (and have the aptitude) to understand things deeper there is always work to be had when “well enough” stops being good enough and someone has to unravel the “RDS queries are taking too long” problems that crop up as a result.

Re: Auto mode is now the default in Claude Code

#92

Post by SchemaLoad »

AussieWog93 wrote: post #76
ta-run wrote: post #74

>We hired 1,053 paid testers through a research vendor for a coding study. >The testers caught the dangerous command just 13.6% of the time (143 of 1,053), while auto mode blocked 89% of the same commands (937 of 1,053). Head to head, auto mode blocked 800 commands that a human approved, while humans blocked only 6 that auto mode allowed. As sessions got longer, humans did worse: they blocked about 17% of dangerous c…

I think literally anyone would stop reading these randomly long long bash commands at all after prompting Claude to do some basic sysadmin task and getting 15 of them in a row.

These models generate the most unreadable bash commands I've ever seen. Utilising every single option available and piping the result through multiple layers of regex and junk.

The mental load of having to actually review these commands beyond the most surface level glance is too much.

Re: Auto mode is now the default in Claude Code

#94

Post by jawiggins »

I use `--dangerously-skip-permissions` and have yet to have it wipe my drive :shrug:. I don't know how I'm supposed to be running dozens of parallel agents each with their own sub-agents while trying to approve commands from each of them, it's just won't scale to the amount of work I need to get done.

Re: Auto mode is now the default in Claude Code

#95

Post by glerk »

kartoshka wrote: post #12

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…

No. I haven't approved commands in more than a year. Worst that I've seen was some agent running git checkout -- in a repo with uncommitted changes. Annoying, but not catastrophic.

Imo these explicit tool-level permissions are really just a bandaid for bad sandboxing. Just be aware of where you are running your agent and what data is at risk of being destroyed or compromised. Assume that arbitrary code can run at any time and be prepared to recover from that.

Re: Auto mode is now the default in Claude Code

#96

Post by dgellow »

chrysoprace wrote: post #70
lukan wrote: 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…

Having used a bit of a mix of Claude Desktop and Claude Code lately, I discovered that Claude Desktop just times out when it asks you for a decision, and just goes ahead with the action anyway. There is no way to turn this off that I've found, unlike Claude Code where you can ask it to never time out.

We need a term that is stronger than dark pattern

Re: Auto mode is now the default in Claude Code

#97

Post by tristanj »

Enabling Auto mode quietly turns on a second LLM (the safety classifier) that increases your token usage by ~15-28%, and Anthropic used to charge you for these tokens.

Per this announcement, they've stopped charging for the tokens used by this safety classifier.

Re: Auto mode is now the default in Claude Code

#98

Post by eru »

jawiggins wrote: post #94

I use `--dangerously-skip-permissions` and have yet to have it wipe my drive :shrug:. I don't know how I'm supposed to be running dozens of parallel agents each with their own sub-agents while trying to approve commands from each of them, it's just won't scale to the amount of work I need to get done.

The permissions system seems to be mostly finegrained to help you from problems that backups and sandboxes already solve.

The more dangerous activities I find are sending messages to the outside world: I can't undo a dumb slack message to my boss.

Re: Auto mode is now the default in Claude Code

#99

Post by eru »

SchemaLoad wrote: post #90
steve_taylor wrote: post #9

I've been running Claude Code with --dangerously-skip-permissions in a Docker container for the last month or so, allowing me to get up and stretch my legs while it does its thing. I definitely wouldn't want to run it unsandboxed.

Sandboxing seems like the obvious solution. These tools prompt me to review an absurd number of very complex bash commands where there is realistically no way to carefully review them. I just want to put the thing in a box with the code and let it run any number of commands on the code without prompting.

You can actually use a hook to have a script review the (bash) commands for you.

Re: Auto mode is now the default in Claude Code

#100

Post by [deleted] »

etoxin wrote: post #29
lukan wrote: 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.

[deleted]
Post reply on HN