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

[FEATURE]: dynamic model list for copilot plugin #9254

New Issue
Open
opened 2026-02-16 18:12:00 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:12:00 -05:00
Owner
Copy Link
Copy Source

Originally created by @nulladdict on GitHub (Feb 13, 2026).

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

some context on the models.dev side: https://github.com/anomalyco/models.dev/issues/885#issuecomment-3895389479

currently copilot plugin has some annoying papercuts in the way the model access is handled
the model lists comes from models.dev and it's the same list for everyone but:

  • some models are only allowed on pro+ or enterprise plan (as of writing it's opus 4.6 fast)
  • most new models have a long-ish rollout window
  • enterprise admins can enable/disable specific models

so users run into issues:

  • when new models roll out we have to wait for rollout to end before adding them to models.dev. otherwise some users will have broken (not yet active) models in the list. which is very annoying because rollout takes a lot of time and the model might be already usable for a large portion of users in vscode
  • when we have models available on certain plans we can either ignore them fully (like opus 4.6 fast) or have them broken for users on a lower plan
  • when we admin disables some models they still appear in the model picker and cause issues

i think the correct way to do this is to:

  • add all models to models.dev regardless of the rollout status or plan access
  • query available models per-user in the copilot plugin and remove unavailable models from the provider. codex plugin already does some (static) filtering so i think the approach is sound
Originally created by @nulladdict on GitHub (Feb 13, 2026). 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 some context on the models.dev side: https://github.com/anomalyco/models.dev/issues/885#issuecomment-3895389479 currently copilot plugin has some annoying papercuts in the way the model access is handled the model lists comes from models.dev and it's the same list for everyone but: - some models are only allowed on pro+ or enterprise plan (as of writing it's opus 4.6 fast) - most new models have a long-ish rollout window - enterprise admins can enable/disable specific models so users run into issues: - when new models roll out we have to wait for rollout to end before adding them to models.dev. otherwise some users will have broken (not yet active) models in the list. which is very annoying because rollout takes a lot of time and the model might be already usable for a large portion of users in vscode - when we have models available on certain plans we can either ignore them fully (like opus 4.6 fast) or have them broken for users on a lower plan - when we admin disables some models they still appear in the model picker and cause issues i think the correct way to do this is to: - add all models to models.dev regardless of the rollout status or plan access - query available models per-user in the copilot plugin and remove unavailable models from the provider. codex plugin already does some (static) filtering so i think the approach is sound
yindo added the discussion label 2026-02-16 18:12:00 -05:00
yindo commented 2026-02-16 18:12:01 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 13, 2026):

This issue might be related to or provide context for these existing issues:

  • #12954: [FEATURE]: 5.3 Codex for Github Copilot provider
  • #13313: Github Copilot GPT 5.3 Codex - Requested Model is not supported
  • #13312: Codex 5.3 not working with copilot
  • #12415: Not all co-pilot models are listed
  • #13164: [FEATURE]: Do not automatically activate new models

Your feature request addresses the root cause of why users run into these model availability issues. Consider linking to this issue when it's triaged.

@github-actions[bot] commented on GitHub (Feb 13, 2026): This issue might be related to or provide context for these existing issues: - #12954: [FEATURE]: 5.3 Codex for Github Copilot provider - #13313: Github Copilot GPT 5.3 Codex - Requested Model is not supported - #13312: Codex 5.3 not working with copilot - #12415: Not all co-pilot models are listed - #13164: [FEATURE]: Do not automatically activate new models Your feature request addresses the root cause of why users run into these model availability issues. Consider linking to this issue when it's triaged.
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 discussion
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#9254
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?