Fix memory tool entry parsing when content contains section sign#162
Merged
teknium1 merged 1 commit intoNousResearch:mainfrom Feb 28, 2026
Merged
Conversation
- Use ENTRY_DELIMITER (\\n§\\n) instead of '§' when splitting entries in _read_file - Prevents incorrect parsing when memory entries contain '§' character - Aligns read logic with write logic for consistency
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR fixes a bug in the memory tool's _read_file method where entries were incorrectly split using a single "§" character instead of the ENTRY_DELIMITER ("\n§\n"). When a memory entry contained the section sign character (e.g., "User prefers § for sections"), the parser would wrongly split it into multiple entries. The fix aligns the read logic with the write logic, which uses ENTRY_DELIMITER.join() for consistency. This ensures entries containing "§" in their content are parsed correctly and prevents data corruption when loading MEMORY.md or USER.md files.