logancyang
Add provider selection field for open router models
Is your feature request related to a problem? Please describe.
Open router allows users to choose just a model while under-the-hood it routes individual requests to underlying providers on the fly. They also allow for an allow-list on api requests for users to limit the potential providers on a given request, e.g.: provider": {"only": ["deepinfra"]}
Exposing provider selection as a field when adding open router models to copilot would be nice. Here is my personal use case: some open sourced models are available from first party providers only in the free-tier (for instance, you can use llama on meta hardware if you run in the free tier but not the paid tier) and third party providers only in the paid-tier (running on managed hardware in unrelated cloud providers). If you pay for a meta api key there would be no reason to pay for the open router tokens to run in the paid tier, but if you run in the free tier your requests could be routed to chute or a similar provider. In order to fully leverage your first party api key, you would want to specify only meta in the allow list on each request. As well, you may want to restrict your requests to free-tier models to go over BYOK (bring your own key with specific providers) in order to conserve free-tier requests against the rate limits since they are counted against separate pools and could incur additional costs. Currently there is no way to do this in obsidian so requests could get routed to a slower or lower context provider on free tiered requests or expend free tier requests when you have a valid paid key that could be used instead.
Describe the solution you'd like Add a field for underlying provider selection to the custom model parameters when open router is the selected provider. Likely a string array that is conditionally included on requests would work fine.
Describe alternatives you've considered The current functionality is fine but could potentially be improved as per above.
