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

121–130 of 338 posts

Re: Auto mode is now the default in Claude Code

#121

Post by Certhas »

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

I am using many many many things that I don't understand. Cars, public transport, etc...

I review and test the end product, not every tiny step along the way. If the LLM uses some command line tools I have never heard of to create a model I can verify, why should I learn a tool that is completely irrelevant to my core expertise?

Re: Auto mode is now the default in Claude Code

#122

Post by croemer »

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

same, and unlike other repliers, I'll say one doesn't need to reinvent a new tool for this. Just use devcontainers.

Same, I've also been running with `--dangerously-skip-permissions` in devcontainers with docker volumes to keep Claude/Codex auth tokens.

Works really well!

Re: Auto mode is now the default in Claude Code

#123

Post by SchemaLoad »

eru wrote: post #99
SchemaLoad wrote: post #90

Earlier quoted context omitted.

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.

This is still less safe and less convenient than sandboxing. I want them to be able to run whatever command they want inside the sandbox even if it's traditionally dangerous (overwrites files, etc) because it can't touch anything that matters and I can revert any changes to the code myself.

If anything the only thing you'd have to have reviewed is sandbox escape attempts.

Re: Auto mode is now the default in Claude Code

#124

Post by dyauspitr »

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…

Yeah who cares what it does, everything is backed up, everything can be rolled back. I always run it with the keys to the kingdom.

Re: Auto mode is now the default in Claude Code

#125

Post by eru »

SchemaLoad wrote: post #123
eru wrote: post #99

Earlier quoted context omitted.

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

This is still less safe and less convenient than sandboxing. I want them to be able to run whatever command they want inside the sandbox even if it's traditionally dangerous (overwrites files, etc) because it can't touch anything that matters and I can revert any changes to the code myself. If anything the only thing you'd have to have reviewed is sandbox escape attempts.

You are right. And the hook is for convenience, not for safety.

Having explicit sandboxes is good, of course. But in addition I also treat my whole computer like a sandbox, it least in the sense that there's no files I would mind if they were overwritten or deleted: you should have backups anyway.

Re: Auto mode is now the default in Claude Code

#126

Post by kartoshka »

wraptile wrote: post #46
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…

Just yesterday it lost my git stash (I had recovered it from a backup). I think for code operations it's ok but as soon as file removal is involved (like git) the auto mode is destined to make a mistake and you only need to learn this once.

It would be nice if there were a way to give some global instructions for the auto-approver like "always reject ___" or "be extra extra careful with ___" for things like file removal and git.

Re: Auto mode is now the default in Claude Code

#128

Post by nullify88 »

thunfischtoast wrote: post #105
Silhouette wrote: post #73

Earlier quoted context omitted.

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…

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 protected, but yeah, I do see some danger.

I have noticed that Fable tends to macgyver solutions together to achieve some goal.

Re: Auto mode is now the default in Claude Code

#129

Post by 9dev »

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

What an awful position to take. Tech used to be about becoming more accessible to people! Now we have a magical assistant to make computers do what you want with natural language, and your desire is gate keeping that so only programmers can use it to write software for themselves?

Re: Auto mode is now the default in Claude Code

#130

Post by yumraj »

conradludgate wrote: post #86
yumraj wrote: post #57

Earlier quoted context omitted.

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?

I'll look into them, thanks..
Post reply on HN