github / github/copilot-cli

Input box pre-filled with DA1 device-attributes reply ( [?61;6;7;…c ) on startup under native-Windows zellij

Aperta
#4,267 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub
area:input-keyboard area:platform-windows area:terminal-rendering
Lingua principale
Shell
Stelle
11.2k
Fork
1.9k
Merge medio
14h 16m
PR unite (30g)
6

Descrizione

### Describe the bug

Describe the bug

When launching Copilot CLI inside a native-Windows zellij session, the input box is pre-filled on startup with a raw terminal escape sequence:

[?61;6;7;22;23;24;28;32;42c

This is a Primary Device Attributes (DA1) reply — the response to a  ESC [ c  capability query. It's meant to be consumed silently, but instead the raw bytes land in the prompt as if typed. I have to clear the box (Ctrl+U) before every session.

This looks like the same class of bug as the already-fixed #36 ("Input box always filled with escape sequence  ]11;rgb:…  on start"), which  niik  traced to Copilot querying the host terminal at startup (there: OSC 11 background color). That fix (0.0.355) evidently didn't cover the DA1 ( ESC[c ) query path.

Affected version

Copilot CLI 1.0.75 (win32-x64)

Steps to reproduce

1. On Windows 11, open Windows Terminal.
2. Start a native-Windows zellij session ( zellij ).
3. Inside a zellij pane, launch  copilot .
4. Observe the input box pre-filled with  `[?61;6;7;22;23;24;28;32;42c` .

Expected behavior

The DA1 reply is consumed by Copilot CLI; the input box starts empty.

Environment

• Copilot CLI: 1.0.75 (win32-x64)
• OS: Windows 11 Enterprise, build 26200
• Terminal emulator: Windows Terminal 1.18.10301.0
• Multiplexer: zellij 0.44.3 (native Windows — no WSL), which added a "host query forwarding" system in 0.44.x that relays capability queries between the inner app and the host terminal. The DA1 reply appears to arrive after Copilot has stopped reading, so it leaks into the input buffer.
•  TERM : (unset on native Windows)
• Process chain:  zellij → pwsh → copilot 

Additional context

• Does not occur when running  copilot  directly in Windows Terminal (no zellij) — pointing to a timing/consume issue on the query-response path when a multiplexer sits in between.
• Decoded sequence: `ESC [ ? 61 ; 6 ; 7 ; 22 ; 23 ; 24 ; 28 ; 32 ; 42 c  = DA1` reply, VT conformance level 61 + advertised feature codes.
• Related prior fix: #36 (OSC 11 reply on start, fixed in 0.0.355).

### Affected version

_No response_

### Steps to reproduce the behavior

_No response_

### Expected behavior

_No response_

### Additional context

_No response_

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Inizia dalla gestione di terminal-query e input-buffer all'avvio di Copilot CLI, confrontando il percorso della risposta DA1 con la correzione precedente per OSC 11 in issue #36. Riproducilo su Windows nativo con zellij 0.44.3, quindi traccia quando arriva la risposta e verifica che il prompt rimanga vuoto, mentre il comportamento diretto di Windows Terminal resti invariato.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
powershell, shell
Ambito
cli, operating-systems, tooling
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Tranquilla
Chiarezza
Abbastanza chiara
Idoneità per principianti
48/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.