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

131–140 of 338 posts

Re: Auto mode is now the default in Claude Code

#131

Post by dist-epoch »

binsquare wrote: post #120
krzyk wrote: post #61

Earlier quoted context omitted.

I'm also in yolo mode, this is the only mode that makes sense for me, if I need to babysit I might as well do it myself. I run it in a VM so it can install any software needed, yes, there is a risk of escaping, but I'm not giving it impossible tasks so there is no need for it to workaround the jail.

What VM do you run it in? as context, I build a light weight portable vm designed for this purpose, so genuinely curious.

Given that people use VMs to sandbox agents of Mac/Windows/Linux, what does portable mean?

Re: Auto mode is now the default in Claude Code

#132

Post by jawiggins »

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

That's fair, I have sent a, "Sorry claude sent that and I didn't tell him to", message before.

Re: Auto mode is now the default in Claude Code

#133

Post by frogulis »

somenameforme wrote: post #68
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…

Regarding ulterior motives - these permissions are 'performative' in that anything you can give it permission to do, it already has the ability to do. They're app level - not OS level. So if they wanted to do something, it wouldn't require you to give permission.

To be clear, I'm not accusing Anthropic of being evil black hats trying to break my computer, I'm accusing (or rather suspecting) them of pushing me towards some kind of product lock-in by making my preferred "sceptical at-arms-length user" workflow more annoying.

Re: Auto mode is now the default in Claude Code

#134

Post by dist-epoch »

__MatrixMan__ wrote: post #82
myaccountonhn wrote: post #69

Earlier quoted context omitted.

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?

Escalations to root are a dime the bucket.

Re: Auto mode is now the default in Claude Code

#135

Post by kabes »

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…

My .bashrc has `alias claude='claude --dangerously-skip-permissions'`

Been using it like that everyday for about a year now and nothing bad has happened. I got backups and if it would fuck things up, it can probably fix it again as well.

Re: Auto mode is now the default in Claude Code

#136

Post by dist-epoch »

Silhouette wrote: post #73
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…

LLMs are inherently dangerous tools I don't see how. An LLM just generates a stream of output and they became very useful doing no more than that. What is dangerous is then interpreting that output as instructions to some other part of a system that has the ability to do damage if misused. and reviewing individual commands (or spamming `y`) doesn't make them less so. Surely if you review each instruction in the outpu…

> do not allow the other part of the system to act on one if it would be harmful

Network security is really easy right, just don't act on harmful requests

Re: Auto mode is now the default in Claude Code

#137

Post by energy123 »

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.

Why not let it delete stuff in the current working folder and in tmp, but give it read-only access elsewhere?

Re: Auto mode is now the default in Claude Code

#138

Post by techpression »

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…

Burning more tokens is definitely in their best interest, users not so much.

Re: Auto mode is now the default in Claude Code

#139

Post by mlperson »

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.

Me too.

Re: Auto mode is now the default in Claude Code

#140

Post by elil17 »

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…

[dead]
Post reply on HN