github / github/copilot-cli

[BUG]: Terminal streaming renderer corrupts output - characters doubled/truncated during streaming

Abierto
#3,749 5 comentarios 8 reacciones 0 asignados Ver en GitHub
area:terminal-rendering
Lenguaje dominante
Shell
Estrellas
11.2k
Forks
1.9k
Merge medio
14 h 16 min
PR fusionados (30 d)
6

Descripción

## Description

The Copilot CLI terminal renderer corrupts streamed output, producing doubled characters, truncated tokens, and repeated lines. This affects both the thinking/reasoning phase output and the final assistant response output.

## Steps to Reproduce

1. Ask Copilot CLI any question that produces a moderately long response
2. Observe the output as it streams to the terminal

## Observed Behavior

Output is visibly corrupted during streaming. Examples seen:
- Partial tokens rendered before full token is available (e.g. `apil` instead of `apiVersion`)
- Characters doubled mid-word (e.g. `obserrvability`, `permpermissions`)
- Words repeated mid-sentence (e.g. `New ReliNew Relic`, `useruser`)
- Lines repeated (e.g. `metadata:` block appearing twice)
- Thinking/reasoning tokens streamed visibly with same corruption artifacts

Example corrupted output observed:
```
apil
apiVersion: rbac.authorization.k8s.io/v1
...
- apiGroups: [piGroups: [""]
```

## Expected Behavior

Output should render cleanly with no corruption, doubled characters, or repeated lines.

## Environment

- Copilot CLI version: 1.0.61
- OS: Darwin (macOS)

## Notes

The underlying content being generated is correct — the issue is purely in how the CLI streams and renders tokens to the terminal.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Start by reproducing the corruption in the Copilot CLI terminal renderer on macOS, comparing thinking/reasoning and final-response streaming. Trace how the renderer handles partial tokens and line updates; done means streamed output matches the underlying content without doubled characters, truncation, or repeated lines.

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

Evaluación

Stack tecnológico
shell
Área
cli
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Tranquilo
Claridad
Bastante claro
Aptitud para principiantes
45/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.