github / github/copilot-cli

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

Abierto
#4,803 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

triage
Lenguaje dominante
Shell
Estrellas
11.2k
Forks
1.9k
Merge medio
14 h 16 min
PR fusionados (30 d)
6

Descripción

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.

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Empieza reproduciendo /ask y /btw en un terminal integrado de Windows VS Code, incluyendo, si es posible, conversaciones reanudadas y tareas simultáneas. Compara el texto transmitido mostrado y almacenado en búfer con la carga útil de la respuesta final; se considera terminado cuando la respuesta sigue siendo legible mientras el panel permanece abierto, incluso cuando la carga útil final está vacía o falta.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
shell, vscode
Área
cli
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Activo
Claridad
Necesita aclaración
Aptitud para principiantes
42/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.