Support Local (On-Premises) Memory Storage in Future Releases?

[yulongbai-nov]

Recent changes in the repository have migrated agent memory storage from local (SQLite-based) to a remote/cloud-based GraphQL API. For users who require on-premises or private deployments, will there be an option to store and manage agent memory locally in future releases? If not, are there recommended approaches for maintaining this capability?

Relevant Commits:

Refactor memory migration logic to remove origin field (local memory logic disabled): f596ad90b34a2a9a3cce3abe7ca3b80d00d47672 Refactor memory management to use GraphQL API for data retrieval and mutation (full shift to remote): 04c901ea5df461e6f2eb57064873ba528f857c21 Refactor: Move constants module and update URLs da120373629757259c4ca8dd724cda19b97bf13c

[avie66]

Hey @yulongbai-nov Thank you for feedback 🙌 It turns out that this task is not a priority for us right now. We would look back into this in future.

[SIGAN]

There should be then GraphQL server published or instructions how to configure it. Constants with URLs. There is a contradiction between "Deploy On-Premise: For maximum security" and the current code base. The fact that memories are shared with external API and it is not documented is very shady practice.