While there's no official fix from Microsoft, there is a workaround.

The Strands Agents SDK has a built-in persistence layer for conversation history - just pass a SessionManager to the Agent constructor.

I’m experiencing the same issue. I have a multi-agent workflow in Agent Builder with “Include chat history” enabled on all agent nodes, deployed via ChatKit hosted (@openai/chatkit-react). The agent completely loses context between turns. Looking at the generated SDK code from Agent Builder, conversationHistory is recreated from scratch on each execution with only the current message. No previous_response_id or session chaining is used. It seems like ChatKit hosted is not injecting the thread history into the workflow execution. Filed a GitHub issue as well: Agent Builder hosted workflow loses conversation context between turns (chat history not passed) · Issue #184 · openai/chatkit-js · GitHub