Pavlo Paliychuk
Pavlo Paliychuk
@tmc Appreciate the review, will open a docs PR this week
@jacoblee93 my bad, just ran the formatter
@Joffcom Hey, makes sense thanks, will update the PR. We don't require an api url for the cloud sdk, so I will make it optional. Noted about nodes contributions, we've...
@Joffcom removed previously added zep cloud memory node, zep cloud api credential and added cloud support to the original node. I made apiUrl optional as well as it's built into...
@Joffcom Makes sense, just updated the credential. I also realized that now that cloud control inside of memory node is somewhat redundant as we can get that info from the...
@Joffcom That makes sense to me, rearranged the order of credential fields. Thanks!
@Joffcom @OlegIvaniv Hey guys, any update on this PR? Thanks!
@OlegIvaniv Hi, thanks for reviewing this. The message merging is intentional. The reason why the memory (facts, summary) along with the messages comes as a Human message is that we've...
@OlegIvaniv Got it makes sense. I will add a configurable option to our `ZepCloudChatMessageHistory` class to return all messages. The Zep Memory Context (facts and summary) will be put inside...
@OlegIvaniv Just updated langchain community version to include a recently [added](https://github.com/langchain-ai/langchainjs/pull/5803) `separateMessages` option to zep memory and chat history. Lmk if that works for you. I also had to bump...