anomalyco / anomalyco/models.dev
Identify local providers that support discovery
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.7k
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 873
Description
Listing models here is likely the wrong approach for tools like opencode for local providers, as there are thousands of supported models, they are never deprecated, and displaying any significant amount bogs down UI. For example, only a handful of models are listed here for LM Studio, and they are older models.
Instead, providers should have a "discoverable" field, which can be used to identify that a local provider supports /v1/models, and that this is the preferred method of populating a model list rather than the hardcoded one here. Work is already being done on this model polling at https://github.com/anomalyco/opencode/pull/15732, and this would allow that feature to be easily generalized to other providers.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the provider definitions and the model-polling work referenced in opencode pull request #15732. Done means local providers can be marked discoverable and model lists use provider discovery instead of relying on large hardcoded lists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ai, backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100