Repository navigation
fix: report measured OpenAI token usage - #95
Merged
mldangelo merged 3 commits intoOct 8, 2026
Merged
Conversation
arunimshukla
force-pushed
the
fix/real-openai-token-usage
branch
from
September 27, 2026 16:59
66ed106 to
3e1430c
Compare
mldangelo
approved these changes
Oct 8, 2026
mldangelo
left a comment
Member
There was a problem hiding this comment.
Reviewed per-iteration token aggregation, omission of incomplete usage, and removal of fabricated cost. Added real-SDK loopback integration coverage for measured totals, zero usage, and missing usage. All 31 local tests and lint pass, as does current Node 20/22/24 CI.
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
Use the token usage reported by OpenAI across the ReAct loop instead of estimating usage from the number of messages.
The provider currently reports:
and derives cost from a hard-coded per-token rate. Two runs with the same message count therefore report identical usage even when the API reports different token counts, and the cost cannot be correct for arbitrary configured models or OpenAI-compatible base URLs.
Changes
completion.usageacross every successful ReAct completioncostwhen the provider has no authoritative price sourceIf any successful completion omits usage, the aggregate is omitted rather than presenting a partial total as complete.