Question about the right repo to contribute a new conversation(and session) manager which works on top of KurrentDB · strands-agents sdk-python · Discussion #168 · GitHub
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for the Strands project, we think it is a breath of fresh air in the scene. The format in which strands keeps messages makes it a right fit to store the conversation and also state in KurrentDB. We store data as a series of events in streams and have in-built windowing capabilities by count or age. For example setting a maxAge to 3600 would automatically mark all messages older than 1 hour for deletion.
We have prototype conversation manager which works on top of KurrentDB and also allows the agent to store and resume from a previous state. This works by extending the ConversationManager. For now we have proposed it to strands-agents/samples#46 for now.
My first reflex was to contribute it to the main repository but this would introduce a new dependency (kurrentdbclient) on the project which I don't feel is the right way to proceed here, but let me know. My second reflex was to contribute it to strands-tools but this is a ConversationManager and not really a tool.
So I wanted to ask, if we wanted to contribute this conversation manager, which repo would be the best place to do that?
We also plan to have it as a session manager when #57 is resolved.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Thank you for the Strands project, we think it is a breath of fresh air in the scene. The format in which strands keeps messages makes it a right fit to store the conversation and also state in KurrentDB. We store data as a series of events in streams and have in-built windowing capabilities by count or age. For example setting a maxAge to 3600 would automatically mark all messages older than 1 hour for deletion.
We have prototype conversation manager which works on top of KurrentDB and also allows the agent to store and resume from a previous state. This works by extending the ConversationManager. For now we have proposed it to strands-agents/samples#46 for now.
My first reflex was to contribute it to the main repository but this would introduce a new dependency (kurrentdbclient) on the project which I don't feel is the right way to proceed here, but let me know. My second reflex was to contribute it to strands-tools but this is a ConversationManager and not really a tool.
So I wanted to ask, if we wanted to contribute this conversation manager, which repo would be the best place to do that?
We also plan to have it as a session manager when #57 is resolved.
Kind regards,
Lokhesh
Beta Was this translation helpful? Give feedback.
All reactions