Thinking Start & End events not supported by EventSchemas

[nicholasrice]

Hello! A bug/question for ya'll.

I noticed doing some experimentation that the EventSchemas parser will throw when attempting to parse THINKING_START and THINKING_END event types. It seems to only support THINKING_TEXT_MESSAGE_START, THINKING_TEXT_MESSAGE_CONTENT, and THINKING_TEXT_MESSAGE_END event types. The @ag-ui/core library does expose specific schemas that parse THINKING_START and THINKING_END event-types though.

It got me thinking maybe THINKING_START and THINKING_END events are deprecated but not indicated so in code?

More generally, I don't see any documentation about the thinking events in AGUI documentation, so I wasn't sure what the state of those event types were.

See min-repro here: https://stackblitz.com/edit/stackblitz-starters-15zqkndn?file=index.js

[nicholasrice]

This is maybe a dupe of #211, though I'm still curious how the two sets of thinking events are intended to relate.

[evestorm]

I’ve encountered a similar issue. I’m currently trying to use the ag-ui protocol in my project, but I noticed that the documentation doesn’t mention any events for Thinking Start & End. However, I did find three events in @ag-ui/core that seem similar to the text message events:
• ThinkingTextMessageStartEvent
• ThinkingTextMessageContentEvent
• ThinkingTextMessageEndEvent

When I checked their definitions, I saw that—unlike TextMessageStartEvent—they don’t have a messageId field.

This makes me wonder: without a messageId or another unique field, how should I match the corresponding Thinking events together?

Any clarification or guidance would be greatly appreciated. Thank you!

[ranst91]

#341
They were missing. Added in this PR

[librajt]

#341 They were missing. Added in this PR

Great! Maybe also need add the subscriber events ?

[goyamegh]

I see this was closed: #211, accidentally I presume?

[librajt]

I see this was closed: #211, accidentally I presume?

Try version 0.0.37, it works well for me, but no subscriber events for 'ThinkingStart' or 'ThinkingEnd', I used 'onEvent' instead, for now