ag-ui-protocol / ag-ui-protocol/ag-ui

Agent Spec integration emits TextMessageChunk instead of TextMessageContent

未關閉
#1,625 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
bug Integration
主要語言
Python
星號
15.9k
分支
1.4k
平均合併
1 天 17 小時
30 天內合併 PR
163

描述

I dunno if this was intentional, but the agent-spec/python integration appears to be emitting TextMessageChunk events rather than TextMessageContent events.

It seems to differ from how other integrations work. I know that the docs say that TextMessageChunk is supposed to expand out to TextMessageStart, TextMessageContent, and TextMessageEnd automatically, but the events I'm observing in my SSE stream just show the TextMessageChunk events only. Is this auto-expansion expected to be handled manually by the consuming client?

Also, it seems like we have a missed opportunity here when the `langgraph` runtime is in use with the integration, the `LangGraphAgent` adapter from the `ag-ui-langgraph` package could be leveraged to maintain consistent behavior. Was there a reason why it's not being used for that runtime?

UPDATE: Okay, I just tried using `LangGraphAgent`, and `add_langgraph_fastapi_endpoint` from the `ag-ui-langgraph` package directly instead of `ag-ui-agent-spec`, and it appears to be working.

Thanks.

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。