claude-code - 💡(How to fix) Fix Mini inline editor (vim) and idle-queue with batch-flush for multi-question responses [1 comments, 2 participants]

Feature Description It would be great to have an idle queue with batch-flush. I find with lengthy multi-question responses, I want to reply to all of them in one batch (otherwise each response creates a new turn), but, especially since I use vim, this can sometimes feel dangerous because too easy to accidentally delete the whole response (yes, can undo the delete...most of the time). Hit the wrong arrow key? Off goes my large, detailed, partially complete response. The biggest issue is the cognitive load: I am editing a long string rather than a robust doc/file/response. The editor is great, but I can't switch to that because that takes up the whole screen - I cannot see the Claude response that I am in turn responding to.

Case in point? This response. I wanted to edit a word (the "resopnse" misspelling), but I can't do it with vim muscle memory (e.g. search), nor with the mouse. And if I press the wrong arrow key at the wrong time, it's gone.

Solution?

1. Better mini editor integration: A non-full-screen editor, otherwise just like the vim editor I can currently use. Best of both worlds (see context, but editing a doc with full vim control).
2. Or, (better yet, and) an idle-queue batch-flush: concentrate on answering one question and then queue it up (but NOT flushed and therefore not fired to the API yet). Then the next. When all is done, fire them all off together. No longer is there out-of-turn processing and responding, and less pain while editing longer responses as a big, long, finicky string.

Both would be great to have!

Environment Info

• Platform: darwin
• Terminal: kitty
• Version: 2.1.123
• Feedback ID: 74ddcb37-a7bd-4635-a746-615cd78a72b1