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
Is your feature request related to a an existing bug? Please link it here.
NA
Describe the solution you'd like
Right now, when memory is turned on, all types of memory is stored locally using chroma or sqlite. Even when you opt in to use something like mem0, the other types of memory are still being stored locally. I would like there to be an option to extend the memory storage class and pass that as the memory store for an agent/crew. This would allow for more finetuning and control of agent memory.
The solution could be as simple as exposing a memory storage parameter for the crew/agent.
Describe alternatives you've considered
I've considered to add support for self managed mem0 instances, for example using a self managed vector store with mem0, but that would only solve part of the problem. I think giving the developer the power to fully manage how memories are stored/retrieved would be incredibly valuable.
Additional context
NA
Willingness to Contribute
Yes, I'd be happy to submit a pull request
The text was updated successfully, but these errors were encountered:
Feature Area
Agent capabilities
Is your feature request related to a an existing bug? Please link it here.
NA
Describe the solution you'd like
Right now, when memory is turned on, all types of memory is stored locally using chroma or sqlite. Even when you opt in to use something like mem0, the other types of memory are still being stored locally. I would like there to be an option to extend the memory storage class and pass that as the memory store for an agent/crew. This would allow for more finetuning and control of agent memory.
The solution could be as simple as exposing a memory storage parameter for the crew/agent.
Describe alternatives you've considered
I've considered to add support for self managed mem0 instances, for example using a self managed vector store with mem0, but that would only solve part of the problem. I think giving the developer the power to fully manage how memories are stored/retrieved would be incredibly valuable.
Additional context
NA
Willingness to Contribute
Yes, I'd be happy to submit a pull request
The text was updated successfully, but these errors were encountered: