[FEATURE] Add an option to support dontAsk and acceptEdits modes
Resolved 💬 3 comments Opened Mar 17, 2026 by ThomasHickman Closed Apr 30, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
I would like Claude Code to be able to run safely on autonomous tasks without requiring my input. The dontAsk mode seems ideal for this, but in dontAsk mode, Claude is not allowed to make any edits to files.
Proposed Solution
To solve this, you could:
- Change the dontAsk mode so that it includes the functionality of the acceptEdits mode
- Add an extra mode to support this feature
- Add a extra configuration option to enable the features of dontAsk or acceptEdits. Users can then use one of these modes and enable the extra configuration option
Alternative Solutions
Workaround that I've considered:
- Adding
Edit(/**)andCreate(/**)to my permissions. For some reason, this doesn't seem to work. It seems like the acceptEdits mode includes more than these permissions as well (I think it doesn't allow writing to directories it deems unsafe and enables some additional permissions) - Adding a
PermissionRequesthook to deny all requests. I'm still getting permission requests after doing this.
Priority
High - Significant impact on productivity
Feature Category
Configuration and settings
Use Case Example
_No response_
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗