feat: pass invocation_state to model providers #1414
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.
Enables custom model providers to access invocation_state from agent calls via kwargs. This supports use cases like custom request metadata, tracing context, and provider-specific configuration.
Changes:
Custom providers can access via: kwargs.get('invocation_state')
Description
This PR enables custom model providers to receive
invocation_statefrom agent invocations. Theinvocation_stateparameter flows from the agent call through the event loop to the model'sstream()method, where custom providers can access it viakwargs.get('invocation_state').This supports use cases such as:
The implementation is fully backward compatible - the abstract
Model.stream()already accepts**kwargs, so no changes are needed to the base interface.Related Issues
N/A
Documentation PR
N/A - No documentation changes needed as this extends existing
**kwargsfunctionalityType of Change
New feature
Testing
How have you tested the change?
hatch run prepareChecklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.