[FEATURE] Manual confirmation new option

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

As a developer I am loving using Claude Code - it has revolutionised by development and made my job exciting again.

As you can imagine I do most of my programming in "manual" mode, so when a change is required I will often see these options:
<img width="273" height="188" alt="Image" src="https://github.com/user-attachments/assets/2cceda56-3f82-4705-b27f-b19d8c2cce98" />

I'm in manual mode because Claude doesn't always get it right. And consequently Claude may have been thinking for a few minutes before proposing 30+ lines of new code, and I can browse through the code which is great - I can confirm that everything Claude is proposing is correct, well actually, there is one line that needs a small change, maybe I changed my mind on the text of a message or the way an error message is worded.
If I choose option 1, then the code change is applied and Claude is off calculating the next change. I'm not sure, should I interrupt Claude for this small issue, while he's working so hard on the next modification. Makes me feel bad.
I never choose option 2, because I'm in manual mode for a reason.
If I choose option 3, then Claude will stop and ask for the modification required, and it is such a small thing, I feel like I'm "nit picking". I've interrupted the entire project because I wanted to modify the word of an error message.

I did trying modifying the proposed changes in the preview editor, but this doesn't end up in the final code. (I'm using VS Code and the Claude Code plugin).

The other option is to let Claude continue and make a note to come back and update that message after Claude has finished all of the changes. But sometimes I forget to read my notes.

Proposed Solution

Personally I would replace option 2 with "Yes, but stop and leave the file open in the editor for further modifications"

I asked Claude Code is this was an option, and while he considered some hooks, he said it wasn't going to achieve what I wanted.

Alternative Solutions

Add a new option with "Yes, but stop and leave the file open in the editor for further modifications"

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

I'm creating a new feature in my app and Claude Code proposes a large segment of code, but I want to change the title from "Recipes" to "My Recipes".
Option 1: Yes
Option 2: Yes, allow all edits this session
Option 3: No

Every option results in Claude racing on to the next task, the file changes are either applied or not (in the case of option 3) but I only wanted to make one small change.
I have to press Escape, interrupt Claude Code, open the file, make the minor change, save and close the file, and then instruct Claude Code to continue again.

Additional Context

One time I tried edit the file while Claude Code was processing for the next change, but a key I pressed responded to something Claude had asked - I didn't get a chance to see what it was, I don't know what I agreed to, and off Claude went again. I hope I didn't break anything.