Feature/memory improvements #392
Open
+32
−4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add environment variable MEMORY_FILE_PATH to configure custom storage location - Support both absolute and relative paths - Update documentation with configuration examples - Bump version to 0.6.3
As it was before
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add support for configuring memory storage location via environment variable, enhancing deployment flexibility while maintaining backward compatibility.
Server Details
Motivation and Context
Currently, the memory server uses a fixed storage location. This change allows users to specify custom storage locations through environment variables, making it more flexible for different deployment scenarios and improving container compatibility.
How Has This Been Tested?
Tested with Claude Desktop client using:
All core functionality (entity creation, relation management, observation handling) remains unchanged.
Breaking Changes
No breaking changes. Default behavior remains the same, only adding optional configuration capability.
Types of changes
Checklist
Additional context