YOLO Mode Please?

Status Fixed / completed
Maintainer reply ✓ Yes — bcherny
Activity 4 comments · opened Feb 26, 2025 · closed Feb 26, 2025
💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

Can we please have a YOLO mode to auto "yes" to all these sorts of things?

 Bash command                                                                                                                                                                                                                                                  
   bash setup-env.sh                                                                                                             
   Sets up development environment using bash script                                                                              Do you want to proceed?                                                                                                         
 ❯ Yes                                                                                                                           
   Yes, and don't ask again for bash setup-env.sh commands in /dir
   No, and tell Claude what to do differently (esc)

Cursor has one and it's great. I'd be OK with not needing one but TUI responsiveness is SLOW and laggy. :(

View original on GitHub ↗

4 Comments

lswank · 1 year ago

@ChrisDryden Thank you! You are the man.

bcherny collaborator · 1 year ago

There are a couple ways to auto-approve permissions:

  1. --dangerously-skip-permissions in a Docker container without internet access
  2. In the latest version (v0.2.18) you can allowlist every tool in allowedTools (docs)

It's up to you to weigh the risks for your use case. Generally we discourage yoloing because it can lead to prompt injection, it can exfiltrate your code and keys to third parties, and it can bork your machine (this has actually happened when people did similar things with similar tools).

github-actions[bot] · 1 year ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.