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
Please do a quick search on GitHub issues first, the feature you are about to request might have already been requested.
Expected Behavior
I've seen other mcp memory stores in python and npm that have a local file-based memory store that is useful for testing and for local development as well as possible other uses. I'm thinking we store memory as a JSON object and have it auto-configure in the application.properties or application.yml.
Current Behavior
Currently we only have in-memory, jdbc, neo4j, and possibly soon a mongo memory. Having the option to supply a json file isn't included directly.
Context
We could extend the in-memory chat memory to allow for a file to be picked up when it initializes, but it would be nice to have a way to combine the two in a local file system method that uses auto-config.
The text was updated successfully, but these errors were encountered:
Please do a quick search on GitHub issues first, the feature you are about to request might have already been requested.
Expected Behavior
I've seen other mcp memory stores in python and npm that have a local file-based memory store that is useful for testing and for local development as well as possible other uses. I'm thinking we store memory as a JSON object and have it auto-configure in the application.properties or application.yml.
Current Behavior
Currently we only have in-memory, jdbc, neo4j, and possibly soon a mongo memory. Having the option to supply a json file isn't included directly.
Context
We could extend the in-memory chat memory to allow for a file to be picked up when it initializes, but it would be nice to have a way to combine the two in a local file system method that uses auto-config.
The text was updated successfully, but these errors were encountered: