4 ms·
This is something I have been so desperately wanting that I thought I would build a hacky version for myself. - How did you solve the long-term memory problem?
by yewenjie 2y ago
This is something I have been so desperately wanting that I thought I would build a hacky version for myself.
- How did you solve the long-term memory problem? What kind of issues are you facing with scaling the number of tools?
- I like the idea but there's one crucial thing missing for me. I will happily pay for your app if it lets me bring my own API keys/ endpoints for models that I can host, so that I know my data is private and secure.
- darweenist 2y agoThanks for the feedback! - Right now, we use a combination of RAG and chain of thought for storing memories. At different time intervals, we'll create memories at different levels of granularity. For example, at the end of every conversation, we'll embed some vectors based on specific commands from the user. At the end of each day, we'll have the LLM reflect on key questions related to a user's routine. And every few days, it'll reflect on the user's short/long term goals. This has worked to some degree, but we're still in the very early stages of figuring out how to do long-term memory for an assistant. - Scaling the number of tools is definitely a struggle since we want to make our integrations as thorough as we can. It takes time, so we just try to keep growing the list consistently. We have an internal goal of adding at least one new major integration every month. - Love the idea of bringing your own API keys/endpoints. We've gotten this feedback before, so we'll seriously consider it in our next few sprints!
- M4v3R 2y ago+1 for bringing your own LLM
- darweenist 2y agoNoted!