ask_user form: pressing Esc silently discards the entire form instead of clearing current input
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 65/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- cli, shell
- Área
- cli, developer-experience
Línea de trabajo
Look for the form handling code in the CLI, likely in a module for the ask_user tool or interactive prompts. Find where Esc key is captured and the current behavior that cancels the form. Compare with the normal prompt input clearing logic. Test by running the CLI and triggering a form to understand the flow. The fix should change the Esc handler to clear the current field instead of closing the form, and ensure a distinct action (like a different key combination) is used for form cancellation.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the bug
When answering an agent-presented form (via the ask_user/elicitation tool), pressing Esc closes/cancels the whole form. Everywhere else in the CLI, Esc clears the current text input (per /help: "esc esc - clear input, interrupt, stop agents, or rewind"). This inconsistency makes it very easy to accidentally lose an entire in-progress form response when the user's intent was just to clear/edit the current field.
Expected behavior
Esc inside a form field should clear that field's current text (consistent with normal prompt behavior), not close/cancel the form. A separate, distinct key/action should be used to actually cancel the form.
Additional context
This came up in a real session: the user had already answered one question in a multi-field form, hit Esc intending to clear/edit text, and the entire form closed with no indication of what (if anything) was preserved. The agent had no way to tell whether the cancellation was intentional or not.
- Lenguaje dominante
- Shell
- Estrellas
- 11.2k
- Forks
- 1.9k
- Merge medio
- 14 h 16 min
- PR fusionados (30 d)
- 6
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/copilot-cli
-
triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
github/copilot-cli#4932 ·
-
triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
github/copilot-cli#4909 ·
-
triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
github/copilot-cli#4906 ·
-
triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
github/copilot-cli#4848 ·
-
area:agents area:mcp
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
github/copilot-cli#4729 ·
Todos los issues de github/copilot-cli
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
elastic/gradle-plugins#156 ·
-
Priority/High ready-for-agent Severity/Major Type/Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
comp/cli P3 type/docs
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
NousResearch/hermes-agent#119756 · 1 comentario ·
-
comp: build/pipeline type: bug version: current (v17+)
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
angular/angularfire#3766 ·
-
out-of-date
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
CachyOS/CachyOS-PKGBUILDS#1903 ·