-
-
Notifications
You must be signed in to change notification settings - Fork 341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Completion model provider should be traitlet-configurable #781
Comments
Also, since we separated into two models (chat and completion), the API keys will most likely be different. How can I authenticate both models with different API keys with only one field? Thanks. |
For now, we would probably only want to only add |
The API keys are a key-value mapping so maybe that is not a problem? If you use cohere for chat you would set "default_api_keys": {
"COHERE_API_KEY": "MY_KEY_1",
"OPENAI_API_KEY": "MY_KEY_1"
} and respective providers would take the key they need. Does it makes sense? |
But in fact is that I am using two models that are both with OpenAI compatible APIs, that is:
When we use those self-hosting models for chat and completions, most likely will use something like vllm to provide OpenAI compatible API Servers. Hence, that is the fact that both completion and chat model will be OpenAI API like. |
Hoping to help get some momentum on this issue. A link to my comments on a related/duplicate issue: TL;DR - it does not currently seem possible to configure the Completions solely from the |
The text was updated successfully, but these errors were encountered: