mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-22 01:55:27 -04:00
Dify's Xinfrence plug-in does not support thinking model switch control and output format control. Xinference has officially tested this part of the function, but it is not displayed here in dify. #710
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bianningtao on GitHub (Oct 13, 2025).
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
Dify's xinfrence plug-in does not support thinking model switch control and output format control. Xinference has officially tested this part of the function, but it is not displayed on dify. The qwen series already supports this part of the function. I use the model deployed privately by xinfrence.
Xinfrence plugin version is 0.0.7
2. Additional context or comments
No response
3. Can you help us with this feature?
@dosubot[bot] commented on GitHub (Oct 13, 2025):
Hi @bianningtao! I'm Dosu and I’m helping the dify-official-plugins team.
You're correct: the Xinfrence plugin (v0.0.7) for Dify does not currently support model switch control or output format control, even though Xinference itself supports these features and other plugins (like Qwen/Tongyi) have implemented them. This gap is tracked in an open issue labeled "help wanted" for contributions.
To add these features, you can look at how plugins like OpenRouter and Tongyi/Qwen handle them. For example, they add parameters such as
enable_thinking,reasoning_budget, andresponse_formatin their model YAML files and handle these in the Python code to pass the correct options to the backend API. The Xinfrence plugin would need similar updates: extend the model schema to accept these parameters, update the invocation logic to forward them to Xinference, and ensure the UI/config exposes these controls to users. You can use the Qwen or OpenRouter plugin implementations as a reference for both parameter handling and config structure [OpenRouter example] [Tongyi/Qwen example].If you want to contribute, start by updating the Xinfrence plugin's model schema and invocation logic to support these parameters, then test with your private Xinference deployment. The open issue (#1854) is the right place to coordinate or discuss your approach.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

@simons19920101 commented on GitHub (Oct 14, 2025):
"I also added the Xinference qwen model. The model loads successfully, but when calling the model in the Dify application chat scenario, the plugin_daemon sends a stream: true request, Xinference returns an SSE response, but the Dify api service ultimately receives an empty answer."
@dosubot[bot] commented on GitHub (Oct 30, 2025):
Hi, @bianningtao. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!
@bianningtao commented on GitHub (Oct 30, 2025):
Yes, it still exists.
@dosubot[bot] commented on GitHub (Nov 16, 2025):
Hi, @bianningtao. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!
@bianningtao commented on GitHub (Nov 19, 2025):
still exists
@dosubot[bot] commented on GitHub (Dec 5, 2025):
Hi, @bianningtao. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!