Do not wrap reasoning_content into <think> tags!!! #41

Open
opened 2026-02-15 21:15:25 -05:00 by yindo · 0 comments
Owner

Originally created by @Devindan on GitHub (Jun 19, 2025).

It's time to discard the tags <think> and </think>.
If the LLM interface already has reasoning_content and content fields, it is more useful to directly use these two fields as the default output values of the LLM node, rather than forcing the already separated CoT content fields into the <think> tag.
Users can choose whether to use CoT by outputting reasoning_content or not, without having to spend effort separating it from the <think> and </think> tags.

Originally created by @Devindan on GitHub (Jun 19, 2025). It's time to discard the tags `<think>` and `</think>`. If the LLM interface already has `reasoning_content` and `content` fields, it is more useful to directly use these two fields as the default output values of the LLM node, rather than forcing the already separated CoT content fields into the `<think>` tag. Users can choose whether to use CoT by outputting `reasoning_content` or not, without having to spend effort separating it from the `<think>` and `</think>` tags.
yindo added the enhancement label 2026-02-15 21:15:25 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugin-sdks#41