How can I grab the message id of AzureAIAgent assistant responses?

[mollaosmanoglu]

I’m using Semantic Kernel (Python) with Azure AI Agents and running into a frustrating limitation.

In my app, I stream responses from the agent and extract citations from StreamingAnnotationContent chunks. The idea is to pair those citations with the exact assistant message they came from so my frontend can contain the citations in the user/assistant pair, which means I need the assistant message’s service id.

The problem is: SK doesn’t expose the Azure message id on the streamed message objects, only the thread_id. For the user message it’s fine, I create it manually via client.agents.messages.create(...) and get its id right away. But for the assistant message, SK starts streaming without giving me its id.

The only workaround I’ve found is to, right after the first streamed delta, poll client.agents.messages.list(thread_id, order="desc", limit=1) to grab the latest assistant message’s id and then attach citations to it.

So the question is: is there any way in SK to get the assistant message id immediately when streaming starts? Or do I have to either keep polling or ditch SK and consume the Azure AI Agents stream directly since it provides a thread.message.created event which includes the message id?

[moonbox3]

Hi @mollaosmanoglu, thanks for surfacing this and for the feedback. We appreciate it.

In agent_thread_actions, we can add handling for the AgentStreamEvent.THREAD_MESSAGE_CREATED event, and hold on to the id. Would it help your use case if we return the thread_message_id as part of the response chunk's metadata dict? This would allow you to get a handle to that id if/when we have a handle to it.

[mollaosmanoglu]

Hi @moonbox3 , thank you for your response. That would indeed be great!

[moonbox3]

Thanks for the response, @mollaosmanoglu. I will get that out this week. I've turned this discussion into the following issue: #12959. Please follow along there for further updates. I'll tag that issue with the PR when it's ready.