adding usage to default context fields #3434
Open
+24
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
@DouweM for review whenever you get a chance no rush on this |
DouweM
requested changes
Nov 17, 2025
| 'max_retries': ctx.max_retries, | ||
| 'run_step': ctx.run_step, | ||
| 'partial_output': ctx.partial_output, | ||
| 'usage': ctx.usage, |
Collaborator
There was a problem hiding this comment.
Thanks, let's update the docstring on line 17, as well as the Temporal doc in the "run context" section.
mattbrandman
force-pushed
the
temporal-usage-on-context
branch
from
e338b7e to
2ac363e
Compare
mattbrandman
force-pushed
the
temporal-usage-on-context
branch
from
befa4d1 to
8a1e022
Compare
Contributor
Author
|
@DouweM rebased and updated |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This adds the usage field to the context that is by default passed to temporal activities. This is useful if each individual message of an agents execution needs / wants to know the usage up to that point. This can be extremely useful if you are doing some type of cancellation flow and need the information to provide to a cancellation handler to save usage up to that point. Usage would not include the current message which would need to be approximated by the end user if it was of vital importance.
Closes #3420