mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
[OpenAI-API-compatible] The thinking model will output multiple <think> blocks. #938
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 @ran411285752 on GitHub (Jan 17, 2026).
Self Checks
Dify version
V1.10.0
Plugin version
V0.0.28-V0.0.30
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
For plugins versions V0.0.28 to V0.0.30, when using the qwen3-next-thinking-FP8 model with vLLM inference, numerous "" labels appear in DIFY during output. This issue does not occur with the same model in version V0.0.27.
✔️ Error log
No response
@dosubot[bot] commented on GitHub (Jan 17, 2026):
This is a known regression in plugin versions V0.0.28–V0.0.30 when using the qwen3-next-thinking-FP8 model with vLLM inference: extraneous
<think></think>tags appear in outputs, which did not happen in V0.0.27. The root cause is that the streaming response includes areasoning_contentfield with empty or newline content, which Dify renders as<think>blocks in the output. This is confirmed in user and maintainer discussions and is related to recent changes in how streamed reasoning content is handled in the plugin and Dify core [source].Dify now supports a
reasoning_formatsetting per workflow node:separated, Dify extracts the content inside<think>tags and exposes it as a separatereasoning_contentfield.tagged(the default for backward compatibility), it keeps the tags in the main text [source] [source].To mitigate the issue, you can try:
reasoning_formattoseparatedin your workflow node configuration to extract and hide empty<think>tags from the main output.<think>tags on the frontend or via post-processing if you want to suppress them entirely.enable_thinkingis set tofalsein your model configuration or API payload (e.g.,chat_template_kwargs: {"enable_thinking": false}), though in some plugin versions this may not fully suppress the tags due to the regression [source].A feature to control reasoning tag handling was merged in PR #23313, which adds a UI toggle and backend support for reasoning format processing [source]. If you are on a version that includes this PR, adjusting the reasoning format should help. If not, you may need to patch the plugin or filter the tags manually as a workaround.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@ran411285752 commented on GitHub (Jan 17, 2026):
reasoning_format Setting it to "separated" ，has not resolved the issue of multiple "deep thinking" labels being displayed on the frontend.
@dosubot[bot] commented on GitHub (Jan 17, 2026):
Setting
reasoning_formatto "separated" doesn't resolve the multiple "deep thinking" labels because neither the backend nor the frontend filters out empty or redundant<think>tags or reasoning_content fields—so the frontend just renders every block it receives, even if it's empty or just newlines. This is a known regression in plugin versions V0.0.28–V0.0.30 with the qwen3-next-thinking-FP8 model and vLLM inference, and recent fixes for related issues may not be present in your version [source].As a workaround, you can manually filter out empty
<think>tags or reasoning_content fields on the frontend, or patch the backend/plugin to suppress empty reasoning content before it reaches the UI. Monitoring for plugin or core updates that address this regression is also recommended. If you need, I can provide example code for frontend filtering.To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@utsumi-fj commented on GitHub (Jan 23, 2026):
This might be a duplicate of langgenius/dify-plugin-sdks#277.
@Mairuis Could you please review langgenius/dify-plugin-sdks#278 when you have time? Thank you!
@crazywoola commented on GitHub (Feb 3, 2026):
Hi @ran411285752, thanks for opening this issue.
Why this is being closed
Dify issue tracking requires English-only issue title and description for consistent collaboration.
Next steps
Please open a new issue in English and include clear details so maintainers can help efficiently.
Thanks for understanding and for your support.