Previously swap-system-message-in-history would result in the conversation history having the system message of the active assistant right after the latest transfer call message. However since sometime around Jan. 16th, the system message in this transfer mode is always the first message in the conversation history. This change appears to be causing some regression issues with agents/squads that have worked well for several months, hence I was wondering if the behaviour of swap-system-message-in-history could be reverted or a new mode could be added that has the same behaviour as the swap-system-message-in-history mode used to before.

@mm7912 I understand the importance of maintaining consistency in your conversation history and how changes can affect your workflow. While I don't have the capability to revert changes or implement new modes directly, I can certainly help you by forwarding your feedback to the relevant team. Would you like me to add a message to the system to document this issue and request a review of the change in behavior of the

swap-system-message-in-history

function? If so, please provide me with any specific details or examples you would like to include in the message.

Here is a call id from Jan 13th: a768818b-e26f-4ad3-86eb-feb0e046e162 (here the system message of final assistant in conversation history appears right after the assistant transfer result message) Here is a call id from Jan 16th: 4fa891c2-9d88-44b5-8979-f95c0d1003a1 (here the system message of final assistant in conversation history appears at the start)

@mm7912 Thank you for providing the call IDs. I will document this issue and include the examples you've provided to illustrate the change in behavior of the system messages in the conversation history. This information will be helpful for the development team to understand the regression issues you're experiencing. Once I've documented this, would you like me to submit a support ticket on your behalf to ensure that this issue is addressed by the appropriate team?

Yes please submit a support ticket

@mm7912 Sweet. Have a great day!