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

[FEATURE]: Help user discover their provider/model pair availability #9386

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

Originally created by @cbrunnkvist on GitHub (Feb 15, 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

I am missing an easy way to check in with each of the models listed by opencode models to see which ones are actually available via API for me to use, today, now.

I think of this action as a "roll call", like the one you do at the morning in school (or in prison, eheh) to check for any absence.

I have actually been doing this already, with a bash for-loop and a lot of opencode run, but that way is painfully slow for obvious reasons - launching opencode from scratch a hundred times, new sessions, managing timeouts ... and then on top of that, I have to parse the somewhat unstructured output of my survey. I don't want to invest more time in a custom script for this - opencode already knows how to switch between its provider-model pairs - there should be a built-in way to perform this type of survey/diagnostic on behalf of the user.

Originally created by @cbrunnkvist on GitHub (Feb 15, 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 I am missing an easy way to _check in with each of the models_ listed by `opencode models` to see which ones are _actually_ available via API for me to use, today, _now_. I think of this action as a "roll call", like the one you do at the morning in school (_or in prison, eheh_) to check for any absence. I have actually been doing this already, with a bash `for`-loop and a lot of `opencode run`, but that way is _painfully slow_ for obvious reasons - launching opencode from scratch a hundred times, new sessions, managing timeouts ... and then on top of that, I have to parse the somewhat unstructured output of my survey. I don't want to invest more time in a custom script for this - opencode already knows how to switch between its provider-model pairs - there should be a built-in way to perform this type of survey/diagnostic on behalf of the user.
yindo added the discussion label 2026-02-16 18:12:19 -05:00
yindo commented 2026-02-16 18:12:19 -05:00
Author
Owner
Copy Link
Copy Source

@cbrunnkvist commented on GitHub (Feb 15, 2026):

My goal is to take the output of this, and make an /audition kind of helper for OmO, and something like this in opencode would be an enormously useful building block for that.

@cbrunnkvist commented on GitHub (Feb 15, 2026): My goal is to take the output of this, and make an `/audition` kind of helper for OmO, and something like this in opencode would be an enormously useful building block for that.
yindo commented 2026-02-16 18:12:19 -05:00
Author
Owner
Copy Link
Copy Source

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

Thanks for the detailed feature request! This is a well-articulated request with clear use cases.

You might also want to check #4734: "[FEATURE]: Refresh models manually" which covers related model list refresh functionality, though your proposal for a batch availability audit tool is a distinct use case.

@github-actions[bot] commented on GitHub (Feb 15, 2026): Thanks for the detailed feature request! This is a well-articulated request with clear use cases. You might also want to check #4734: "[FEATURE]: Refresh models manually" which covers related model list refresh functionality, though your proposal for a batch availability audit tool is a distinct use case.
yindo commented 2026-02-16 18:12:19 -05:00
Author
Owner
Copy Link
Copy Source

@cbrunnkvist commented on GitHub (Feb 15, 2026):

Real-user story: as one of the 99% that can't afford a monthly $200 Anthropic pass, I have often found myself switching between several providers, assign different models to different agents or specializations, in order to get around quotas, rate limits, but also because I like to experiment with different models. I think being able to make a roll-call would be a genuinely useful feature.

@cbrunnkvist commented on GitHub (Feb 15, 2026): Real-user story: as one of the 99% that can't afford a monthly $200 Anthropic pass, I have often found myself switching between several providers, assign different models to different agents or specializations, in order to get around quotas, rate limits, but also because I like to experiment with different models. I think being able to make a roll-call would be a genuinely useful feature.
yindo commented 2026-02-16 18:12:19 -05:00
Author
Owner
Copy Link
Copy Source

@cbrunnkvist commented on GitHub (Feb 15, 2026):

Thanks for the detailed feature request! This is a well-articulated request with clear use cases.

You might also want to check #4734: "[FEATURE]: Refresh models manually" which covers related model list refresh functionality, though your proposal for a batch availability audit tool is a distinct use case.

That's a nice feature too, but it's solving a differnt problem. I don't necessarily need to REFRESH the list, I just need to validate that my currently assigned org/project/API keys and/or subscriptions are available or not - OR which ones are temporarily unavailable due to rate-limits. I don't want it to remove anything from the list in that case.

@cbrunnkvist commented on GitHub (Feb 15, 2026): > Thanks for the detailed feature request! This is a well-articulated request with clear use cases. > > You might also want to check [#4734](https://github.com/anomalyco/opencode/issues/4734): "[FEATURE]: Refresh models manually" which covers related model list refresh functionality, though your proposal for a batch availability audit tool is a distinct use case. That's a nice feature too, but it's solving a differnt problem. I don't necessarily need to REFRESH the list, I just need to validate that my currently assigned org/project/API keys and/or subscriptions are available or not - OR which ones are temporarily unavailable due to rate-limits. I don't want it to remove anything from the list in that case.
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#9386
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?