Add 'Yes, but...' option to tool approval prompt
Summary
When Claude Code prompts for tool approval (edit, write, bash, etc.), the only options are Yes, Yes to all, and No. There's no way to say "Yes, but..." — i.e., approve the action while providing inline course-correction.
Problem
Currently, if I see Claude is about to make an edit that's 80% right but needs a tweak, I have to:
- Approve the edit
- Wait for Claude to finish
- Explain what I wanted differently
- Wait for the corrective edit
This is wasteful. You wouldn't let a construction worker finish an entire brick wall before telling them the first row is off. You'd correct course while the work is happening.
Proposed Solution
Add a "Yes, but..." option (or similar) to the tool approval prompt that:
- Approves the current action
- Accepts a short text input with guidance (e.g., "yes, but use a different method name" or "yes, but also handle the null case")
- Feeds that guidance back into Claude's context so subsequent actions incorporate the correction immediately
This enables real-time steering without the approve → wait → correct → wait cycle.
Impact
This is especially valuable during multi-step edits, large refactors, or any task where Claude makes a series of related changes. Being able to steer mid-flight would significantly reduce wasted iterations.
🤖 Generated with Claude Code
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗