Describe the bug
When Copilot asks a multiple-choice question during planning and I select the last option to enter free text, I sometimes press Ctrl+G to edit that answer in my external $EDITOR — the same way I can for a normal prompt.
Expected: Ctrl+G opens the current freeform answer in $EDITOR, and on save the edited text returns to the question's freeform field, still in question mode.
Actual: Ctrl+G exits question mode entirely. It's unclear whether an answer was accepted or the question was abandoned. The session state after is ambiguous.
Environment: Copilot CLI v1.0.73, Linux (WSL).
Affected version
Copilot CLI v1.0.73
Steps to reproduce the behavior
- Trigger a question with a freeform "type your own answer" option.
- Select that option and start typing.
- Press Ctrl+G.
=> Question prompt is torn down; no clear accepted/abandoned signal.
Expected behavior
Wire the Ctrl+G "edit in $EDITOR" handler to the freeform question input so it round-trips the answer back into question mode, OR disable Ctrl+G in that context with a clear message instead of silently exiting.
Additional context
No response
Describe the bug
When Copilot asks a multiple-choice question during planning and I select the last option to enter free text, I sometimes press Ctrl+G to edit that answer in my external $EDITOR — the same way I can for a normal prompt.
Expected: Ctrl+G opens the current freeform answer in $EDITOR, and on save the edited text returns to the question's freeform field, still in question mode.
Actual: Ctrl+G exits question mode entirely. It's unclear whether an answer was accepted or the question was abandoned. The session state after is ambiguous.
Environment: Copilot CLI v1.0.73, Linux (WSL).
Affected version
Copilot CLI v1.0.73
Steps to reproduce the behavior
=> Question prompt is torn down; no clear accepted/abandoned signal.
Expected behavior
Wire the Ctrl+G "edit in $EDITOR" handler to the freeform question input so it round-trips the answer back into question mode, OR disable Ctrl+G in that context with a clear message instead of silently exiting.
Additional context
No response