Request: Clarifying Conversation Handling in conversations API

[tomfuller71]

Has anyone successfully used the Conversations API to replicate the old “thread” concept from the Assistants API?

My assistant conversations can get quite long, and I’d like to implement a flow similar to the previous thread model:

Initial Message

I can use the sendMessage function returned from the useChat hook to include a ChatRequestOptions headers object with a firstMessage: true header. I can use this in my api route to trigger the creation of a new conversation using the Conversations API and receive the conversation_id (similar to the old “create thread”). In my API route, I would then create a chat session record in my database to hold UIMessages plus metadata.

How should I send the conversation_id back to the client?

• Is it included in providerMetadata on finish?
• Can the useChat hook be extended to maintain state for conversationId?

Subsequent Messages

If I can receive the conversation_id client-side, I can include it as a header option in sendMessage. But how do I pass this same conversation_id to streamText in my api route so that it gets included in the underlying Response API call?