Choice 3 - "No and tell copilot to do something else" is not accepted and I have to press escape

[mamonu]

Describe the bug

when Im trying to answer with choice 3 to an edit "No and tell copilot to do something else" is not accepted and I have to press escape

Affected version

0.0.394 Commit: 3d79feb

Steps to reproduce the behavior

1. Pressing 3 and ENTER on an edit
2. Nothing happens
3. I can only press 1 or 2 or ESC

Expected behavior

I would expect to be able to say No to Copilot and explain what else I want to do instead

Additional context

OSX Tahoe 26.1
ARM M4Pro
iterm2
zsh

[dogmatic69]

was supposedly "fixed" in #904

[andyfeller]

Thank you for raising this issue, @mamonu, and apologies for any confusion or frustration this has caused! 🙇 Let me theorize what I think is happening, which I'd love your thoughts and confirmation around.

Theory

Previously, the "No, and tell Copilot what to do different" option used to fail back to the main input box, leaving the user sitting there with Copilot doing nothing. Recently, this was changed such that the user provides instruction to correct Copilot in order to keep it going.

See in this screen capture where I'm instructing Copilot on the correct capitalization of a script:

Screenshare.-.2026-01-24.10_51_50.AM.mp4

Thoughts

If you could confirm this is the case for you, I'd love to hear your thoughts on how this could be improved. I can understand this experience might not be obvious, so would love ideas to lower friction. Thanks again for your time!

[mamonu]

Thanks @andyfeller for the context. So this is a UI/UX issue after all IMO.
Even something like having a "No, and tell Copilot what to do different <INSERT SUGGESTION HERE>" (or something to
that effect if the wording is not right) would make it more obvious.

Like I seriously didn't expect or realise this functionality existed because there wasn't an obvious/visble change in the UI from the previous version where this feature was not available.

a more minimal UI idea would be to have a cursor flashing when selection is on 3. So its more obvious that User input can be taken into account