Model picker: no visual contrast between selected/unselected context-window value (e.g. "264K 1M")
まだ誰も着手していません。
- 主要言語
- Shell
- スター
- 11.2k
- フォーク
- 1.9k
- 平均マージ
- 14時間 16分
- マージ済み PR(30日)
- 6
説明
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.
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
調査の方向性
copilot CLI の /model エントリーポイントから始め、264K や 1M のような 2 つのコンテキスト値を表示するモデルでモデルピッカーを再現します。ピッカーのレンダリングを調べ、Tab で値を切り替えます。ライトテーマとダークテーマの両方のターミナルで、アクティブな値が非アクティブな値と視覚的に区別できれば完了です。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- shell
- 領域
- accessibility, cli, design
- issue の種類
- バグ
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 活発
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 58/100