-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document Chat
and Conversation
Utilities When Using Summary Conversation Memory
#1217
Comments
@shhlife ah I had misunderstood; the behavior you see with the That said, this output is concerning:
Does the LLM consistently reply with a summary as part of its response? I can't seem to reproduce it with: from griptape.memory.structure import SummaryConversationMemory
from griptape.structures import Agent
agent = Agent(conversation_memory=SummaryConversationMemory(offset=2, autoprune=True), stream=True)
agent.run("Hi, I'm jason")
agent.run("I love bananas and trees")
agent.run("I left my heart in San Francisco")
agent.run("I'm quite fond of apples")
agent.run("I just love food in general")
|
@collindutter ahh.. I didn't understand how that worked. Maybe we can update the docs to show what's expected & show what is being sent to the LLM? Is it possible to get just the summary itself? Also, the showing of the summary is happening when using the Chat utility.
|
SummaryConversationMemory
maintaining entire thread of memory, even with offset
setChat
and Conversation
Utilities When Using Summary Conversation Memory
Describe the bug
It appears like SummaryConversationMemory is maintaining the entire thread of memory instead of summarizing it.
To Reproduce
prints out
Expected behavior
I would expect it to just have the last 2 Q/A entries, and the summary.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
I also noticed that when using the
Chat
utility, it outputs the response AND the summary with each interaction.The text was updated successfully, but these errors were encountered: