Unverified50% confidenceFactExact time
Session communication is done through an event stream: the frontend sends user.message events, and the backend listens to the SSE stream and pushes the agent's responses back to the browser in real time.
1
Sources
50%
Confidence
Long-term
Relevance
10/25/2026
First Seen
Sources
Related Entities
Related Claims
VerifiedSSE or WebSocket protocols can push the model's token-by-token generated content to the front end in real time, enabling streaming responses from the Agent74% similarVerifiedIn multi-turn conversations, the System message sets the behavioral tone and constraints, the user message represents user input, and the assistant message is the model's historical replies.72% similarUnverifiedEvent-driven triggers can process messages as soon as they arrive, whereas scheduled polling has a latency window.72% similarUnverified节点间通过话题进行异步消息发布/订阅，适合持续性数据流；通过服务进行同步请求/响应，适合一次性任务71% similarUnverifiedMid-conversation interjection faces the coordination problem between streaming generation and the message queue: newly arriving user input must either be cached for the next round of requests or injected into the current context via an interrupt/append mechanism.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1095353API
curl https://kongchang.com/api/v1/knowledge/claims/1095353MCP
get_claim(id=1095353)