[Bug]: `start_to_think` with no `end_to_think`
Self Checks
- [x] I have searched for existing issues search for existing issues, including closed ones.
- [x] I confirm that I am using English to submit this report (Language Policy).
- [x] Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
- [x] Please do not modify this template :) and fill in all the required fields.
RAGFlow workspace code commit ID
de24e74b4c90ec154965c1bc7dc7a0fe79e669a1
RAGFlow image version
v0.21.1-slim
Other environment information
Actual behavior
Expected behavior
增加end_to_think字段,确保前端能判断已经思考完成了
Steps to reproduce
[Bug]: agent接口/api/v1/agents/{agent_id}/completions的模型回复只有start_to_think字段,没有end_to_think字段
Additional information
No response
Hi @AI-Mart! I'm Dosu and I’m helping the ragflow team.
The /api/v1/agents/{agent_id}/completions endpoint currently does not guarantee the presence of the end_to_think field in its responses. While the backend's Canvas logic can emit both start_to_think and end_to_think fields when parsing
Reference: session.py implementation
Reference: Canvas logic
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@AI-Mart Could you please share the steps to reproduce the issue?
直接调用agent接口聊天就可以发现,或者平台自带的前端也没有识别出来,全是灰色的,没有区分思考和正常回答
@AI-Mart I cant reproduce your issue. Please provide more details. Which model and model provider you are using ?
用qwen3-32b
接口没有结束思考的字段标记
@AI-Mart
I still cannot reproduce your issue with qwen3-32b, could you provide a screen shot of your issue?
要用工作流编排调试才能遇到
@AI-Mart I still cannot reproduce your issue with qwen3-32b, could you provide a screen shot of your issue?
要用工作流编排调试才能遇到
I have same problem in agent.
We are rarely able to reproduce this issue, so there is limited assistance we can provide at this time.
Since there has been no further activity for over three weeks, we will proceed to close this issue. If the problem persists or you have additional questions, please feel free to reopen the issue or create a new one. We’re happy to assist anytime.
