You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
Please do not modify this template :) and fill in all the required fields.
Dify version
0.15.3
Cloud or Self Hosted
Cloud
Steps to reproduce
Although dify supports the integration of DeepSeek models, it has attempted to deploy many distilled versions of R1 models on its own, such as DeepSeek-R1-Distill-Qwen-32B, or directly integrate with DeepSeek-R1. However, these models are not very compatible with the React framework or agent's function call calls. In this case, a new framework is still needed for the model problem. It can be seen that AppBuilder has integrated R1 early and can call tools, and Coze has only recently integrated it. However, it has trained a new function call version of R1. Can anyone answer this question? Is it necessary to train the model.
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
The text was updated successfully, but these errors were encountered:
Self Checks
Dify version
0.15.3
Cloud or Self Hosted
Cloud
Steps to reproduce
Although dify supports the integration of DeepSeek models, it has attempted to deploy many distilled versions of R1 models on its own, such as DeepSeek-R1-Distill-Qwen-32B, or directly integrate with DeepSeek-R1. However, these models are not very compatible with the React framework or agent's function call calls. In this case, a new framework is still needed for the model problem. It can be seen that AppBuilder has integrated R1 early and can call tools, and Coze has only recently integrated it. However, it has trained a new function call version of R1. Can anyone answer this question? Is it necessary to train the model.
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
The text was updated successfully, but these errors were encountered: