chat api stream Content Output and Summary event is common！！！！ how to recognize them

[wisty]

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.4.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

LLM SiliconFlow deepseek-ai/DeepSeek-V3

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot[bot]]

In the Dify chat API stream, "Content Output" and "Summary" are not distinct event types in the codebase. Instead, these terms are usually abstractions for the actual stream events defined in the code. The main events you should look for are:

• Content Output: This typically corresponds to the events like message, text_chunk, or agent_message—these carry the main content or output tokens as the model generates them.
• Summary: This is usually represented by the message_end event, which signals the completion or finalization of the output stream.

You can recognize these by checking the event field in the stream payload. Only the event names defined in the StreamEvent enum (such as message, text_chunk, message_end, etc.) are used in the actual API stream—there are no protocol-level events named "Content Output" or "Summary" in the codebase or API responses. Any references to those terms are just user-facing descriptions or documentation abstractions, not actual event types in the implementation. For more details, see the relevant code for event definitions and stream handling here and here.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[wisty]

@crazywoola

[crazywoola]

Any suggestions? Feel free to open a PR :)

[wisty]

I change LLM deepseek-chat response