Describe the bug
I consider this a UX bug.
When copilot wants to execute some command, (e.g., code edits), it'll give an option like, "No, and tell copilot what to do instead".
In previous versions, selecting that option would just return you to the normal prompt mode, and you'd type the alternative. I think this is how the one installed via npm worked.
In the latest Copilot v1.0.68, when you select that menu option either by pressing the number or navigating with the arrow keys and pressing enter, nothing happens.
Only through sheer frustration at a color scheme regression this morning during which I randomly typed a flurry of keys on the keyboard this morning did I discover that the intent is to select that option and type the alternative instructions directly in the menu.
That was not easily discoverable.
Affected version
GitHub Copilot CLI 1.0.68. Run 'copilot update' to check for updates.
Steps to reproduce the behavior
The description explains this already
Expected behavior
Something to clearly indicate where the input is supposed to happen
Additional context
No response
Describe the bug
I consider this a UX bug.
When copilot wants to execute some command, (e.g., code edits), it'll give an option like, "No, and tell copilot what to do instead".
In previous versions, selecting that option would just return you to the normal prompt mode, and you'd type the alternative. I think this is how the one installed via npm worked.
In the latest
Copilot v1.0.68, when you select that menu option either by pressing the number or navigating with the arrow keys and pressing enter, nothing happens.Only through sheer frustration at a color scheme regression this morning during which I randomly typed a flurry of keys on the keyboard this morning did I discover that the intent is to select that option and type the alternative instructions directly in the menu.
That was not easily discoverable.
Affected version
GitHub Copilot CLI 1.0.68. Run 'copilot update' to check for updates.
Steps to reproduce the behavior
The description explains this already
Expected behavior
Something to clearly indicate where the input is supposed to happen
Additional context
No response