-
-
Notifications
You must be signed in to change notification settings - Fork 8.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
[Request] Dify provider #1563
Comments
👀 @QIN2DIM Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
🥰 Description of requirementsIs there any way to integrate the backend interface exposed by Dify into lobe-chat. 🧐 SolutionCurrently (taking Claude3 as an example): (User) --> (LobeChat) --> (RealProvider)
expected: (User) --> (LobeChat) --> (DifyAPI) --> (RealProvider)
📝 Supplementary informationThe interface exposed by DifyAPI to control the chat application (agent) is not a compatible OpenAI interface, and the return type and request parameters are different. Therefore, directly changing the environment variables |
|
dify 没有 OpenAI 格式的接口 |
dify does not have an interface in OpenAI format |
✅ @QIN2DIM This issue is closed, If you have any questions, you can comment and reply. |
🥰 需求描述
能否有任何一种方法,可以将 Dify 暴露出来的后端接口集成到 lobe-chat 中。
🧐 解决方案
目前(以 Claude3 为例):
预期:
很久之前有在 lobe-chat 提过知识库的需求,但这个议题早已 inactive 了。
Dify 上可以做更多的除 prompt 之外的编排工作。如果可以接入 DifyAPI 的话,相当于曲线套壳,接入了更丰富的生态。
目前 lobe-chat 的软件架构很灵活,公共商店的插件更新和新提供商的集成速度非常快。但也因为灵活性放弃了接入 pg 和 Milvus 之类的知识库基础设施。但类似 Dify,fastgpt 对外暴露了接口可以在其他地方接入知识库的功能。
📝 补充信息
DifyAPI 暴露的操控聊天应用(智能体)的接口并不是兼容性的 OpenAI 接口,返回类型和请求参数都不一样。所以直接改环境变量的
OPENAI_PROXY
和OPENAI_API_KEY
不起作用。The text was updated successfully, but these errors were encountered: