-
Notifications
You must be signed in to change notification settings - Fork 59.8k
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
[Feature Request] 不同的模型(即使同为兼容OpenAI)设置不同的key和url #5984
Labels
enhancement
New feature or request
Comments
Title: [Feature Request] Different models (even if they are both compatible with OpenAI) set different keys |
bestsanmao
changed the title
[Feature Request] 不同的模型(即使同为兼容OpenAI)设置不同的key
[Feature Request] 不同的模型(即使同为兼容OpenAI)设置不同的key和url
Dec 26, 2024
bestsanmao
added a commit
to bestsanmao/ChatGPT-Next-Web-Forked
that referenced
this issue
Dec 27, 2024
…deepseek-chat&deepseek-corder models), so that user can use openai and deepseek at same time with different api url&key
comradez
pushed a commit
to comradez/NextChat-for-deployment
that referenced
this issue
Dec 27, 2024
…deepseek-chat&deepseek-corder models), so that user can use openai and deepseek at same time with different api url&key
Dogtiti
added a commit
that referenced
this issue
Dec 29, 2024
since #5984, add DeepSeek as a new ModelProvider (with deepseek-chat&deepseek-coder models), so that user can use openai and deepseek at same time with different api url & key
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🥰 Feature Description
现在模型越来越多,大多数新出的模型api都兼容openai,但是不同的模型有不同的key和api url。当前的nextchat如果自定义模型(环境变量中设的自定义模型)设为@openai
就只能使用全局的唯一的一个key和api url
🧐 Proposed Solution
希望能在环境变量设置自定义模型时指定不同的key和api url
📝 Additional Information
No response
The text was updated successfully, but these errors were encountered: