fix(framework): omit costUsd when the agent reports tokens but no price#617
Merged
Merged
Conversation
suleimansh
added
bug
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
1 participant
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.
The Claude Code driver's
parseUsagesetcostUsd: 0when a result line carried token usage but nototal_cost_usd.DriverUsage.costUsdis documented as omitted (never 0) in that case: the budget cap reads 0 as "free" and undefined as "unknown" (#540), and the Codex driver already omits it. Now the field is omitted when there's no finite price, matching the contract and the other driver. Claude runs that report a price are unchanged.Regression test added (StreamJsonParser: usage present, no price -> costUsd absent). Changeset: patch.