Repository navigation
Replies: 1 comment
|
Confirmed on Windows 11 with For one ordinary session, A few acceptance details that would make the composer search especially useful:
This is distinct from #3147, which adds filtering and bulk selection to the provider model-candidate picker in Settings. This request is specifically for the per-session composer component at This small UX improvement would save substantial time for OpenRouter and other large catalogs. Thanks for raising it. |
Uh oh!
There was an error while loading. Please reload this page.
Add search/filter to the composer model dropdown
Problem
When I click the model selector in the composer bar (the trigger that shows "DeepSeek-V4-Flash" or whatever model is currently active), I get a dropdown with all provider groups and their models listed out. If a provider has a lot of models — which is common with OpenRouter or custom providers — this list gets really long and I have to scroll through everything to find what I want.
The weird thing is: if I type
/modelinstead, the popup that opens already has a search box that filters models by name. So the search capability exists in the codebase (filterOptionsinui-commands/popup.ts), it's just not available in the composer trigger that a lot of people actually use.I almost forgot that I could also use
/model— I just click the model button like I do in other chat UIs. The current dropdown works fine when there are only a few models, but becomes painful at scale.What I'd expect
Click the model trigger → the model pane opens → there's a small search input at the top where I can type "qwen" or "glm" and the list filters down in real time. Basically the same experience as the
/modelpopup, but in the dropdown I already use.Affected code
packages/client/ui-model-selection/src/client/ModelSelect.tsx— the composer model seatpackages/client/ui-commands/src/client/popup.ts— already hasfilterOptions()that could be reusedPossible solution
Add a compact search input to the
pane === 'model'view inModelSelect, wired to the samefilterOptionslogic the/modelpopup already uses. The search could sit at the top of the model list, filter thestate.groups→modelshierarchy by name, and disappear or collapse when not needed.Not sure about the exact UI design... the team knows this better than I do but the core ask is just: let me search the model list from the composer trigger, not just from
/model.All reactions