github / github/copilot-cli

Model picker: no visual contrast between selected/unselected context-window value (e.g. "264K 1M")

Offen
#4,873 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

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

Beschreibung

Describe the bug

In the copilot CLI's model picker (the panel shown when switching models / after a Model changed from ... for this session message), the "Context" column for a model that offers two context-window sizes shows both values together, e.g. 264K 1M for Claude Opus 5.

There is no visible difference (weight, color, dimming, checkmark, etc.) between the currently-selected context-window value and the other one. Looking at the row, it's impossible to tell whether the session is currently using the 264K or the 1M context window — you have to trust the small Model changed from ... (1M context) for this session log line above instead of the picker itself.

This is not a light-vs-dark theme color problem: I compared VS Code's light theme and dark theme (both using the integrated terminal), and the row renders identically in both — same lack of contrast between the two values in either theme. Screenshots attached (light theme, then dark theme).

Affected version

GitHub Copilot CLI 1.0.85

Steps to reproduce the behavior
  1. Run copilot inside VS Code's integrated terminal.
  2. Trigger the model picker (e.g. run /model, or open the panel shown after switching models for the session).
  3. Look at the "Context" column for a model with two context sizes, e.g. "Claude Opus 5" showing 264K 1M.
  4. Try to tell, from the row's styling alone, which of the two values (264K or 1M) is the one currently applied to the session.
  5. Toggle it (Tab) and look again — the rendering doesn't change in a way that clarifies which value is now active.
Expected behavior

The currently active context-window value should be clearly distinguishable from the inactive one (e.g. bold + accent color for the selected one, dimmed/greyed for the other), in both light and dark terminal themes, so the user can tell at a glance which one is selected without having to scroll up and re-read the session log.

Additional context
  • Operating system: macOS (Darwin)
  • Terminal: VS Code integrated terminal
  • Reproduced identically in VS Code light theme and dark theme — same lack of contrast between the two Context values in either theme:

VS Code light theme:
Image

VS Code dark theme:
Image

  • Minor but real usability impact: before noticing the small log line above the picker, I genuinely couldn't tell whether my context-window selection had taken effect at all.

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Beginne am /model-Einstiegspunkt der copilot CLI und reproduziere den Modell-Picker mit einem Modell, das zwei Kontextwerte wie 264K und 1M anzeigt. Untersuche die Darstellung des Pickers und schalte den Wert mit Tab um; abgeschlossen ist die Aufgabe, wenn sich der aktive Wert sowohl im hellen als auch im dunklen Terminal-Theme sichtbar vom inaktiven Wert unterscheidet.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
shell
Bereich
accessibility, cli, design
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Aktiv
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
58/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.