Is your feature request related to a problem? Please describe.
We’re seeing an issue with the Response API. The conversation_id seems to change with every message.
According to the docs here:
https://platform.openai.com/docs/guides/conversation-state?api-mode=responses#openai-apis-for-conversation-state
If we extend the code to send a third message, we’re supposed to pass the response_id from the second_response. But this response_id is different from the response_id from first_response — it has the same prefix and suffix, but the middle part changes.
This seems quite different from the Threads API, where one can keep the same thread_id for the whole conversation, even though each message has its own message_id.
Describe the solution you'd like
Thus to mitigate this issue we have to store conversation history at our end as we have added CRUD we need to add a logic to lookup previous responses to retain conversation memory
Is your feature request related to a problem? Please describe.
We’re seeing an issue with the Response API. The conversation_id seems to change with every message.
According to the docs here:
https://platform.openai.com/docs/guides/conversation-state?api-mode=responses#openai-apis-for-conversation-state
If we extend the code to send a third message, we’re supposed to pass the response_id from the second_response. But this response_id is different from the response_id from first_response — it has the same prefix and suffix, but the middle part changes.
This seems quite different from the Threads API, where one can keep the same thread_id for the whole conversation, even though each message has its own message_id.
Describe the solution you'd like
Thus to mitigate this issue we have to store conversation history at our end as we have added CRUD we need to add a logic to lookup previous responses to retain conversation memory