[FEATURE]: Keep models grouped when searching #2194

Open
opened 2026-02-16 17:34:36 -05:00 by yindo · 4 comments
Owner

Originally created by @aaryan-rampal on GitHub (Oct 20, 2025).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

I have 3 providers set up, one of which is billed per token (Openrouter) and one which is subscription (Anthropic). I usually like to use the subscription one, but when I try to search for a model, it removes this grouping and gives me everything as a flat list with provider information added.

It would be a QOL improvement for me and maybe others to keep this grouping even after the search. I see the current functionality was implemented in f1e7e7c138 but it doesn't seem like there was any specific reason that it creates a flat list upon search.

If this feature is deemed okay, I have implemented and tested this on a local dev environment, and can hook up a PR to this for review

Originally created by @aaryan-rampal on GitHub (Oct 20, 2025). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request I have 3 providers set up, one of which is billed per token (Openrouter) and one which is subscription (Anthropic). I usually like to use the subscription one, but when I try to search for a model, it removes this grouping and gives me everything as a flat list with provider information added. It would be a QOL improvement for me and maybe others to keep this grouping even after the search. I see the current functionality was implemented in f1e7e7c1383075c87859cdbb1d08d510398302a9 but it doesn't seem like there was any specific reason that it creates a flat list upon search. If this feature is deemed okay, I have implemented and tested this on a local dev environment, and can hook up a PR to this for review
Author
Owner

@aaryan-rampal commented on GitHub (Oct 20, 2025):

Image

Example of this running on dev build

@aaryan-rampal commented on GitHub (Oct 20, 2025): <img width="997" height="633" alt="Image" src="https://github.com/user-attachments/assets/03b1b62d-0748-4442-926b-b15c8ac90838" /> Example of this running on dev build
Author
Owner

@rekram1-node commented on GitHub (Oct 20, 2025):

@aaryan-rampal we have this fixed in the opentui branch, bit of cleanup to do but it will ship this week.

Image
@rekram1-node commented on GitHub (Oct 20, 2025): @aaryan-rampal we have this fixed in the opentui branch, bit of cleanup to do but it will ship this week. <img width="603" height="481" alt="Image" src="https://github.com/user-attachments/assets/7446a50b-e5b2-4f5d-9d3a-780652ab636c" />
Author
Owner

@aaryan-rampal commented on GitHub (Oct 20, 2025):

Whoops sorry, didn't see those change when I was looking through. Thanks! It will be a nice addition.

@aaryan-rampal commented on GitHub (Oct 20, 2025): Whoops sorry, didn't see those change when I was looking through. Thanks! It will be a nice addition.
Author
Owner

@rekram1-node commented on GitHub (Oct 20, 2025):

Hey not a problem at all, I don't think anyone would expect you to know what is in every branch :)

Should ship this week!

@rekram1-node commented on GitHub (Oct 20, 2025): Hey not a problem at all, I don't think anyone would expect you to know what is in every branch :) Should ship this week!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#2194