[BUG] Chat history should be manage at backend if ChatId or Session id is getting passed in api calls.

[navinkeshari]

Construct a sequence involving memory nodes and conversation nodes. Initiate a conversation via the REST API, providing the chat ID or session ID after the initial call response. The flow fails to maintain the same context and instead alters the context. To handle context changes, the backend requires the passing of a chat_history list, potentially leading to an increase in request bandwidth. The system should retrieve chat details based on the chat or session ID.

[HenryHengZJ]

agree! we will work on that improvement!

[emrahtoy]

also related with #1584

[yos1p]

Thumbs up on this. Very important.

[HenryHengZJ]

This is now available in v1.6.5, every memory nodes now have a sessionId and automatically retrieve the chat history with it. This removes the need for passing history array in the API request

[emrahtoy]

Much appreciated, thank you.

[haimco50]

This is now available in v1.6.5, every memory nodes now have a sessionId and automatically retrieve the chat history with it. This removes the need for passing history array in the API request

thanks! @HenryHengZJ - what about context field on any other node fields initialized as part of any sessionId conversation - are those will be resored as well when passing a sessionId in a new conversation - trying to figure out how session tracking realy works - it seems to be working for chat hostory but not for context field for example - not sure whether this is bug or by design.