ask_user form: pressing Esc silently discards the entire form instead of clearing current input

Offen

#4,943 erstellt am 22.9.2026 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit: 3/5
Geschätzter Aufwand: 1-2 Tage
Anfängerfreundlichkeit: 65/100

Issue-Typ: Bug
Klarheit: Klar beschrieben
Aktivitätsstatus: Aktiv
Tech-Stack: cli, shell
Bereich: cli, developer-experience

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area:input-keyboard area:tools

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.

Vorherrschende Sprache: Shell
Sterne: 11.2k
Forks: 1.9k
Ø Merge: 14 Std. 16 Min.
Gemergte PRs (30 T.): 6

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus github/copilot-cli

Built-in skill `github-pr-media` cannot run: `gh auth token` is empty in a cloud agent session, and the endpoint rejects `Bearer` Offen

triage

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100

github/copilot-cli#4932 · Erstellt am 22.9.2026
/ide finds no workspaces under the CLI sandbox: kill(pid,0) EPERM misread as a dead process Offen

triage

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100

github/copilot-cli#4909 · Erstellt am 19.9.2026
MCP OAuth: DCR sends client_name "copilot-cli", rejected with 403 by Figma's allowlist (expects "GitHub Copilot CLI") Offen

triage

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100

github/copilot-cli#4906 · Erstellt am 18.9.2026
/feedback: “Save feedback bundle” is easily mistaken for submitting feedback Offen

triage

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100

github/copilot-cli#4848 · Erstellt am 15.9.2026
Built-in research agent tells subagents to call unavailable github/get_me tool Offen

area:agents area:mcp

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100

github/copilot-cli#4729 · Erstellt am 04.9.2026

Alle Issues in github/copilot-cli