anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Favorite Models List #392

New Issue
Closed
opened 2026-02-16 17:26:34 -05:00 by yindo · 5 comments
yindo commented 2026-02-16 17:26:34 -05:00
Owner
Copy Link
Copy Source

Originally created by @timoclsn on GitHub (Jun 29, 2025).

Originally assigned to: @adamdotdevin on GitHub.

I love the multi-model and provider nature of opencode because I like to use different models for different use cases (planning/architecting, implementing, etc.).

To make that switching easier, I would like to have the possibility to define favorite models (across providers) and to switch between them quickly:

  • Define a "favoriteModels" list in my config
  • Display my favorite models list as the first "page" in the models dialog
Originally created by @timoclsn on GitHub (Jun 29, 2025). Originally assigned to: @adamdotdevin on GitHub. I love the multi-model and provider nature of opencode because I like to use different models for different use cases (planning/architecting, implementing, etc.). To make that switching easier, I would like to have the possibility to define favorite models (across providers) and to switch between them quickly: - Define a "favoriteModels" list in my config - Display my favorite models list as the first "page" in the models dialog
yindo closed this issue 2026-02-16 17:26:34 -05:00
yindo commented 2026-02-16 17:26:34 -05:00
Author
Owner
Copy Link
Copy Source

@thdxr commented on GitHub (Jun 29, 2025):

@adamdotdevin having a single list sorted by last used would fix this

@thdxr commented on GitHub (Jun 29, 2025): @adamdotdevin having a single list sorted by last used would fix this
yindo commented 2026-02-16 17:26:34 -05:00
Author
Owner
Copy Link
Copy Source

@adamdotdevin commented on GitHub (Jun 29, 2025):

yeah, @timoclsn, dax and i had worked out an ideal form of the model dialog:

  • do away with provider navigation and just list all available models, sorted by last used date and then release date desc (newly added to models.dev)
  • for each model we render model name (default text color) and provider name (muted text color)
  • as you use models, they end up at the top of the list (last used date sort)

i get that this is a bit more involved than the work you had done for favorite models, but are you up to taking this on?

@adamdotdevin commented on GitHub (Jun 29, 2025): yeah, @timoclsn, dax and i had worked out an ideal form of the model dialog: - do away with provider navigation and just list all available models, sorted by last used date and then release date desc (newly added to models.dev) - for each model we render model name (default text color) and provider name (muted text color) - as you use models, they end up at the top of the list (last used date sort) i get that this is a bit more involved than the work you had done for favorite models, but are you up to taking this on?
yindo commented 2026-02-16 17:26:34 -05:00
Author
Owner
Copy Link
Copy Source

@timoclsn commented on GitHub (Jun 30, 2025):

I like the current multipage nature of the models picker because the models list can get quite long when you have a lot of providers configured.

But I understand where you are probably coming from. With one list and the most recent on the top, it works out of the box without needing to configure anything 😍.

I'll take a shot at it, but it will need a thorough code review as I've never written any Go before.

@timoclsn commented on GitHub (Jun 30, 2025): I like the current multipage nature of the models picker because the models list can get quite long when you have a lot of providers configured. But I understand where you are probably coming from. With one list and the most recent on the top, it works out of the box without needing to configure anything 😍. I'll take a shot at it, but it will need a thorough code review as I've never written any Go before.
yindo commented 2026-02-16 17:26:34 -05:00
Author
Owner
Copy Link
Copy Source

@adamdotdevin commented on GitHub (Jun 30, 2025):

yeah, i think if we also sort by release date desc its going to be a pretty nice experience up front even, lots of providers or not. should have the models that matter at the top from the start.

@adamdotdevin commented on GitHub (Jun 30, 2025): yeah, i think if we also sort by release date desc its going to be a pretty nice experience up front even, lots of providers or not. should have the models that matter at the top from the start.
yindo commented 2026-02-16 17:26:34 -05:00
Author
Owner
Copy Link
Copy Source

@timoclsn commented on GitHub (Jun 30, 2025):

See https://github.com/sst/opencode/pull/563 for a first prototype 😊

@timoclsn commented on GitHub (Jun 30, 2025): See https://github.com/sst/opencode/pull/563 for a first prototype 😊
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#392
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?