Model picker: no visual contrast between selected/unselected context-window value (e.g. "264K 1M")
Nessuno ha ancora preso questa issue.
- Lingua principale
- Shell
- Stelle
- 11.2k
- Fork
- 1.9k
- Merge medio
- 14h 16m
- PR unite (30g)
- 6
Descrizione
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
- Run
copilotinside VS Code's integrated terminal. - Trigger the model picker (e.g. run
/model, or open the panel shown after switching models for the session). - Look at the "Context" column for a model with two context sizes, e.g. "Claude Opus 5" showing
264K 1M. - 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.
- 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
Contextvalues in either theme:
VS Code light theme:
VS Code dark theme:
- 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.
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia dal punto di ingresso /model della copilot CLI e riproduci il selettore dei modelli con un modello che mostri due valori di contesto, come 264K e 1M. Esamina il rendering del selettore e alterna il valore con Tab; il lavoro è completato quando il valore attivo è visibilmente distinto da quello inattivo sia nei temi del terminale chiaro sia in quelli scuri.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- shell
- Ambito
- accessibility, cli, design
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Attiva
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 58/100