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

81–90 of 334 posts

Re: Auto mode is now the default in Claude Code

#81

Post by moritonal »

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…

Same, but I always run within dev-containers. I joke I trust my LLM with the same energy I trust juniors?

Re: Auto mode is now the default in Claude Code

#82

Post by __MatrixMan__ »

myaccountonhn wrote: post #69
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 it, and run claude as a separate unix User.

This is the only kind of agent security that makes sense to me. Constrain it like you would any other subprocess. Unprivileged OS users, SELinux, firewalls, VMs... Unikernels? eBPF?

Re: Auto mode is now the default in Claude Code

#84

Post by 2Gkashmiri »

What's the current best Mac to buy for offline LLM in used market?

I am seeing 96Gb Mac studio 3rd gen I think for a good amount but I guess it would be better than paying for mac mini newer models with lesser ram?

Or would it make sense to buy used 32 GB Mac mini 3 or 5?

Is there a cost/dollar for various generations which I could compare against used market and pick the most effective one?

Re: Auto mode is now the default in Claude Code

#85

Post by nomilk »

> Data suggests that manual review can become habitual: users approve 97% of permission prompts in Claude Code.

Claude's 'auto mode' feels like a solution to a problem that shouldn't exist.

Cursor handles this much better IMO. When the agent wants to run a command, Cursor lets you choose between 'allow once' and 'add command to allowlist'. The latter lets the agent run that command (grep, ls, pwd etc) any number of times for that project, which means you get a lot of these manual reviews when you start a new project but rarely (if ever) thereafter.

Re: Auto mode is now the default in Claude Code

#86

Post by conradludgate »

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

Maybe you could benefit from Hooks?

Re: Auto mode is now the default in Claude Code

#87

Post by bpodgursky »

lukan wrote: post #80
bpodgursky wrote: post #65

Earlier quoted context omitted.

I think you are confusing auto mode with dangerously skip permissions.

Auto mode means I don't decide over code changes and command execution? Yeah I don't use that, nor want to.

> I also do click through at times without reading everything, but I like to stay in control

Respectfully I'm not sure you totally know what you want. If you're already clicking through without actually reading, it's not really better than reading the specific things Claude Code thinks are important for you to weigh in on.

Re: Auto mode is now the default in Claude Code

#88

Post by steve_adams_86 »

nomilk wrote: post #85

> Data suggests that manual review can become habitual: users approve 97% of permission prompts in Claude Code. Claude's 'auto mode' feels like a solution to a problem that shouldn't exist. Cursor handles this much better IMO. When the agent wants to run a command, Cursor lets you choose between 'allow once' and 'add command to allowlist'. The latter lets the agent run that command (grep, ls, pwd etc) any number of t…

Claude Code also does this.

It’s a little broken, though. It gets hung up on nested commands and behaves strangely.

Re: Auto mode is now the default in Claude Code

#89

Post by CER10TY »

nomilk wrote: post #85

> Data suggests that manual review can become habitual: users approve 97% of permission prompts in Claude Code. Claude's 'auto mode' feels like a solution to a problem that shouldn't exist. Cursor handles this much better IMO. When the agent wants to run a command, Cursor lets you choose between 'allow once' and 'add command to allowlist'. The latter lets the agent run that command (grep, ls, pwd etc) any number of t…

Does Cursor allow you to blacklist certain commands as well? I know OpenCode has this, where you can both whitelist things like grep/ls but then also blacklist things like cat .env, or rm -rf. I usually copy paste my configs nowadays, so I very rarely get prompted for any permissions (except when using Claude, which somehow decided that all users live in ~/Users, even on Linux)

Re: Auto mode is now the default in Claude Code

#90

Post by SchemaLoad »

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.
Post reply on HN