[FEATURE REQUEST] Auto-accept system actions

[nullbio]

It would be nice if we could put it into a auto-accept mode that doesn't ask for permission to do -anything- (bar a blacklist of obviously bad commands), and we can just define the system rules in our CLAUDE.md. I get that you wouldn't want that as the default behavior because of risks, but if the user is confident in how they're using Claude, it should be up to them to decide their risk tolerance. As such, I think it would be very convenient to have this option.

Just to give you one real world example, I've already told Claude in my CLAUDE.md that it can do file commands in my project folder, but it's still prompting for permission :(. Another one would be when I've left it to run when I get up to do something and come back and it's been sitting there waiting for permission for 3 minutes :'(:'(

[sid374]

Thanks for the feedback. We are exploring ways to do allow for this while still being safe

[aaronik]

Surprised this hasn't gotten more traction! I think that despite the inherent risks, especially with some internal mitigation, this would be a very powerful feature. Honestly, I think ultimately this is where things are going - towards more and more autonomy.

[nullbio]

Feels more like a business decision to do this in the aim of productizing the "fully automatic" option, rather than it being an issue of safety. I see no other reason why this would not already be available, considering that Claude Code already has good enough safety features and the difference between being forced to press enter and having it automatically press enter isn't a big one as far as the safety aspect is concerned, if the user has agreed to it and is watching the behavior already.

[rickoneeleven]

come on, someone deffo knows a hack for this, spill the beanies

[aaronik]

Oh I think there is actually a thing for this already - start Claude code with the flag --dangerously-skip-permissions and voila

[rickoneeleven]

wow, you're right. cheers big dawg.

[github-actions[bot]]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.