Cancelling/closing an ask_user form silently discards all previously answered fields
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 65/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- shell
- Ambito
- cli, developer-experience
Direzione di ricerca
Look for the ask_user/elicitation tool implementation in the codebase, likely in a directory like src/ or lib/. Find where form cancellation is handled and where field answers are stored. Examine the flow that returns 'User cancelled the request' and see if partial answers can be captured. Check for UI components that manage form state. Testing involves running the CLI and triggering a multi-field form to verify the bug and any fix.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Describe the bug
When a multi-field form (via the ask_user/elicitation tool) is cancelled or closed (e.g. via Esc, see related issue about Esc behavior), any fields the user had already answered before cancelling are discarded entirely. The tool result returned to the agent is just a generic cancellation notice with no partial data — even though the user may have already provided a real, considered answer to an earlier question in the same form.
Expected behavior
If a user has answered one or more fields before a form is exited/cancelled, those partial answers should either be (a) preserved and returned to the calling agent so context isn't lost, or (b) the UI should clearly warn the user before discarding a partially-completed form, distinguishing 'cancel with no answers yet' from 'cancel after already answering something.'
Additional context
In a real session, a user answered the first question of a multi-field form, then the form was closed (likely via Esc). The tool call result contained only "User cancelled the request" with no indication that a field had been answered, and no way to recover it. The agent could not tell the user what had been captured (nothing) or distinguish intentional full-cancellation from an accidental exit after partial input.
- Lingua principale
- Shell
- Stelle
- 11.2k
- Fork
- 1.9k
- Merge medio
- 14h 16m
- PR unite (30g)
- 6
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di github/copilot-cli
-
triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
github/copilot-cli#4932 ·
-
triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
github/copilot-cli#4909 ·
-
triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
github/copilot-cli#4906 ·
-
triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
github/copilot-cli#4848 ·
-
area:agents area:mcp
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
github/copilot-cli#4729 ·
Tutte le issue di github/copilot-cli
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
bug easy help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
lacs-project/sysknife#503 ·
-
help wanted kind/documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
liquidmetal-dev/flintlock#1239 ·