fix: automatic memory injection for Google GenAI provider (#215) #221
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.
fixes #215 This commit fixes two critical issues that prevented memory injection from working with the Google GenAI SDK:
_extract_user_query now handles Google GenAI's 'contents' parameter:
inject_recalled_facts now properly injects context for Google GenAI:
Also fixed a minor bug where kwargs['messages'] wasn't being assigned back in the else branch for non-Anthropic/Bedrock providers.
Includes comprehensive tests for all Google GenAI scenarios: