Change optimize_query default to False in client #76
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.
Changes
optimize_queryparameter fromTruetoFalsein the client'ssearch_long_term_memoryfunctionRationale
This change reduces unnecessary LLM calls for query optimization by defaulting to
False. Users can still explicitly enable optimization when needed by passingoptimize_query=True.Testing
test_search_long_term_memory_with_optimize_query_default_falseto verify the new defaulttest_search_long_term_memory_with_optimize_query_true_explicitto verify explicit override still works