Add invocation_state to ToolContext #761
Merged
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
#557 provided ToolContext which enabled tool_use but we held off on invocation_state until we had customer demand/use-cases. Issues #579 and #750 point out use cases that can't be easily solved today, so we'll allow invocation_state to be plumbed through.
We still have problems with the SDK updating the invocation_state, but it's an existing problem that we can't address until 2.0.
Naming
I went with
invocation_state
to match what we use inAgentTool.stream()
, though the description refers to keyword arguments passed to agent invocation.Related Issues
Addresses issue #579, #750
Documentation PR
Will be a follow-up PR in the docs repo
Type of Change
New feature
Testing
How have you tested the change? Verify that the changes do not break functionality or introduce warnings in consuming repositories: agents-docs, agents-tools, agents-cli
hatch run prepare
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.