github / github/copilot-cli

/ask and /btw answers go blank while the dialog stays open

Ouverte
#4,803 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

triage
Langage dominant
Shell
Étoiles
11.2k
Forks
1.9k
Merge moyen
14 h 16 min
PR mergées (30 j)
6

Description

Describe the bug

When I use /ask or its /btw alias, answer text appears and then disappears without me pressing Escape or otherwise dismissing the response. The answer box stays open but becomes blank.

This is different from the expected disappearance after explicitly closing the temporary answer panel.

Affected version

1.0.83-5

Steps to reproduce the behavior
  1. Run Copilot CLI in the VS Code integrated terminal on Windows.
  2. In an existing conversation, submit /ask <a short text-only question> or /btw <a short text-only question>.
  3. Allow the answer to render and leave the panel open without dismissing it.
  4. Observe that the answer text can disappear while the panel remains open.

This has happened repeatedly in this environment, but a deterministic minimal reproduction has not yet been isolated. It is not established whether a resumed conversation or a concurrently running main task is required.

Expected behavior

Once answer text is displayed, it should remain readable in the open panel until I explicitly dismiss it. Finishing the response should not erase already displayed text.

Additional context
  • OS/architecture: Windows, x64.
  • Terminal: VS Code integrated terminal.
  • Related closed report: github/copilot-cli#3759 describes blank /ask responses on resumed chats in version 1.0.61. Linking as possibly related, not as a confirmed duplicate or regression.

Suspected cause, not confirmed: Completion handling may replace an already streamed answer with an empty value when the final answer payload is empty or missing. A component-level simulation reproduces that failure mode, but the final payload from an actual failing live query has not been captured.

Local workaround status: The symptom was observed before modifying the installation. A temporary local UI workaround was subsequently applied to retain displayed and buffered streamed text when the final answer is empty or missing, while still using a nonempty final answer when provided. Its effectiveness against the original live symptom has not yet been confirmed; it is not an upstream fix or proof of the suspected cause.

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Commencez par reproduire /ask et /btw dans un terminal intégré Windows VS Code, y compris, si possible, les conversations reprises et les tâches concurrentes. Comparez le texte diffusé affiché et mis en tampon avec la payload de la réponse finale ; c’est terminé lorsque la réponse reste lisible tandis que le panneau reste ouvert, y compris lorsque la payload finale est vide ou absente.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
shell, vscode
Domaine
cli
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
Active
Clarté
À clarifier
Accessibilité débutants
42/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.