Rename memory tools for clarity (lazy vs eager) #118
Merged
Conversation
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
- Rename add_memory_to_working_memory → lazily_create_long_term_memory - Rename create_long_term_memory → eagerly_create_long_term_memory - Old tool names still work as silent aliases for backwards compatibility - Update all documentation, examples, and tests to use new names
nkanu17
reviewed
Jan 23, 2026
Contributor
nkanu17
left a comment
nkanu17
left a comment
There was a problem hiding this comment.
I had a couple minor comments about defining constants to store function names as they are reused in multiple areas and a deprecation warning.
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.
Summary
Rename memory tools to better reflect their behavior:
add_memory_to_working_memory→lazily_create_long_term_memorycreate_long_term_memory→eagerly_create_long_term_memoryThe new names clarify the distinction:
Backwards Compatibility
The old tool names continue to work as silent aliases. The
resolve_tool_callmethod routes both old and new names to the same handlers, so existing integrations won't break.Changes
client.pyto return new namesresolve_tool_callto accept both new and deprecated namesTesting