You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[REQUEST] Available models/providers - easy updates + cleanup #451
Is your feature request related to a problem? Please describe.
Missing some SOTA models + it's cumbersome to update with the way models are handled throughout the code currently
Model names in UI dropdowns are a bit verbose
Describe the solution you'd like
Maybe piggy back off of some other library to automatically pull in models as they become available OR have a simple .json config file that models can easily be added to/removed from
Additional Context
By a similar vain it should probably allow users to use custom models more easily (holistic approach to defining model endpoints in JSON or in a single .ts file in the providers dir)
Also, some models are slightly different in how they handle passing through requests, so as much as we'd like to have one JSON file for us it's a decent abstraction how we have it now. If you look in the /providers file, we have the models listed there with their own transformations. Maybe we can clean it up a bit to be slightly simpler and couple some redundant logic.
Yeah that makes sense. It seemed like there were handles across several files that would need updating in addition to the actual request handling itself – it would be nice if everything was just in a anthropic.ts or bedrock.ts file (pricing, model definition, request handling, etc). Would let users quickly add any new models vs. having to make updates across the codebase
Activity
emir-karabeg commentedon Jun 3, 2025
@mkummer225 which models would you like to see?
Also, some models are slightly different in how they handle passing through requests, so as much as we'd like to have one JSON file for us it's a decent abstraction how we have it now. If you look in the /providers file, we have the models listed there with their own transformations. Maybe we can clean it up a bit to be slightly simpler and couple some redundant logic.
mkummer225 commentedon Jun 3, 2025
@emir-karabeg
AWS Bedrock, OpenRouter, Azure
Yeah that makes sense. It seemed like there were handles across several files that would need updating in addition to the actual request handling itself – it would be nice if everything was just in a
anthropic.tsorbedrock.tsfile (pricing, model definition, request handling, etc). Would let users quickly add any new models vs. having to make updates across the codebasejustserdar commentedon Jun 6, 2025
I'm working on local ollama self host model support (PR on my end), I suggest we standardize IO using something like:
https://ai-sdk.dev/docs/reference/ai-sdk-core
mkummer225 commentedon Jun 6, 2025
Yeah ai-sdk would definitely make it easier to extend, looks like there's tool calling support as well