DRAFT: Dev/add usage details to Usage class #726
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.
PR to enhance the
Usage
object and related logic, to support more granular token accounting, matching the details available in the OpenAI Responses API . Specifically, it:input_tokens_details
andoutput_tokens_details
fields to theUsage
dataclass, storing detailed token breakdowns (e.g.,cached_tokens
,reasoning_tokens
).Motivation