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

@ag-ui/client - textMessageBuffer not populated when emitting events directly

未关闭
#888 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
bug SDK
主要语言
Python
星标
15.9k
派生
1.4k
平均合并
1 天 17 小时
30 天内合并 PR
163

描述

When extending AbstractAgent and emitting TEXT_MESSAGE_* events directly via the subscriber (not through HttpAgent with a server), the textMessageBuffer parameter passed to onTextMessageContentEvent is empty/undefined.

This appears to be because textMessageBuffer is computed by defaultApplyEvents which looks up the message content in the managed messages array. When events are emitted directly without going through defaultApplyEvents, no message objects are created, so the buffer lookup fails.

Questions:

Is this the intended behavior?
Should AbstractAgent maintain its own text buffer for direct event emission use cases?
Should the documentation clarify that textMessageBuffer only works when using the built-in event processing pipeline?

As a workaround I am manually accumulating deltas in an onEvent handler

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。