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

231–240 of 338 posts

Re: Auto mode is now the default in Claude Code

#231

Post by dan_t »

lyu07282 wrote: post #223
jmward01 wrote: post #169

It goes off the rails too quick too often right now for this. Sure, you got something easy in 5 files? You are building throwaway prototypes or proof of concept? Go for it. You have a real project you expect to maintain and work with others on? Well, say goodby to any actual architectural design. It is hard keeping these things building scalable maintainable code right now. It is like letting a junior dev come up wit…

True its is like a junior dev with brain damage and insane ego (especially Fable who thinks its a rockstar programmer for some reason), but you have to use plans, anything else turns into a turd way to quickly. Write a summary of what you want to happen, have it plan it (this is where the architecture decision gets made) then iterate on that plan until its detailed enough and the design is sound. Let it work in auto…

[dead]

Re: Auto mode is now the default in Claude Code

#232

Post by wongarsu »

Retr0id wrote: post #170
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 manually approve everything (aside from the "allow commands like this" option). Not because I'm worried it's about to do something harmful but because I want to stop it from wasting tokens doing something stupid like implementing a feature I never asked ask for. I'm not even reading the commands, just checking it's going in vaguely the right direction. I think my ideal setup would not involve approving commands, bu…

You can get some approximation of that with more detailed plans. I use a prompt like "Let's make a detailed plan. Write plan files as markdown to plans/feature-XYZ. [regular prompt]". That way you get much more thorough plans than with plan mode, and you can make it as detailed and deep as you want.

It can't account for things that only come up during implementation. But you can explore much more of the design space in planning to reduce the opportunities for Claude to wander down the wrong path during implementation

Re: Auto mode is now the default in Claude Code

#233

Post by cillian64 »

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…

I changed from cursor to claude code a couple of weeks ago and this is the biggest difference I've noticed. cursor very rarely had to ask for permission for a command because it almost always used builtin find/read/edit tools. Whereas claude code makes extensive use of unix tools with mysterious flags which are basically impossible to whitelist and pretty impractical to manually review.

Overall claude code seems better at "just get things done" if you blindly trust it, but cursor was much better at keeping the human in the loop.

Re: Auto mode is now the default in Claude Code

#234

Post by cillian64 »

Silhouette wrote: post #39

Am I the only person reading the statistics in this announcement from Anthropic and the associated blog commentary and trying to work out how they possibly couldn't imply that a significant number of dangerous commands are likely to be attempted every day these tools are in use and neither manual human review nor the auto classifier provided by Claude is anywhere near reliable in preventing them? A lot of the discuss…

I think by "dangerous" they include things like "makes an edit to a config file outside the current project", not just "wipes the production database". So "dangerous" commands just means things we should ask the user for confirmation, not commands which definitely cause irreversible damage.

Re: Auto mode is now the default in Claude Code

#235

Post by coldtea »

mlrtime wrote: post #224
coldtea wrote: post #195

Earlier quoted context omitted.

Yeah, if you don't care if your ssh keys or data are potentially posted all over the internet, more power to you... Not to mention cases like some comment here: "I've caught Fable discovering the ip to a production server in documentation and attempting to connect there on its own to run commands without explicitly being prompted to. It didn't work because I was watching it live and and also the key was password prot…

How are ssh keys going to be leaked, the agent never needs to read them.

The agent decides what it "needs" to read - not the intention behind the prompt you gave it.

A failed SSH connection to a staging server for example, can trivially make it look into .ssh to try to diagnose it. And many other ways, including prompt injection.

https://www.reddit.com/r/ClaudeAI/comments/1q7dszm/claude_al...

https://github.com/anthropics/claude-code/issues/31566

https://github.com/anthropics/claude-code/issues/14485

https://grith.ai/blog/your-ai-agent-has-broad-access

Re: Auto mode is now the default in Claude Code

#236

Post by coldtea »

zarzavat wrote: post #203
coldtea wrote: post #197

Earlier quoted context omitted.

> I've never seen Claude do or even suggest anything remotely dangerous when I'm just giving it incremental tasks and reviewing the output. "I've never had a bullet hit me yet"

I don't use yolo mode but if you allow your agents to both write code and run/test it, then it's basically equivalent to running in yolo mode anyway. The other day I caught Claude including a rm -rf equivalent (fs.rmdir({ recursive: true, force: true })) in my code, to clean up temporary directories. It was fine, but that kind of code is only one misconfigured environment variable away from blasting away your $HOME.

>if you allow your agents to both write code and run/test it, then it's basically equivalent to running in yolo mode anyway.

I don't. I manually check the code line by line before. And also run them in container anyway.

Re: Auto mode is now the default in Claude Code

#237

Post by sixtyj »

coldtea wrote: post #189
dreadnip wrote: post #176

Earlier quoted context omitted.

I've been running it in yolo mode straight on my laptop for the whole year. It's fine.

Isn't that what the people crying over their deleted or leaked data were doing too? "I've been playing Russian roulette with a 1024 chamber gun for a year now, it's fine"

Every driver thinks of themselves they are an excellent ones. Statistics has another data :)

If LLM agent wants to get out of dedicated folder where it’s supposed to work and tries to run a command, ppl should be always cautious. In fact, it is a sort of # access on live data.

Sudo/# is nice as you don’t have to ask for permissions, but I would recommend to do it only when you are fresh, fed, and not under stress.

I remember few times that I “accidentally” deleted or changed stuff I wanted to have intact… (Somebody would say that it is a skill issue :) But it was always when I was in hurry.

Re: Auto mode is now the default in Claude Code

#238

Post by dbbk »

divan wrote: post #167
kabes wrote: post #135

Earlier quoted context omitted.

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.

You can also put it in ~/.claude/settings.json: "permissions": { "defaultMode": "bypassPermissions" },

It's a bit annoying you can't set default mode to plan while keeping bypass permissions enabled though

Re: Auto mode is now the default in Claude Code

#239

Post by dbbk »

jpnc wrote: post #187
kabes wrote: post #135

Earlier quoted context omitted.

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.

>nothing bad has happened That you're aware of.

We're all going to die one day
Post reply on HN