[FEATURE] Limited edit choices cause all or none approval decisions
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
When Claude starts implementing changes to a file it prompts whether I should allow it to edit the file but I can't skip out this prompt again unless I allow all editing. It's all or nothing. I'd like some in between and current options don't support this.
Today when Claude wants to edit a file it prompts us with these three choices:
- Yes
- Yes, allow all edits during this session (shift+tab)
- No
If we don't allow access to all edits, it will prompt us repeatedly, for this file and for other files in the same directory. Stopping productivity by pausing for user intervention.
Proposed Solution
Offer two additional options that cover those scenarios, e.g.
- Yes
- Yes, allow all edits during this session (shift+tab)
- Yes, allow edits for all files in this directory during this session
- Yes, allow all edits for this file during this session
- No
Alternative Solutions
When the user tabs on '1. Yes' and types "allow all edits for this file during this session", respect that instruction. Currently, Claude ignores this directive and instead it re-prompts.
The same for "allow edits for all files in this directory during this session".
Priority
High - Significant impact on productivity
Feature Category
Interactive mode (TUI)
Use Case Example
Example scenario:
- Claude and I agree to a change that requires touching all test cases in a large number of files in a directory.
- It shows me the first change and I'm good with it so I press 1 for yes I don't want to allow it to edit any files outside this directory
- Claude prompts me again for more changes in the same file and/or the same directory. My only choice is to approve each change or approve all changes.
Additional Context
It's pretty clear, the more files and directories you have and the more changes you have, the more annoying this limitation is.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗