mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
Missing content(only reasoning_content) when enable thinking by deepseek-ai/DeepSeek-V3.2(siliconflow) in Agent #871
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 @leslie2046 on GitHub (Dec 12, 2025).
Self Checks
Dify version
1.11.0
Plugin version
0.0.37
Cloud or Self Hosted
Self Hosted (Source)
Steps to reproduce
✔️ Error log
No response
@dosubot[bot] commented on GitHub (Dec 12, 2025):
This is a known issue with DeepSeek models: when thinking mode is enabled, sometimes only the reasoning_content is returned and the final content is missing. This often happens due to output handling bugs in the plugin, especially with streamed responses that use string replace operations, which can cause missing or incomplete content. Similar problems have been reported for DeepSeek v3.1 and v3.2 in both siliconflow and other providers (example, details and workaround).
If you are self-hosted and comfortable patching code, a common workaround is to modify the plugin's streamed output handling: instead of using string replace to build up the response, append new content directly (e.g.,
full_text += resp_content[len(full_text):]). This prevents character loss and empty output.Other things to try: increase the max_tokens parameter, reduce prompt size, or split large knowledge base chunks. If direct API calls to DeepSeek-V3.2 with thinking mode enabled return both reasoning_content and content, the issue is almost certainly in the plugin's output handling logic.
Keep an eye out for plugin updates, as this area is under active development. If you need more details on where to patch, let me know your deployment details and I can point you to the relevant code section.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@leslie2046 commented on GitHub (Dec 21, 2025):
This is due to the unstable use of the thinking mode enabled tool in the DeepSeekV3.2 model itself.
The reasons are as follows.
10/10 enable think
10/10 disable think
1/10 enable think
2/10 disable think
1. sometimes response no tool_calls
2. sometimes response with tool_calls