chore: add cached tokens props into RabbitMQ agent message#4086
Open
forestileao wants to merge 1 commit intomainfrom
Open
chore: add cached tokens props into RabbitMQ agent message#4086forestileao wants to merge 1 commit intomainfrom
forestileao wants to merge 1 commit intomainfrom
Conversation
Signed-off-by: Pedro F. Leao <pedroforestileao@gmail.com>
|
👋 Commands for maintainers:
|
lucaspin
approved these changes
Apr 11, 2026
shiroyasha
approved these changes
Apr 11, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
cache_read_tokensandcache_write_tokensfields to theAgentRunFinishedMessageprotobuf message (fields 7 and 8)
AgentUsagePublisherprotocol,UsagePublisher,and
NoopUsagePublishercache_read_tokensandcache_write_tokensfromRunUsageto the RabbitMQ messagein
_record_usageWhy
Previously,
total_tokensin pydantic_ai'sRunUsageonly includesinput_tokens + output_tokens— cached tokens were tracked in the DB (update_run_usage) but neverpublished to the RabbitMQ usage message. This means the SaaS usage service had no visibility
into prompt caching costs.