-
Notifications
You must be signed in to change notification settings - Fork 260
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
Add SQL Conversation Storage #111
Conversation
…ction management features. Updated documentation to reflect changes in database connection handling and best practices for closing connections. Improved error handling during database initialization.
…requirements for the Python project.
Any update on this PR? I've got a similar use-case where we're using a SQL DB for storing conversations. Looks like the current HEAD of this fork needs a rebase. Happy to contribute if OP no longer has the bandwidth, but also not sure if the maintainers are willing to accept this. Looking for some feedback either way. Thanks! |
Hi @Rajaniraiyn, Also add a mention to this package in the doc for python. Thanks. |
Hey @cornelcroi
Thanks |
Can you add the pip install with the package like we did here ? Thanks. |
@cornelcroi I have updated both DynamoDB and SQL storage docs for python, specifying extras dependency installation. Let me know any further changes required. |
Great, thanks. |
Issue number: #110
Summary
Changes
This PR adds a new feature, SQL Storage, to the Multi-Agent Orchestrator system. It introduces persistent conversation storage using the
libsql
library, supporting both local SQLite databases and remote databases. This implementation improves flexibility, reliability, and scalability for storing agent conversation history.User experience
Before this change:
After this change:
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change? No
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.