-
-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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
我只在环境变量里配置了OPENAI_API_KEY和OPENAI_PROXY_URL 1.44.1更新后模型自定义排序有似乎效了,但那些多出来的模型排序优先级比这个自定义排序的优先级高 |
|
|
|
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
对于环境变量的需求还是很重要的,对于用户来说并不懂配置,希望能兼容原先的环境变量 |
The need for environment variables is still very important. For users who do not know how to configure, they hope to be compatible with the original environment variables.
|
2 是上文的<是否能在环境变量里添加自定义服务商>,设置里提供了自定义服务商,这就不用在原先的Openai服务商中配置,希望能够在变量里能添加 |
2 is the above ? Custom service providers are provided in the settings, so there is no need to configure them in the original Openai service provider. I hope that I can add them to the variables. |
This comment was marked as resolved.
This comment was marked as resolved.
The problem of sorting and refreshing not taking effect has been fixed in #5330 |
@SpeedupMaster MODEL_LIST 环境变量会保持原样,今天会兼容上,之前什么样,现在也应该是什么样;
不考虑在环境变量中添加自定义服务商,能配置的东西太少了,未来可能会考虑加一个全局范围的服务商设定,面向管理员来控制。
@coulsontl 这个是 by design ,后续这个 ai provider 的页面还会加入文生图、文生视频等各类模型,provider 也不再仅局限于 chat 类的 provider。 |
@SpeedupMaster MODEL_LIST environment variables will remain the same and will be compatible today. What was before should be what it is now;
I don’t consider adding a custom service provider in the environment variables. There are too few things that can be configured. In the future, I may consider adding a global service provider setting for administrators to control.
@coulsontl This is by design. In the future, various models such as Vincent pictures and Vincent videos will be added to the AI provider page. The provider is no longer limited to chat providers. |
the cross-region inference in aws bedrock still makes user confused; the naming issues need to be addressed Ref: #4659 |
docker部署环境下OPENAI_MODEL_LIST环境变量下各项设置失效。 |
Various settings under the OPENAI_MODEL_LIST environment variable in the docker deployment environment are invalid. |
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.
Azure 和 Groq,始终提示 KEY 不存在或错误,明明是正确的配置 |
Azure and Groq always prompt that the KEY does not exist or is wrong, but it is obviously the correct configuration. |
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.
未来是否会提供环境变量预配置自定义服务商的功能 期待 ❤️ |
Looking forward to whether the function of environment variable preconfiguration and custom service provider will be provided in the future ❤️ |
This should have been fixed? 1.45.3 Can be tested again |
@2273446670 v1.45.3 应该已经修复 |
@2273446670 v1.45.3 should have been fixed |
在 v1.45.3 中,已经按照批量插入,不做已有配置项更新的逻辑来处理了。 |
In v1.45.3, it has been processed according to the logic of batch insertion and no update of existing configuration items. |
@jiajiaxd github provider 的问题在 1.45.4 修复 |
@jiajiaxd github provider problem will be fixed in 1.45.4 |
@arvinxx Azure 好像也有问题 |
@arvinxx Azure seems to have a problem too |
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: