Skip to content
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

feat: persistent memory layer #1

Open
pkarw opened this issue Dec 7, 2024 · 1 comment
Open

feat: persistent memory layer #1

pkarw opened this issue Dec 7, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@pkarw
Copy link
Collaborator

pkarw commented Dec 7, 2024

Add a vector store to save the execution context between the calls. With the persistent storage, we will be able to

  • implement async calls (ag continue the flow after Slack/Email message from where it paused)
  • implement a Knowledge repository for the agent to use and aggregate
  • optimize the context window (RAG)

It should be dependency-less.
It should be abstract - so one can switch the driver within the Team configuration.
It probably should provide a toolkit like @tools/vectorstore -> add, find etc.

TBD: to select a vector store provider for the initial use, options:

@pkarw pkarw added the enhancement New feature or request label Dec 7, 2024
@pkarw
Copy link
Collaborator Author

pkarw commented Dec 9, 2024

Should be implemented both ways:

  • vector store (described above)
  • simple KV tool - memoryGet, memorySet + configurable backend

Wdyt @grabbou?

@pkarw pkarw changed the title feat: Persistent memory layer feat: persistent memory layer Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant