[Feature Request] "Confirm interrupt? (y/[n])" for vim-mode conflict
Status Fixed / completed
Maintainer reply ✓ Yes — sid374
Activity 7 comments · opened Apr 7, 2025 · closed Jun 10, 2025
💡 Likely answer: A maintainer (sid374, contributor)
responded on this thread — see the highlighted reply below.
Too often I hit "esc" in vim mode and it cancels the current operation. Consider adding a setting that requires confirmation to interrupt. When hitting "esc", continue until the user also hits "yes". Maybe make "yes" the default and let the user just hit "esc enter"
7 Comments
In fact this might actually be a bug, I'm not 100% sure. I think if I hit "esc" while in "insert mode" it actually interrupts the AI -- it should probably take me to normal mode first.
Looks like "esc" might conflict in a couple different ways. If I hit esc when auto-accept is on, it cancels auto-accept rather than taking me out of insert mode. Then, when I hit esc again it cancels the AI operation rather than taking me out of insert mode.
Esc should always first take you out of insert mode before applying any other claude-specific escape operations (those are basically commands for vim's command-mode)
The latest change to make "esc" always interrupt the AI first is quite different than what I'd expect here. When in "insert mode" with vim, ESC should always first take you back to normal mode. Esc a second time should interrupt.
I agree, fix incoming
This has been fixed!
Agreed, esc takes me back to normal mode! I've been taking it for granted recently and never commented. Thank you!
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.