[enhancement] Add reasoning_effort parameter support for Azure/OpenAI configs #3737
+9
−0
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
Added support for the
reasoning_effortparameter inAzureOpenAIConfigandOpenAIConfigclasses to enable testing and comparison of different reasoning effort levels ("low", "medium", "high") supported by OpenAI's reasoning models (o1, o3, gpt-5).The parameter was recently added to OpenAI SDK but was not implemented in Mem0's configuration classes, causing a
TypeErrorwhen users tried to passreasoning_effortin their config.This change enables users to evaluate performance and latency trade-offs across reasoning models directly within Mem0.
Fixes #3651
Type of change
How Has This Been Tested?
Tested by initializing both config classes with the
reasoning_effortparameter and verifying: