問題文
A multi-turn assistant must keep context across turns without the application resending the whole history. Which design does the service provide for this?
選択肢
- Upload the transcript to the Files API after every turn and reference the file in the next request, because the Responses API has no notion of a conversation.
- Create a conversation with the Conversations API and pass its identifier in each Responses API request, so the service manages the state.
- Reuse the same container for the whole session, and the turns of the conversation are then kept in the container workspace.
- Enable long-term memory on the project, which makes the service attach the full transcript of each earlier conversation to every new request.