ask_user  form: pressing Enter early submits/cancels and permanently discards the in-progress typed answer

Describe the bug

Severity: High (data loss — user-authored content is unrecoverable)

Impact: Loss of substantial user-typed input; forces the user to re-type from scratch and erodes trust in the form UI.

Suggested fixes: Draft autosave/restore for elicitation forms; make Enter insert a newline in text fields (submit via a distinct key like Ctrl+Enter); on cancel/escape, stash the draft (similar to  ctrl+s  stash/pop) rather than discarding it.

Affected version

GitHub Copilot CLI 1.0.83

Steps to reproduce the behavior

What happened: While typing a long free-text answer into an agent  ask_user  elicitation form, I pressed Enter before finishing. This submitted/advanced the form, and when I hit Escape to get back, my entire in-progress answer was erased with no way to recover it.

Expected behavior

Expected: Either (a) Enter in a multi-line form field should insert a newline (require an explicit submit action/confirmation to send), and/or (b) an accidental submit/escape should preserve the drafted text (e.g., restore it into the input buffer, or offer undo/ ctrl+r -style recovery). Long answers should never be silently, irrecoverably lost.

Additional context

No response

Start by reproducing the early-Enter and Escape flow in the ask_user elicitation form, then inspect how text input is handled across submit and cancel. Done means long drafts are not irretrievably discarded and the chosen submission behavior is clear and tested for accidental key presses.