-
-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
Brand new AI provider Feedback | 全新 AI Provider 管理模块反馈 #5327
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment has been minimized.
This comment has been minimized.
the cross-region inference in aws bedrock still makes user confused; the naming issues need to be addressed Ref: #4659 |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
在使用新版 AI Provider Lobechat 呼叫 OpenAI o1 正式版模型時,發現與舊版本相同的問題,無法支援該正式版模型。以下是詳細情形與分析: 問題描述
可能原因根據目前了解,OpenAI o1 正式版針對參數做了部分調整,其中包含:
這些變更導致目前舊版本呼叫方式不再適用於 o1 正式版。 正確呼叫範例(Python)以下示範如何呼叫 OpenAI o1 正式版模型,請注意呼叫時需要符合上述調整: from openai import OpenAI
client = OpenAI()
response = client.chat.completions.create(
model="o1",
messages=[
{
"role": "developer",
"content": [
{
"type": "text",
"text": "你是一位專業的程式語言分析工程師。"
}
]
},
{
"role": "user",
"content": [
{
"type": "text",
"text": "早安!"
}
]
},
{
"role": "assistant",
"refusal": null,
"content": [
{
"type": "text",
"text": "早安!有什麼可以為您效勞的嗎?"
}
]
}
],
response_format={
"type": "text"
},
reasoning_effort="medium"
) 額外建議隨著語言模型供應商不斷推出新版本,並加入各自特有的參數(例如 OpenAI 早期便提供的 若未來能在「語言模型設定」頁面開放 客製化參數 的功能,例如可以自由指定 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
issues 如这个issues所说的,在之前就设置了azure的相关配置,然后更新了新的版本之后控制台会沿用之前的设置,新的设置不生效(模型端点不生效,例如之前写的是aaaaa => gpt-35-turbo ,现在改成了bbbbb => gpt-35-turbo,还是会请求到之前a的设置) |
issues As mentioned in this issue, the relevant configuration of azure has been set up before, and then the console will continue to use it after updating to the new version. The previous settings and new settings do not take effect (the model endpoint does not take effect. For example, what was written before was aaaaa => gpt-35-turbo, but now it is changed to bbbbb => gpt-35-turbo, the previous settings of a will still be requested) |
We released a brand new AI Provider management module in version v1.44.0, bringing a completely new experience for managing AI service providers. Based on extensive user feedback, we introduced the following in this new Provider version:
As the new feature for the beginning of 2025, we expect this new module to encompass all possibilities for the coming year, making LobeChat the most versatile client in the AI Chat field~
Important
Note: This AI Provider module upgrade is only available under the server DB. Future iterations will support pglite mode. The dexie db will maintain its original implementation and will be completely removed in v2.0.
At the same time, the AI Provider page has undergone a complete rewrite from data storage to front-end implementation in order to achieve better performance and interaction experience. Therefore, at this stage, the logic related to the original environment variables may not be implemented or may have flaws. If you encounter any scenarios that do not meet your expectations, please provide feedback below, and I will strive to complete the fix within T+1 days.
Therefore, when this post is closed, if there are still no feedback on the environment variable issue, it will be removed as a deprecated feature in V2.
我们在 v1.44.0 版本发布了全新的 AI Provider 管理模块,带来了全新的 AI 服务商管理体验。结合诸多用户反馈,我们在这一全新的 Provider 版本中,带来了:
FC
和Vision
,未来将会根据社区诉求开放更多参数,例如模型是否支持流式等);Important
注意事项:本次 AI Provider 模块升级,只在服务端 DB 与 pglite 模式下可用。而 dexie db 仍保持原有实现,后续将在 v2.0 中完全移除。
由于AI Provider 这个页面从数据存储到前端实现是一次完全的重写,以期获得更好的操作性能和交互体验。因此数据上是完全独立的两套,我们不做任何迁移,升级后你需要自行重新配置对应的 Provider。同时现阶段的实现中,和原有 环境变量 相关的部分的逻辑可能没有实现或者存在瑕疵。如果遇到不符合你的预期场景,请在下方反馈,我会争取在当天评估是否对齐原有逻辑,如需对齐, T+1 天内完成对齐。
待本帖关闭时,如果仍然没有反馈的环境变量问题,也将作为废弃功能在 V2 中移除。
作为 2025 年的开年新特性,我们期望这个新的模块能承载未来一年的全部可能性,让 LobeChat 变成 AI Chat 领域最全面的 AI 客户端 🚀
The text was updated successfully, but these errors were encountered: