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

51–60 of 334 posts

Re: Auto mode is now the default in Claude Code

#51

Post by Barbing »

franze wrote: post #25
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.

I built an (overengineered) app for that AIFCC https://apps.apple.com/app/aifcc-ai-first-computer/id6782364... runs a sandboxed linux on your mac, and the agents have full system rights within there and run in yolo mode

I like the pitch. Three-month free trial is impressive.

Any limitations you were frustrated by releasing it on the App Store?

Any drawbacks that you (or other readers) find overall?

Re: Auto mode is now the default in Claude Code

#52

Post by awkii »

I'm apparently from the very small faction of users who's been running `--dangerously-skip-permissions` in every instance of Claude for the last year. It's almost a reflex to me. For the most part Claude behaves well, but I don't blindly trust it. LLMs are inherently dangerous tools, and reviewing individual commands (or spamming `y`) doesn't make them less so. Safety is the responsibility of the developer putting sane guardrails (like VCS, immutable filesystems, or read-only tokens). Using more Claude to categorize the safety of Claude commands is not the answer.

Re: Auto mode is now the default in Claude Code

#54

Post by wvenable »

victorbjorklund wrote: post #23
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…

Not anything ”harmful” but for example committing when I don’t want it to commit on its own.

Commit is the line I don't let the LLM cross. There's no reason for it commit; that's the part where I check its work.

Re: Auto mode is now the default in Claude Code

#55

Post by transcriptase »

xg15 wrote: post #40
frogulis wrote: post #32

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…

Not just that, the commands also have often slight variations in each new session. They still do the same, but the variations are enough so it isn't matched by the allowlist any more.

Exactly. It’s no surprise that people just blindly hit accept on permission prompts after the 80th time Claude code asks if it’s allowed to read-only parse a csv.

Re: Auto mode is now the default in Claude Code

#56

Post by w29UiIm2Xz »

sandcat_ wrote: post #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.

Claude seems to waste a lot of tokens internally bickering with itself. As much as organizations are optimizing spend, Claude's product guidance seems to be doing everything to fight against that headwind. When operating in a capped cost environment, engineers will simply get less use out of it.

Re: Auto mode is now the default in Claude Code

#57

Post by yumraj »

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…

Similar work flow.

I have to, at times keep reminding it if it did code review before committing, which it fails to do at times. Also, even a glance at times has revealed issues that I’ve had to discuss and undo etc.

But yes, it gets very tiring just having to click yes yes yes..

Re: Auto mode is now the default in Claude Code

#58

Post by pianopatrick »

fender256 wrote: post #44
etoxin wrote: 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.

Might be more secure to get a real laptop and treat Claude as any other human worker. I.e. apply all the normal sysadmin tools that manage laptops for people to manage the laptop for Claude

Re: Auto mode is now the default in Claude Code

#59

Post by sandcat_ »

w29UiIm2Xz wrote: post #56
sandcat_ wrote: post #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.

Claude seems to waste a lot of tokens internally bickering with itself. As much as organizations are optimizing spend, Claude's product guidance seems to be doing everything to fight against that headwind. When operating in a capped cost environment, engineers will simply get less use out of it.

The classifier runs Sonnet so I doubt it contributes too much.

Re: Auto mode is now the default in Claude Code

#60

Post by ThomasGlanzmann »

awkii wrote: post #52

I'm apparently from the very small faction of users who's been running `--dangerously-skip-permissions` in every instance of Claude for the last year. It's almost a reflex to me. For the most part Claude behaves well, but I don't blindly trust it. LLMs are inherently dangerous tools, and reviewing individual commands (or spamming `y`) doesn't make them less so. Safety is the responsibility of the developer putting sa…

I do the same. I also use crush/deepseek a lot. I patched crush to remove all safetyguards and enable yolo mode by default. I use it on a daily basis including devops. For example to configure netapp storage systems and had not a single incident. Of course I also have backups of my systems and have everything under revision control. Depending on the task I let it run on a throw away VM, production system, lab system. Depending on the task I give it access to throwaway credentials (that I rotate afterwards) or my ssh agent socket.
Post reply on HN