`responses` corrupts previous conversations `assistant` item

Yes, this appears to be a bug and it is easily reproducible. Looking for an unblocker, I think @merefield is on to something with the question about how instructions are being used here. To me, it looks like the hardcoded assistant message actually contains instructions. In that case, the hardcoded message could instead be added as an instruction to each model request. Two other perspectives: * Replacing the corrupted hardcoded message after each call is probably the quickest fix, but it adds latency and is ultimately just a workaround. It also needs to happen after every Responses API call because the bug will reappear with each new assistant message. * If possible, use only the Responses API, since this issue does not appear there. The tradeoff is that you need to manage conversation state yourself instead of relying on server-side state management. Since you mentioned that you are still expanding your knowledge, this could also be a good opportunity to deepen your understanding of how chat applications are built. Hope this helps!