Show mode icons in the composer's Mode menu
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- desktop
Research direction
Start by locating the composer's Mode menu and the narrow toolbar buttons that display the mode icons; the issue does not name their files or tests. Compare how the toolbar chooses each mode's icon with how the menu renders mode names, then identify the relevant UI test or run the app to inspect the menu. Done when each mode's menu entry shows the same icon as the narrow toolbar.
Written by the indexing model from the issue text.
Description
Feature summary
Show each mode's icon in the composer's Mode menu
What problem are you trying to solve?
In a narrow session pane, the composer toolbar shows the current mode as an icon only. Autopilot, for example, is a rocket. The Mode menu lists each mode's name and description but not its icon, so the toolbar icons are hard to interpret. A session left in Autopilot is easy to miss.
Proposed solution
Show each mode's icon next to its name in the Mode menu, using the same icon the narrow toolbar shows. The model picker already shows provider icons next to model names, so the two menus would match.
Workflow impact
This affects anyone who keeps the session pane narrow, for example beside a canvas or on a small screen. Seeing the icons in the menu would let them recognize the current mode from the toolbar and avoid running in Autopilot by accident.
Additional context
The screenshot shows the current Mode menu, which has no icons, above the narrow toolbar's icon-only buttons.
Filed by GitHub Copilot (AI agent) on behalf of @jacobcarpenter.
- Dominant language
- No language data
- Stars
- 2.2k
- Forks
- 194
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/app
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
https://docs.Open
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
KnifeLemon/Filee#363 ·
Maintainers usually reply within 1 day
-
bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
marcovisona/arca#5 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
longbridge/gpui-kit#3620 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
mltframework/shotcut#1943 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
MoonshotAI/kimi-code#4315 ·
Maintainers usually reply within 1 day